Difference between revisions of "Peer: Author Deposit"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) (page start) |
Kleinfercher (talk | contribs) (→Submission of Publications: added UC) |
||
Line 6: | Line 6: | ||
==Submission of Publications == | ==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 (whta kind of metadata???) | |||
*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 an pdf. | |||
*4. The user can select the 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 capture to avoid spamming | |||
*6 The webform performs a simple validation (what kind???) | |||
**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=== | |||
===Open Questions=== | |||
==Processing and Deposit of Publications== | ==Processing and Deposit of Publications== |
Revision as of 15:11, 8 September 2009
This page contains the specification of author deposits in the PEER project.
---- Work in progress ----
The Author Deposit Scenario[edit]
Submission of Publications[edit]
Authors are invited to self deposit publications to the PEER repositories.
Status/Schedule[edit]
- Status: in design
Actors[edit]
- Depositor
Flow of Events[edit]
- 1. A user chooses to deposit his publication to the PEER depot.
- 2. The user can enter basic metadata into a webform (whta kind of metadata???)
- 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 an pdf.
- 4. The user can select the 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 capture to avoid spamming
- 6 The webform performs a simple validation (what kind???)
- 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[edit]
Open Questions[edit]
Processing and Deposit of Publications[edit]
All further steps (including duplicate check) will be developed by INRIA.
Open Questions[edit]
- Were will the simple deposit form be hosted?
- What is needed for validation? (pdf mandatory, what else?)
- How does the xml look like
Additional Information[edit]
- MPDL will not store any deposits, if the PEER Depot is not available the author attempt will be unsuccessful.