Peer: Author Deposit

This page contains the specification of author deposits in the PEER project.

---- Work in progress ----

The Author Deposit Scenario

Schema will follow

Submission of Publications

Authors are invited to self deposit publications to the PEER repositories.

Status/Schedule

• Status: in design

Actors

• Depositor

Flow of Events

• 1. A user chooses to deposit his publication to the PEER depot.
• 2. The user can enter basic metadata into a webform
• 3. The user can upload a file
  • 3.1. The system checks the file mimetype and gives an error message when the file is not recognized as application/pdf.
• 4. The user can select a journal name from a provided list
• 5. The user can send the metadata and the file to the peer depot.
  • 5.1. The user needs to fill out a captcha to avoid spamming
• 6 The webform performs a simple validation
  • 6.1. The webform content is validated successfully
  • 6.2. The webform content is validated unsuccessfully and the user gets a feedback that the content was not sent (he can change the content and try again).
• 7. The content is send to the PEER depot via FTP
  • 7.1. The content can successfully be deposited to the peer depot - the use case ends successful.
  • 7.2. The PEER depot is unavailable, the user gets a message, that the content could not be transferred to the PEER depot - the use case ends unsuccessful.

Constraints

• No deposits will be stored, if the PEER Depot is not available the author attempt will be unsuccessful.
• The user can not decide to which repository his publication is deposited to, the publication will be deposited to all participating reps.

Open Questions

• What metadata can the user enter?
• What are the minimal requirements of metadata (validation)?
• In what format do we send the metadata to the PEER depot?
• How do we talk to the FTP server? which host? which account credentials?

Additional Information

• The basic deposit webform will be hosted at the MPDL (same server as track system).

Processing and Deposit of Publications

All further steps (including duplicate check) will be developed by INRIA.

Metadata

Authors need to provide the following metadata from the deposit form: (IN PROGRESS)

||Label||Mandatory||Occurence||Comment|| DublinCore-like name Comment Title Article Title Creator3 Corresponding Author’s name: Last Name, First Name AuthorEmail Corresponding Author’s email address Description Abstract Date3 Date of Publication Identifier3 DOI or PublisherArticleId Coverage Geographic location of the Contributing Author: ISO 3166 Journal Journal Title Affiliation multi-tier organization list : Country, Organization, Laboratory 1.1.3.2 Recommended metadata ISSN These elements are not mandatory to electronic publication, and can be derived from CrossRef after a DOI is provided, and may therefore not be provided by Publishers. Further investigation will be conducted on the use of CrossRef for DOI resolution. Volume Issue Page

Type3 Mapped to info:eu-repo/semantics/article, info:eu-repo/semantics/acceptedVersion Subject Subject headings; Scientific classification (defaults to what is provided in the general STM Journal table) Language ISO 639-3 (defaults to 'eng') Embargo Embargo Period (defaults to what is provided in the general STM Journal table)1

Publishing and the Ecology of European Research

Portable Document Format

File Transport Protocol

Max Planck Digital Library

Digital Object Identifier

International Organization for Standardization

International Standard Serial Number

International Association of Scientific, Technical and Medical Publishers