Difference between revisions of "Talk:PubMan Func Spec Easy Submission"
Jump to navigation
Jump to search
(→Functional Prototype: added comment) |
|||
| Line 30: | Line 30: | ||
===Data involved=== | ===Data involved=== | ||
BibTeX File, structured format. See [https://zim01.gwdg.de/repos/smc/tags/public/PubMan/example_bitex_AEI.bib example file] by the AEI. | |||
===Constraints=== | ===Constraints=== | ||
*BibTeX files are | *BibTeX files are idiosyncratically structured; [http://www.gerd-neugebauer.de/software/TeX/BibTool.en.html BibTool] may help with preprocessing/normalization. | ||
Does this mean we need not to provide any mapping?--[[User:Uat|Ulla]] 11:03, 26 February 2008 (CET) | |||
*Basic TeX Parsing is needed to interpret non-ascii characters etc., see for example https://dev.livingreviews.org/projects/epubtk/browser/trunk/ePubTk/lib/bibtexlib.py . | |||
*In BibTeX fields are not repeatable; thus multiple authors need to be parsed from the ''author'' field. | |||
*BibTeX allows for different formats of representing an author's name; thus the parser needs to be smart enough to recognize them all. See for example http://search.cpan.org/~gward/Text-BibTeX-0.34/BibTeX/Name.pm | |||
===Future development=== | ===Future development=== | ||
| Line 43: | Line 48: | ||
=Functional Prototype= | =Functional Prototype= | ||
Please check the [https://zim01.gwdg.de/repos/smc/ | Please check the [https://zim01.gwdg.de/repos/smc/tags/public/PubMan/Prototypes/Easy_Submission/index.html functional prototype for easy submission] | ||
Comments functional team: | Comments functional team: | ||
Revision as of 10:03, 26 February 2008
UC_PM_EASM_01 upload file in structured format[edit]
Status/Schedule[edit]
- Status: in specification
- Schedule:R3
Motivation[edit]
- The user wants to upload a locally created BibTeX file, containing one reference.
Expected outcome[edit]
Reference is uploaded to a collection on PubMan.
The item is created on PubMan and can be edited/modified afterwards.
Steps[edit]
- The user chooses a collection where he has depositor privileges
- The user chooses to upload a file in structured format.
- The user starts the upload.
- The system processes the uploaded file, checks for completeness, 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 upload, invalid file, 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]
BibTeX File, structured format. See example file by the AEI.
Constraints[edit]
- BibTeX files are idiosyncratically structured; BibTool may help with preprocessing/normalization.
Does this mean we need not to provide any mapping?--Ulla 11:03, 26 February 2008 (CET)
- Basic TeX Parsing is needed to interpret non-ascii characters etc., see for example https://dev.livingreviews.org/projects/epubtk/browser/trunk/ePubTk/lib/bibtexlib.py .
- In BibTeX fields are not repeatable; thus multiple authors need to be parsed from the author field.
- BibTeX allows for different formats of representing an author's name; thus the parser needs to be smart enough to recognize them all. See for example http://search.cpan.org/~gward/Text-BibTeX-0.34/BibTeX/Name.pm
Future development[edit]
- Upload files in structured format containing more than one reference
see Ingestion
Functional Prototype[edit]
Please check the functional prototype for easy submission
Comments functional team:
- Do we have agreed which are the Metadata to be filled in manual easy submission? At least source and lang is missing.--Ulla 12:35, 15 February 2008 (CET)
- The proposals by Natasa should be considered: default content category per genre, default creator roles per genre, default affiliation (same as previous), default source genre per item genre, default creator role if creator is of type organisation--Ulla 12:35, 15 February 2008 (CET)
- The overall requirement for submission (genre-specific Metadata for edit mask) has to be considered for easy as well as normal submission for R3
- After Manual submission, step 4, user has the same option as in Fetch MD, Step 3--Ulla 12:35, 15 February 2008 (CET)
- Fetch MD, Step 2: Provision of an external Id and uploading a bibtex file are 2 different issues. The introductory phrase on the GUI "Please provide an ID" should be more generic to cover both cases.--Ulla 12:35, 15 February 2008 (CET)
- Fetch MD, Step 3: Typo on GUI, short short. In addition, would re-phrase to "...might not cover all fetched Metadata".
--Ulla 12:35, 15 February 2008 (CET)