Functional Specification[edit]

	PubMan Functional Specification
	View · Browse ; Full Submission · Easy Submission; Import · Export ; Quality Assurance · Search; Collaboration · Copyright; Collection Administration; Organizational Unit Management; User Management ; Feeding local webpages ; History of affiliations; ;
	edit

UC_PM_EASM_01 upload file in structured format[edit]

BibTeX File, structured format. See example file by the AEI.

BibTeX files are idiosyncratically structured; BibTool may help with preprocessing/normalization.
- e.g. upper and lower case corrections, resolving macros, unicode encodings vs. (la)tex encoding, etc.
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

Normalize BibTeX with BibTool (resolves macros, may be used to map field names, unifies the syntax).
Parse the - now normalized - records.
Allow for/provide a mapping for non-standard fields (and possibly genres).
Handle substructure of fields
- Multiple entries in author and keyword fields. (see also http://nwalsh.com/tex/texhelp/bibtx-23.html)
- (La)TeX encoding for special characters/formulae. (see for example https://dev.livingreviews.org/projects/epubtk/browser/trunk/ePubTk/lib/charmaps/tex2unicode.py)
Map BibTeX fields/genres (including non-standard ones) to eSciDoc PubItem application profile. Mapping can be found here.
Java Tools to check
- http://jabref.sourceforge.net/
- http://www-plan.cs.colorado.edu/henkel/stuff/javabib/