Your SlideShare is downloading. ×
OpenAIRE Slides - Tutorial on compliance with proprietary repository platforms
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

OpenAIRE Slides - Tutorial on compliance with proprietary repository platforms

68
views

Published on

Tutorials/short videos about making your repository OpenAIRE compliant. (Jan. 2012 - January is OpenAIRE compliance month.)

Tutorials/short videos about making your repository OpenAIRE compliant. (Jan. 2012 - January is OpenAIRE compliance month.)

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
68
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. plus 2nd-Generation Open Access Infrastructure for Research in Europe Compliancy for proprietary platforms: what and how
  • 2. OpenAIRE compliancy Export APIs: implement export via OAI-PMH – OpenAIRE guidelines User-interfaces: enrich publication deposition workflow – Researchers must be able to associate to past publications and future publications license information and list of funding EC projects How to make your repository OpenAIRE compliant2
  • 3. Narration assumptions Your repository does not handle license and project information Your repository back-end is based on a relational database 3 How to make your repository OpenAIRE compliant
  • 4. Local data model changes Your local database has to be adapted to – Include the list of EC projects and the list of licenses as available to OpenAIRE – Associate to each publication an arbitrary long list of EC projects and one license (with an end date, if license is «embargo») How to make your repository OpenAIRE compliant4 EC projects Licenses Publications 0:n 0:n 1:1 0:n embargo_endDate E-R schema
  • 5. Local database changes Add tables or alter existing tables to handle – Licenses – EC Projects – Relationships with local tables representing publications 5
  • 6. Local database changes Licenses Licenses consist of the vocabulary: “openaccess”, “restricted”, “embargo” – Without altering publication table: create new tables for license vocabulary and for the relative associations to publications (including embargo_endDate) – Altering publication table: create new table for license vocabulary and add two attributes for license type (foreign key to licenses) and embargo_endDate How to make your repository OpenAIRE compliant6
  • 7. Local database changes Licenses - Without altering publication table 7 Publications Pub_License Licenses Embargo_endDate Name PubID:FK,PK LicenseName: FK Relational schema
  • 8. Local database changes Licenses - Altering publication table 8 Publications Licenses Embargo_endDate Name LicenseName: FK Relational schema
  • 9. Local database changes EC Projects OpenAIRE keeps the list of EC projects synchronized with CORDA EC databases OpenAIRE makes the EC projects list available for third-party consumption through a number of protocols: – EC projects materialization: download via OAI-PMH the list of EC projects from OpenAIRE – EC Projects on-demand: integrate user interfaces with HTTP calls to OpenAIRE project list 9
  • 10. Local database changes EC Projects Materialization approach (heavy, but repository operation independent from OpenAIRE system) – Create new tables for EC projects and for the relative associations with publications – EC project table minimally consist of: grant agreement and project title – Implement synchronization threads On-demand approach (light, but repository operation dependent from OpenAIRE system) – Create new table for associations between publications and EC projects, which are referred with their grant agreement number and title (for local visualization) How to make your repository OpenAIRE compliant10
  • 11. Local database changes EC Projects – Materialization approach 11 Publications Pub_Project ECProjects GrantAgreement PubID:FK,PK GrantAgreement: FK,PK Title Synchronization Relational schema
  • 12. Local database changes EC Projects – ON-demand approach 12 Publications Pub_Project PubID:FK,PK GrantAgreement: PK Title Relational schema
  • 13. Relevant links For repository managers: – http://www.openaire.eu/en/support/tool kits/repository-managers How to make your repository OpenAIRE compliant13
  • 14. plus 2nd-Generation Open Access Infrastructure for Research in Europe Automatic inference of links between EC projects and your deposited publications
  • 15. The problem By making your repository platform OpenAIRE compliant your researchers will in the future be able to specify which EC projects have funded the publications they are depositing and under which typology of license What happens with publications they deposited in the past? How to automatically infer relationships between publications and EC projects15
  • 16. Solutions Manual approach – Researchers (or librarians with info given by the researchers) are to go over all deposited publications again, to fill in the missing information Automated approach – OpenAIRE provides the machinery capable of inferring links between publications and EC projects How to automatically infer relationships between publications and EC projects16
  • 17. Automated inference 17 D-NET Mediation Services ... Publication-project linksOpenAIRE compliant repositories Text (OCR) mining [GRID-powered, D4Science data infrastructure] D-NET Inference Services OAI-PMH OpenAIRE guidelines
  • 18. Automated inference Requirements – Repository manager must provide the PDF file of the publications (e.g., FTP) – The name of the file must contain the OAI-PMH identifier of the metadata record relative to the file Output – OpenAIRE returns a list (e.g., txt, Excel) of file names followed by the list of grant agreement numbers (i.e., project identifiers) connected to them – Repository managers must write scripts to use such list and complete their databases – Researchers may be involved to validate the result of the automated inference process How to automatically infer relationships between publications and EC projects18
  • 19. Technical insights The OpenAIRE infrastructure interoperates with the D4Science infrastructure – http://www.d4science.eu The approach exploits the GRID power embedded into the D4Science infrastructure – http://www.gcube-system.org How to automatically infer relationships between publications and EC projects19