Eprints AP notes

From DigiRepWiki

This page draws together notes summarised from discussions on the EPRINTS-APPLICATION-PROFILE@ISCMAIL.AC.UK list. The record of the full discussion can be found in the JISCMAIL list archives.

Contents 1 ScholarlyWork title 2 ScholarlyWork subject 3 ScholarlyWork abstract 4 ScholarlyWork identifier 5 ScholarlyWork creator 6 Expression 7 Expression type 7.1 RAE Output types 7.2 OpenURL Genre List 7.3 ePrints UK project simple DC guidelines 7.4 BOAI scope 7.5 Queensland eprints (Fedora) 7.6 Eprints Soton (eprints.org) 7.7 CCLRC e-pubs 7.8 Edinburgh Research Archive (DSpace) 7.9 DARE Type list 7.10 Proposed Type List 8 Expression rights 9 Expression bibliographicCitation 10 Expression references 11 Manifestation publisher 12 Agent 12.1 Agent name 12.2 Agent dob

ScholarlyWork title

Summary of discussion/issues to 2006-06-26:

Multiple titles for different expressions, changes to title throughout the lifecycle of a Work. Relationship to Model and to Expression title.

Summary of discussion/issues to 2006-06-30:

• Consider specifying colon-space (rather than just colon) for separating subtitle from title. Even better, specify space-colon-space as it follows punctuation standards for ISBD (and makes a distinction with embedded colons in the title proper)

• Consider specifying that initial articles should be omitted.

• Consider capitalisation of proper names - it's not so easy these days to "only capitalise proper nouns"; e.g. "eLib", "e-Bay", etc. See the RDA draft at: http://www.collectionscanada.ca/jsc/working2.html#rda-pt1

ScholarlyWork subject

Summary of discussion/issues to 2006-06-26:

Changes to title throughout the lifecycle of a Work, across different expressions.

ScholarlyWork abstract

Summary of discussion/issues to 2006-06-26:

Multiple abstracts for different expressions, changes to abstract throughout the lifecycle of a Work.

Summary of discussion/issues to 2006-06-30:

Consider multiple abstracts, e.g. for translations.

ScholarlyWork identifier

Summary of discussion/issues to 2006-06-26:

Guidelines on using DOI for the Identifier of a work should be clearer about which DOI it is talking about, ie a DOI assigned by a repository.

ScholarlyWork creator

Summary of dicussion/issues to 2006-06-26:

Authoritative vs. as is on item; multiple authorship; changes in authorship at expression level

See notes on Agent.

Include a value string and a reference to the Agent.

Consider whether statement of responsibility is better captured elsewhere.

Expression

The DCAP needs additional properties to represent the following relationships in the model (if agreed):

• isFundedBy
• isSupervisedBy
• isEditedBy

Suitable candidates from the MARC Relator properties recently published by Library of Congress (http://www.loc.gov/loc.terms/relators/):

• Funder

http://www.loc.gov/loc.terms/relators/FND

"A person or organization that furnished financial support for the production of the work."

e.g.

Statement (
 Property URI ( marcrel:FND )
 DescriptionRef ( organisation1 )
)

(The "qualified name" form for the property URI is "marcrel:FND" rather than "marcrel:funder" because LoC use the codes in the property URIs)

• Supervisor / Advisor / Thesis Advisor

http://www.loc.gov/loc.terms/relators/THS

"A person under whose supervision a degree candidate develops and presents a thesis, mémoire, or text of a dissertation."

This is specific to these particular classes of resource, so we need to consider (a) whether these classes are in scope (and they may not be) and (b) whether supervisors may be specified for other classes of resource.

• Editor

http://www.loc.gov/loc.terms/relators/EDT

"A person or organization who prepares for publication a work not primarily his/her own, such as by elucidating text, adding introductory or other critical matter, or technically directing an editorial staff."

See points made about EPrints AP ScholarlyWork title

This element may be the same as that recorded in ScholarlyWork title, in which case it would not be included.

Expression type

RAE Output types

From:

Pre-defined field values for the RAE 2008 data collection system: http://www.rae.ac.uk/datacoll/subs/RAE2008PredefinedFieldValues.pdf

Output Code	Output Type	Required fields
A	Authored book	Year of publication Book title Number of pages Publisher ISBN URL if available DOI if available
B	Edited book	Year of publication Book title Number of pages Publisher ISBN URL if available DOI if available
C	Chapter in book	Chapter title Book title Number of pages in chapter Publisher of book Name of editors ISBN number of book URL if available DOI if available
D	Journal article	Article title Volume number Page numbers for article Title of journal ISSN number of journal Month/Year of publication URL if available DOI of article
E	Conference contribution	Title Name of conference/published proceedings Page numbers if available Media of output if not published ISSN number of proceedings if available Month/Year of publication or Date of conference URL if available DOI if available
F	Patent / published patent application	Title and/or brief description Patent registration number Date URL if available
G	Software	Name of software Name of software house [Publisher] Media of output Date URL if available
H	Internet publication	Title and/or brief description Publisher if available ISSN if available Date URL of publication DOI if available
I	Performance	Title and/or brief description Place of performance Media of output Start Date End Date URL if available
J	Composition	Title and/or brief description Media of output Date URL if available
K	Design	Title and/or brief description Media of output Date URL if available
L	Artefact	Title and/or brief description Location Media of output Date URL if available
M	Exhibition	Title and/or brief description Commissioning body Number of pages Publisher of report if available Date URL if available DOI if available
N	Research report for external body	Title and/or brief description Commissioning body Number of pages Publisher of report if available Date URL if available DOI if available
O	Confidential report (for external body)	Title and/or brief description Commissioning body Number of pages
P	Devices and products	Title and/or brief description Manufacturer if available Date
Q	Digital or visual products	Title and/or brief description Publisher if available Media of output Date URL if available
R	Scholarly edition	Brief description Title of scholarly edition Number of pages if available Publisher if available Editors and/or media of output ISBN number of book if available DateURL if available DOI if available
S	Research datasets and databases	Title and/or brief description Location Size Media of output Date URL if available DOI if available
T	Other form of assessable output	Title and/or brief description Location Brief description of type Date URL if available DOI if available

OpenURL Genre List

From Ann Apps, via eprints-application-profile@jiscmail.ac.uk:

Journal	http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal
	journal
	issue
	article
	conference
	proceeding
	preprint
	unknown (but known to be journal related)
Book	http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book
	book
	bookitem
	conference
	proceeding
	report
	document
	unknown (this is the fallback)
dissertation	no sub-genre list
patent	no sub-genre list

ePrints UK project simple DC guidelines

From: Using simple Dublin Core to describe eprints (http://www.rdn.ac.uk/projects/eprints-uk/docs/simpledc-guidelines/)

• Book
• BookChapter
• ConferenceProceedings
• ConferencePaper
• ConferencePoster
• InCollection
• TechnicalReport
• OnlineJournalArticle
• JournalArticle
• NewsArticle
• Other
• Preprint
• Thesis

BOAI scope

"For which body of literature, exactly, does BOAI hope to secure open access?

BOAI only seeks open access for the scientific and scholarly research texts that authors give to publishers and readers without asking for any kind of royalty or payment. As the BOAI public statement puts it, "[p]rimarily, this category encompasses...peer-reviewed journal articles, but it also includes any unreviewed preprints that [scholars] might wish to put online for comment or to alert colleagues to important research findings." It does not include books from which their authors would prefer to generate revenue. It does not include any non-scholarly writings, such as novels or news.

While the BOAI does not specifically cover donated scholarship other than peer-reviewed journal articles and preprints, it could be extended quite naturally to all the writings for which authors do not expect payment. These include scholarly monographs on specialized topics, conference proceedings, theses and dissertations, government reports, and statutes and judicial opinions."

http://www.earlham.edu/~peters/fos/boaifaq.htm

Queensland eprints (Fedora)

Type list:

• Book
• Book Chapter
• Conference Paper
• Conference Poster
• Department Technical Report
• Journal Article
• Newspaper/MagazineArticle
• Preprint
• Thesis

Eprints Soton (eprints.org)

Type list:

• Article
• Book
• Book Section
• Conference or Workshop Item
• Monograph
• Patent
• Thesis
• Artefact
• Show/Exhibition
• Composition
• Performance
• Other

CCLRC e-pubs

Type list:

• Journal Article
• Technical Report
• Misc
• Presentation
• Paper in Conference Proceedings
• Book Chapter(s) or Section(s)
• ePrint (Unrefereed Preprint)
• Thesis
• Conference Proceedings
• Book
• Journal Issue
• Manual
• ePrint (Refereed Postprint)
• Booklet

Qualifiers:

• isPresentation
• isInProceedings
• isProceedings

Edinburgh Research Archive (DSpace)

Type list:

• Thesis or Dissertation
• Research Paper
• Preprint
• Report
• Working paper
• Conference paper
• Book chapter
• Poster

DARE Type list

1. Annotation
2. Article / Letter to editor
3. Article in monograph or in proceedings
4. Book (monograph)
5. Book review
6. Book editorial
7. Collection
8. Commission report or memorandum
9. Conference lecture
10. Conference report
11. Contribution for newspaper or weekly magazine
12. Dataset
13. Dissertation
14. Documentation for grant request
15. Educational material
16. Event
17. External research report
18. Inaugural lecture
19. Interactive resource
20. Internal report
21. Newsletter
22. Newspaper article
23. Part of book or chapter of book
24. Patent
25. Physical resource
26. Preprint
27. Report for financing agency (grants)
28. Research paper
29. Service
30. Set of images
31. Software
32. Sound
33. Statistical report
34. Still image (photo, video, movie)
35. Student thesis
36. Technical documentation
37. Working material

http://www.surf.nl/download/DARE%20use%20of%20DC%20v.%202.0.pdf

Proposed Type List

See the Eprints Type Vocabulary Encoding Scheme

Expression rights

Summary of discussion/issues to 2006-06-30:

• Consider RightsHolder / CopyrightHolder as an additional Agent
• Consider DateCopyrighted

Expression bibliographicCitation

Comment from Ann Apps 2006-06-23:

I think it would be a good idea to recommend the inclusion of an OpenURL ContextObject (note name) as a 'good thing' (maybe not quite as much as 'should'). This would be of significant use to downstream applications. Eg OpenURL resolution could just prefix the resolver address and a minor bit of syntax.

For bibliographicCitation it is a good idea to have both a text version and a ContextObject - this is the DC Citation recommendation. For references it isn't possible to recommend that because there would be not way to tie them together in the list of references.

There should probably also be an example. Possibly:

Statement (
 PropertyURI (dcterms:bibliographicCitation)
 ValueString (ctx_ver=Z39.88-2004&ctx_tim=2006-04-11T11:56:10TZD 
&rft_val_fmt=info:ofi/fmt:kev:mtx:journal
&rft.genre=article
&rft.jtitle=NATURE
&rft.issue=7083
&rft.issn=0028-0836
&rft.atitle=Glutamate+receptors+at+atomic+resolution
&rft.date=2006
&rft.spage=456
&rft.epage=462
&rft.aulast=Mayer
&rft.auinit=M+L
   SyntaxEncodingSchemeURI (info:ofi/fmt:kev:mtx:ctx)
 )
)

[Everything after 'ValueString(' to 'M+L' is a single line]

Note it would also be possible to include a rfr_id which could indicate the repository identifier.

Expression references

Summary of JISCMAIL discussion to 2006-06-23:

Recommended that the wording in the "eprint specific recommendation" section should be altered. Current wording constrains references to eprint-type resources, but should be applicable to the citation of anything, including research data.

Manifestation publisher

Summary of discussion/issues to 2006-06-26:

Publisher

Different notions of 'publisher' exist

1. Publisher (formal publisher) of the journal/book/proceedings in which an eprint appears (Manifestation)
2. Publisher of the eprint, in terms of who makes it available (i.e who is supplying it to us), rather than who formally publishes it. This might be the same as the formal publisher, but might also be the repository 'agent'. It might co-exist with the formal publisher as both the publisher AND a repository might make the same thing available (Copy)
3. Publisher of the metadata and some or all of its eprint manifestations/copies - the repository (Eprint)

Different views:

• Manifestation publisher should be used to capture the informal AND formal publisher
• Manifestation publisher should only be used for the formal publisher
• Copy publisher should be used for the informal publisher

• The formal publisher is not needed
  • Bibliographic Citation will capture the formal publisher of books/proceedings and possibly the source repository
  • An additional Expression Status value [published/unpublished] could capture whether something has been formally published or not

Repository as Publisher

Is there any need to trace the source repository from which an eprint derives?

• Repository is administrative metadata and should be considered out of scope of the core appliation profile (although we might need to consider the administrative metadata requirements for future work?)
• Repository is an entity (thus needing a new element)
  • Repository as Agent, Location, Collection and Catalogue
• Repository is an agent (thus needing a new relationship)
• Repository is not a functional requirement at all

Proposal: Capture the id of the repository or other 'service' making available the Copy by using the notion of a Collection and an isMemberOf or isPartOf relationship.

Agent

Agent name

See also notes re ScholarlyWork creator

Summary of discussion/issues to 2006-06-26:

How far should the AP go in capturing parts of names?

• Where repositories ask for the author name as it appears on the (published) item, this might be captured with Expression bibliographicCitation and an authoritative version of the Agent(s) also captured.
• At a future point this authority name might be provided to the repository from another source, possibly a name authority aggregation service.
• Eprints.org are working on some code to suggest names from various sources.

Summary of discussion/issues to 2006-06-30:

Comments from Gordon Dunsire

• Use AACR (and its successor RDA) to guide name format.
  • Use the form of name most widely used by the author or their agent (publisher, etc.).
  • If this results in the same form of name for different persons, expand the initials and/or give all forenames as an extension to the name: "Smith, J. (James)". If the AP were to ask self-depositors to always do this, it will go a long way to constructing a useful authority file.
  • If this still results in the same form of name, add dates of birth (and death where appropriate). The date is given as a year only, unless this still results in the same form, in which case the day and month are added. This is probably something that would have to be done downstream, for the privacy reasons already discussed.
  • (To complete the process). If there are two persons with the same surname, forenames, and birthday, add some other kind of distinguishing data, e.g. "of Edinburgh": "Smith, J. (James), 25 Dec 1980- (of Edinburgh)" (I haven't got AACR to hand, so apologies for mistakes in punctuation).
  • Do not use honorifics or affiliation for agent name authority.
• Consider breaking name elements into separate fields.
• Consider existing authority sources (see Roddy MacLeod's message re CoS)

Agent dob

Summary of discussion/issues to 2006-06-26:

• This is seen as 'Personal' information and there might be resistance to including it.
• There might be better ways to disambiguate people.
• Library name authority does not rely on date of birth, but does use year of birth/death.