PubMan OpenAire Requirements

MPDL

The OpenAIRE Project - some background information
OpenAIRE stands for "Open Access Infrastructure for Research in Europe". The project's aim is to enhance Open Access in Europe by implement the Open Access policy.

Practical actions to implement the policy:


 * European Helpdesk System: Network of Open Access offices in 27 countries.
 * OpenAIRE Portal and e-infrastructure for repository network.
 * Repository for Publications without an institutional repository.

Why do (should) we care
Currently the European Commission has two policies on Open Access in practice:
 * Guidelines for Open Access . (ERC Scientific Council, 2007)
 * Open Access Pilot in FP7 .(European Commission, August 2008)
 * Open Access in Horizon2020, the EU Framework Programm for Research and Innovation

-->Horizon2020 (starting in the year 2014) requires that all funded publications are published in an OpenAIRE-Compliant repository.

Alternative: Publishing in the OpenAIRE Orphan Repository. Problem: Publications would have to be entered in two repositories. This means more work for scientific/librarian staff.

Requirements for OpenAIRE Compliance

 * Working OAI-PMH : OpenAIRE Repositories are harvested weekly by the OpenAIRE Portal.
 * Definition of a DC-Set for Harvesting.
 * Listing of PubMan in OpenDOAR (Directory of Open Access Repositories)
 * Get Project Vocabulay
 * Implement a new metadata field for project vocabulary in PubMan
 * Validation of PubMan : Therefore a web tool is available.
 * Registration of PubMan at OpenAire Portal. Logo is available and can be implemented ;-)

To Dos for the PubMan Team
The To-Dos for OpenAIRE compliance are described in the following sections.

Overview


 * Make the OAI-PMH-Interface work.
 * Set PubMan on DOAR List.
 * Define a DC-Set for Harvesting.
 * Validate PubMan.
 * Register PubMan.

1 Make OAI-PMH work

 * Done: Ask Michael Franke. Probably this is complicated.--> OAI-PMH is working now.

2 Set PubMan on DOAR-List
The DOAR-List is a list of open access repositories around the world. To be harvested by the OpenAIRE Portal a repository has to be on these list.

At the moment PuRe is registered as "escidoc" at this list. 

eDoc is still listed as MPG's institutional repository.

Title

 * Use element dc:title
 * | Application Profile

Creator

 * Use element dc:creator
 * Application Profile

Publication Date

 * Use element dc:date
 * Take date.published --> date.published-online --> date.accepted --> date.submitted --> date.modified --> date.created --> event.startdate
 * Application Profile

Publication Type

 * Use element dc:type
 * Genre mapping
 * Article --> info:eu-repo/semantics/article
 * Book --> info:eu-repo/semantics/book
 * Book Chapter --> info:eu-repo/semantics/bookPart
 * Proceedings --> info:eu-repo/semantics/conferenceObject
 * Conference Paper --> info:eu-repo/semantics/conferenceObject
 * Meeting Abstract --> info:eu-repo/semantics/other
 * Talk --> info:eu-repo/semantics/lecture
 * Conference Report --> info:eu-repo/semantics/conferenceObject
 * Poster --> info:eu-repo/semantics/other
 * Teaching --> info:eu-repo/semantics/other
 * Thesis degree=Master --> info:eu-repo/semantics/masterThesis
 * Thesis degree=Diploma --> info:eu-repo/semantics/other
 * Thesis degree=Magister --> info:eu-repo/semantics/other
 * Thesis degree=PhD --> info:eu-repo/semantics/doctoralThesis
 * Thesis degree=Staatsexamen --> info:eu-repo/semantics/other
 * Thesis degree=Habilitation --> info:eu-repo/semantics/other
 * Thesis degree=Bachelor --> info:eu-repo/semantics/bachelorThesis
 * Paper --> info:eu-repo/semantics/workingPaper
 * Report --> info:eu-repo/semantics/report
 * Journal --> info:eu-repo/semantics/other
 * Issue --> info:eu-repo/semantics/other
 * Series --> info:eu-repo/semantics/other
 * Other --> info:eu-repo/semantics/other
 * Newspaper Article --> info:eu-repo/semantics/other
 * Newspaper --> info:eu-repo/semantics/other
 * Case Note --> info:eu-repo/semantics/other
 * Case Study --> info:eu-repo/semantics/other
 * Book Review --> info:eu-repo/semantics/review
 * Opinion --> info:eu-repo/semantics/other
 * Contribution to a collected edition --> info:eu-repo/semantics/other
 * Collected edition --> info:eu-repo/semantics/other
 * Contribution to a commentary --> info:eu-repo/semantics/other
 * Commentary --> info:eu-repo/semantics/annotation
 * Contribution to a festschrift --> info:eu-repo/semantics/other
 * Festschrift --> info:eu-repo/semantics/other
 * Contribution to an encyclopedia --> info:eu-repo/semantics/other
 * Encyclopedia --> info:eu-repo/semantics/other
 * Contribution to a handbook --> info:eu-repo/semantics/other
 * Handbook --> info:eu-repo/semantics/other
 * Editorial --> info:eu-repo/semantics/other
 * Manuscript --> info:eu-repo/semantics/other
 * Manual --> info:eu-repo/semantics/other
 * Monograph --> info:eu-repo/semantics/other
 * Multi-Volume --> info:eu-repo/semantics/other
 * Patent --> info:eu-repo/semantics/patent
 * Film --> info:eu-repo/semantics/other
 * Application Profile

Resource Identifier

 * Use element dc:identifier
 * Order:
 * Object Handle
 * File handle
 * Item URL (Not realised, because this implicated that URLs are added to the FOXMLs)
 * File URL (Not realised, because this implicated that URLs are added to the FOXMLs)


 * Application Profile

ProjectID

 * Application Profile
 * Use element dc:relation
 * Use syntax: info:eu-repo/grantAgreement/Funder/FundingProgram/ProjectID /[Jurisdiction]/[ProjectName]/[ProjectAcronym]
 * Implement
 * Project number as Identifier
 * Funder as Role
 * Field for Funding Program. Use CoNE for the field "Funding Program"
 * Field for Project Name
 * Vocabulary for ProjectIDs is availabe | here

AccessLevel

 * Use element dc:rights
 * Mapping for any Fulltext|Publisher Version|Postprint|Preprint (hierarchical order):
 * 1 when visibility = public --> info:eu-repo/semantics/openAccess
 * 2 when embargo date is filled --> info:eu-repo/semantics/embargoedAccess (nicht umgesetzt)
 * 3 when visibility = restricted --> info:eu-repo/semantics/restrictedAccess
 * 4 when visiblitiy = private --> info:eu-repo/semantics/closedAccess
 * Application Profile

'''For further Information see the OpenAIRE Guidelines Version 3.0

4 Define a DC-Set for Harvesting
The OpenAire Guidelines suggest "OpenAIRE" as setName and "openaire" as setSpec.

For further information see the OpenAIRE Guidelines Version 3.0, und

Items to be included in the set content:
 * (Items with at least one file with visibility "public" and content category "Any Fulltext", "Preprint", "Postprint" or "Publisher Version") OR
 * (Project ID available)

The DC-Set has to include the following elements (Source: OpenAire Guidelines) :

Mandatory elements :


 * Title
 * Creator
 * AccessLevel
 * Publication Date
 * Publication Type
 * Resource Identifier

Mandatory, when applicable elements :


 * subject
 * description
 * ProjectID
 * EmbargoEnd
 * Publisher

Recommended Elements :


 * Format (MIME-Type)
 * Language (ISO 639-3)
 * LicenseCondition
 * Alternative Identifier
 * Referenced Publication
 * Referenced Dataset
 * Contributor
 * Publication version
 * Format
 * Source
 * Relation
 * Coverage
 * Audience

For further information on the elements see OpenAire Guidelines Version 3.0:

5 Validate PubMan
For validating PubMan as OpenAIRE compliant repository a web tool is available.

Login: mpdl Passwort: pubman123

OAI usage validation

OAI content validation

Validation date: 2014-07-03

Auswertung der Error-Meldungen des Validation-Tests + Hinweis auf Probleme der OAI-PMH-Schnittstelle:

6 Register PubMan as OpenAIRE repository
After passing the validation, a registration is only a few mouseclicks away. The validation tool is also to use for registration. Registration is only possible, if the repository is on OpenDOAR list.

Adjustments after Validation 2015-02-12
TODO

DONE


 * Mapping Genre "Thesis"
 * Map "Thesis" to "info:eu-repo/semantics/other"


 * Mapping Date
 * If no "date.published" and "date.published online" are available, map "Event-Startdate" to "dc:date".


 * dc:format
 * Is: start- and endpage are exported in field dc:format.
 * Should be: according to the guidelines the mimetype should get exported in field dc:format. If there is no file attached, no dc:format should get exported.


 * Export of alternative identifiers
 * Is: identifiers like DOI or eDoc-ID are exported in field dc:identifier.
 * Should be: according the the guidelines alternative identifiers (list see ) should get exported in recommended field "dc:relation". The term is defined by info:eu-repo/semantics/altIdentifier info:eu-repo/semantics/altIdentifier/ /, for example: info:eu-repo/semantics/altIdentifier/doi/10.1234/789.1. For more information see.
 * Suggestion: cancel export of alternative identifiers in field "dc:identifier". Implement the export of alternative identifiers in field dc:relation only if it is not too much effort.
 * Mapping:
 * arxiv --> arxiv – arXiv.org identifier
 * DOI --> doi – Digital Object Identifier
 * ISBN --> isbn - International Standard Book Number
 * ISSN --> pissn - International Standard Serial Number (print version)
 * PMID --> pmid - PubMed ID
 * URN --> urn - Uniform Resource Name
 * URI --> urn - Uniform Resource Name


 * Export of the source
 * Is: the titel of the source, volume, issue, publisher and publisher place are exported in field dc:source.
 * OpenAIRE guidelines say: Use field dc:source only when the described resource is the result of digitization of non-digital originals. Otherwise, use dc:relation.Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system. The syntax of info:eu-repo/semantics/reference is: info:eu-repo/semantics/reference/ / . A list of the allowed schemes can be found here . Example: info:eu-repo/semantics/reference/doi/10.1234/789.1
 * Suggestion: cancel export of source in field "dc:source". Implement the export of source.ISSN in field dc:relation with syntax info:eu-repo/semantics/reference/issn/112233 if it is not too much effort.
 * removed dc:source but the rest will not be implemented


 * Creator Roles
 * Is: other roles than "author" are not exported as dc:creator, they are not exported at all. This is a problem for all items that don't contain any creator with role "author" --> No mandatory field "dc:creator" is exported, the validation fails.
 * OpenAIRE guidelines say: "In cases of lesser responsibility, other than authorship, use dc:contributor. If the nature of the responsibility is ambiguous, recommended best practice is to use dc:publisher for organizations, and dc:creator for individuals"
 * Suggestion. If role is "editor", export it in field dc:contributor.


 * Organisation as creator
 * Is: organisation as author is exported as ,  . Organisation as an other role than "author" is not exported at the moment (see "Creator Roles").
 * OpenAIRE guidelines say: "In the case of an organization name which clearly includes an organizational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops. For example: Utrecht University. Department of Computer Sciences If it is not clear whether there is a hierarchy present, or unclear which is the larger or smaller portion of the body, give the name as it appears in the resource. Only encode organisations in this element to indicate corporate authorship, not to indicate the affiliation of an individual.
 * Suggestion:If there is an organization, export it in field dc:contributor.