Eprints Integration in Institutional Repositories-Using SWORDv2

Functional Overview
The most common use of the EPrints software is by academic and research libraries as an open access repository for managing their faculty and student output. EPrints is the software of choice for academic, non-profit, and commercial organizations building open digital repositories. EPrints preserves and enables easy and open access to all types of digital content including text, images, moving images, mpegs and data sets. The items which are to be exported will be configured in the configuration file corresponding to the metadata described in the EPrints . The EPrints export will be handled by “Admin, Config and System” roles and “Timer”. The Researcher only can assign the Items to export into EPrints.
EPrints have two types of deposit mechanisms named SWORD and Command Line Export. Converis carries this out by using the mechanism SWORDv2.

Using SWORD
The SWORD (Simple Web-service Offering Repository Deposit) protocol was designed to facilitate the interoperable deposit of resources into systems such as repositories. The use of an interoperable standard eases the burden of developing clients to deposit such resources. This paper examines nine different deposit use cases, and provides case studies and examples of each use case to demonstrate the wide range of repository deposit scenarios. The use cases range from the deposit of scholarly communication outputs from a publisher to a repository and the automatic deposit of data from laboratory equipment, to inter-repository transfer and collaborative authoring workflows.
Depositing is a two-stage process within APP and SWORD. First, a request from an authenticated user is sent to the implementation for what APP calls the „service document‟, this returns details of the collections that user is allowed to deposit to within the repository. At this point, the user may deposit their file into the chosen collection. Various things may prevent success, for example lack of authentication credentials, unacceptable file format or a corrupt MD5 checksum. The repository will send a respond indicating the success, or otherwise of the deposit.

Detailed Requirements

No.

Requirement

TYPE

#1

Correctly configured Converis regarding the Institutional Repository integration

#2

Correctly configured irconfig file


Entity Attributes
The following attributes have to be added for the following entities.

Entity PUBLICATION

InfoObject

Name

Description

Data Type Input

Type Display

Lenght

Publication

irCollection

IR collections

CHOICEGROUP

SELECT

N/A

Publication

irHandle

STRING

TEXTFIELD

256.0

Publication

irHash

IR Hash value to be used for update function

STING

TEXTFIELD

1024.0

Publication

irSubmit

To select a publication to be submitted to IR

CHOICEGROUP

SELECT

N/A

Publication

irSubmittedOn

Used to specify the publication submitted date

DATE

DATETIMEPICKER

N/A

Publication

depositDate

To specify the fullText deposit date

DATE

DATETIMEPICKER

N/A

Publication

depositDone

To deposit the fullText

BOOLEAN

BOOLEANCHECKBOX

N/A


Relation Attributes
The following attributes have to be added for the following relation entities.

Relation Entity PUBL_has_JOUR

Relation Type

Name

Description

Data Type

Input Type

Display Length

PUBL_has_JOUR

ISSN

ISSN from publication

STRING

TEXTFIELD

255.0

Relation Entity PUBL_has_FILE

Relation Type

Name

Description

Data Type

Input Type

Display Length

PUBL_has_FILE

Description

Description of the File

STRING

TEXTFIELD

255.0

PUBL_has_FILE

embargoDate

Indicates the date for when the embargo expires and the full text can be made available

DATE

DATETIMEPICKER

N/A

PUBL_has_FILE

embargoSituation

Indicates whether the full text should be available for download (open access), only within a given IP range, only through request full text, or not at all (closed access)

CHOICEGROUP

SELECT

N/A

Comments (0)