Instance » History » Revision 9
Revision 8 (Miriam Baglioni, 02/12/2021 05:56 PM) → Revision 9/10 (Andreas Czerniak, 15/12/2021 03:52 PM)
h1. Instance An instance is one specific materialization or version of the result. For example, you can have one result with three instances as result of deduplication: * one is the pre-print * one is the post-print * one is the published version Each instance is characterized by the properties described in the following table. |_. field name |_. cardinality |_. type |_. description | | *accessright* | ONE | [[AccessRight]] | Maps "dc:rights":https://www.dublincore.org/specifications/dublin-core/dcmi-terms/elements11/rights/, describes the access rights of the web resources relative to this instance. | | *alternateIdentifier* | MANY | [[AlternateIdentifier]] | All the identifiers associated to the result other than the authoritative ones | | *articleprocessingcharge* | ONE | [[APC]] | The money spent to make this book or article available in Open Access. Source for this information is the OpenAPC initiative. | | *license* | ONE | string | License URL | | *pid* | MANY | [[ResultPid]] | The set of persistent identifiers associated to this instance that have been collected from an authority for the pid type (i.e. Crossref/Datacite for doi). See [[OpenAIRE_entity_identifier_and_PID_mapping_policy]] for more information. | | *publicationdate* | ONE | string | Date of the research product | | *refereed* | ONE | string | describes if this instance has been peer-reviewed or not. Allowed values are peerReviewed, nonPeerReviewed, UNKNOWN (as defined in https://api.openaire.eu/vocabularies/dnet:review_levels with synonoums of peer_review:: https://api.openaire.eu/vocabularies/dnet:review_levels/0001 ). please see below section *refereed*| https://api.openaire.eu/vocabularies/dnet:review_levels) | | *type* | ONE | string | The specific sub-type of this instance (see https://api.openaire.eu/vocabularies/dnet:result_typologies following the links) | | *url* | MANY | string | URLs to the instance. They may link to the actual full-text or to the landing page at the hosting source. | Example data : <pre> { "accessright":{ "code":"c_abf2", "label":"OPEN", "openAccessRoute":"gold" "scheme":"http://vocabularies.coar-repositories.org/documentation/access_rights/" }, "alternateIdentifier":[], "license":"http://creativecommons.org/licenses/by-nc/4.0", "pid":[], "publicationdate":"2009-02-12", "refereed":"UNKNOWN", "type":"Article", "url":["https://periodicos2.uesb.br/index.php/folio/article/view/4296"] } </pre> h2. refereed * peerReviewed:: https://api.openaire.eu/vocabularies/dnet:review_levels/0001 * nonPeerReviewed:: https://api.openaire.eu/vocabularies/dnet:review_levels/0002 base on "guidelines":https://guidelines.openaire.eu covers the vocabularies * "DRIVE guidelines 2.0 - info:eu-repo/semantic":https://wiki.surfnet.nl/download/attachments/10851536/DRIVER_Guidelines_v2_Final_2008-11-13.pdf (OpenAIRE v1.0 - Literature) * "COAR Vocabulary v2.0 and v3.0":https://vocabularies.coar-repositories.org/resource_types/ h2. Notes/Comments * 2021-12-15 ACz, do we have a field ''articleprocessingcharge'' or ''processingcharge'' ? The resourceType give the information about the type like ''article'' or ''book...'' . Further reading, "D6.4 – Monitoring OA transformation with APC data analysis final report":https://doi.org/10.5281/zenodo.4700057