SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
1.
PRIME: Publisher, Repository and
Institutional Metadata Exchange
Achievements, Challenges and Recommendations
UCL LIBRARY SERVICES
INSTITUTE OF ARCHAEOLOGY
2012
75 YEARS OF LEADING GLOBAL ARCHAEOLOGY
Brian Hole (UP & UCL)
Jisc MRD Programme Workshop, Birmingham, 25 March 2013
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
9.
PRIME: Project focus
• Developing a system to exchange metadata between:
• the UCL Discovery EPrints institutional repository
• the Archaeology Data Service subject repository
• the Journal of Open Archaeology Data (JOAD)
• Focusing on archaeology data only to pilot the system
• Building on other successful JISC projects:
• DryadUK
• REWARD
• SWORD-ARM
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
10.
PRIME metadata schema:
Subset of the DataCite metadata schema:
• Identifier
• Creator
• Title
• Publisher
• PublicationYear
• Subject
• ResourceType (controlled list)
• Rights
• Description
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
11.
PRIME use cases:
#1: User deposits data in subject repository
#2: Researcher deposits data in institutional repository
#3: Researcher deposits data through data journal
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
12.
PRIME: Use Case #1
User deposits data in subject repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
13.
PRIME: Use Case #1
User deposits data in subject repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
14.
PRIME: Use Case #1
User deposits data in subject repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
15.
PRIME: Use Case #1
User deposits data in subject repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
16.
PRIME: Use Case #1
User deposits data in subject repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
17.
PRIME: Use Case #2
Researcher deposits data in institutional repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
18.
PRIME: Use Case #2
Researcher deposits data in institutional repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
19.
PRIME: Use Case #2
Researcher deposits data in institutional repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
20.
PRIME: Use Case #2
Researcher deposits data in institutional repository
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
21.
PRIME: Use Case #3
Researcher deposits data through data journal
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
22.
PRIME: Use Case #3
Researcher deposits data through data journal
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
23.
PRIME: Use Case #3
Researcher deposits data through data journal
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
24.
PRIME: Use Case #3
Researcher deposits data through data journal
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
25.
Metajournals as incentives
brian.hole@ubiquitypress.com www.ubiquitypress.com / @ubiquitypress
Often the research has to be fitted to funder priorities
But eventually it gets carried out
Science sometimes has unintended results, which may be of interest to a much wider communityThe resulting data therefore needs to be widely distributed
A UCL Researcher submits an article to a journal, and is asked to archive the data as a precondition of publication. The journal sends the metadata to the subject repository so that the author does not have to re-enter it. The subject repository sends the metadata and DOI of the data to the institutional repository so that it has a record of the output, and the DOI back to the journal to link the article with the data.