Talk:PubMan Func Spec Easy Submission

From MPDLMediaWiki
Revision as of 11:12, 15 February 2008 by Uat (talk | contribs) (New page: ==UC_PM_EASM_01 upload file in structured format== ===Status/Schedule=== *Status: '''in design''' *Schedule:'''R3''' ===Motivation=== *The user wants to upload a locally created BibTeX fi...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

UC_PM_EASM_01 upload file in structured format[edit]

Status/Schedule[edit]

  • Status: in design
  • Schedule:R3

Motivation[edit]

  • The user wants to upload a locally created BibTeX file, containing one reference.

Expected outcome[edit]

Reference is batch uploaded to a collection on PubMan.

The item is created on PubMan and can be edited/modified afterwards.

Steps[edit]

  1. The user chooses a collection where he has depositor privileges
  2. The user chooses to upload a file in structured format.
  3. The user starts the upload.
  4. The system processes the uploaded file, checks for completeness, creates an item and releases them immediately. The use case ends successfully.

Alternatives[edit]

3. The user gets an error message, indicating type of error (time out during upload, invalid file, validation rules not met).

3a. User tries the upload again. continue with step 3.

3b. User cancels the upload procedure.

Actors involved[edit]

User with depositing rights for at least one collection

Data involved[edit]

BibTex File, structured format

Constraints[edit]

  • BibTeX files are individually structured. We have to agree on one common BibTex format we are going to support.

We can provide mandatory fields for each genre. Question: where should we document the mapping?

Future development[edit]

  • Upload files in Endnote format(either version 1.x-7 or verion 8.x)
    • encoding of files depends on endnote version: 1.x to 7 support ASCII, 8.x support UTF8
    • Mapping to PubMan Genres depends on endnote version (different mappings needed)

UC_PM_EASM_02 fetch Metadata from external system[edit]

Status/Schedule[edit]

  • Status: in design
  • Schedule:R3

Motivation[edit]

  • The user wants to fetch metadata for a specific item from an external system, providing an identifier.

Expected outcome[edit]

The Metadata for the item, based on the identifier, are fetched from the external system. The item is created on PubMan and can be edited/modified afterwards.

Steps[edit]

  1. The user chooses a collection where he has depositor privileges
  2. The user provides the identifier.
  3. The user starts the fetch method.
  4. The system fetches the metadata, creates an item and releases them immediately. The use case ends successfully.

Alternatives[edit]

4. The user gets an error message, indicating type of error (time out during fetching, invalid identifier, validation rules not met).

4a. User tries the upload again. continue with step 3.

4b. User cancels the upload procedure.

Actors involved[edit]

User with depositing rights for at least one collection

Data involved[edit]

Identifier from arXiv Identifier DOI

Constraints[edit]

no constraints

Future development[edit]

Provide fetching for other identifier