You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Mandatory elements

PublicationCERIF representationGuidelinesENRESSH
One publication equals one record, to which other information is related to.XML element PublicationOther elements are children to this element, as such a mandatory (1)mandatory (1)

Justification: As it's the base element for all the other elements it should be mandatory to provide.

Disclaimer: High variation on source systems in terms of publication inclusion criteria, e.g. are non-scholarly publications included as well (professional and general/popular books, articles, reports etc.) or are conference presentations or short abstracts included. To some extent this can be traced by the type -element and what kind of types are included. Scope of what is actually recorded as a publication could be provided by for example provenance information in about element or otherwise controlled/validated in metadata exchange. Limitations to inclusion criteria are not recommended though, as comparability and analysis of records are more dependent on e.g. publication types to be consistent.

Internal identifierCERIF representationGuidelinesENRESSH

The organization's own ID for the publication. 

XML attribute idmandatory (1)mandatory (1)

Justification: For technical purposes e.g. harvesting and updating the record, a unique id is needed for the metadata to be traceable.

Disclaimer: None?

Publication typeCERIF representationGuidelinesENRESSH

Publication type according to the publication type classification.

XML element Type from namespace https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Typesmandatory (1)mandatory (1)

Justification: Metadata should be provided on the publication type to have at least some structure and information on the publications. This allows the data to be comparable and used as a basis for analysis and research.

Disclaimer:  Source systems almost never have the exact same semantics / classifications for publication types e.g. what is included in a review article type might differ based on the source system definition. Mapping publication types from data model to another always leads to loss of information. Three different approaches can be had on the mapping (1) try to achieve the most accurate possible mapping between data models (2) use the so called lowest denominator of publication types; a limited set of broad categories (3) use lowest denominator publication types, but include refinements where possible and use the broad categories externally.

Publication titleCERIF representationGuidelinesENRESSH

Publication title as given in the article or the book. If necessary, the title of a foreign-language publication may be transliterated. 

XML element Title as a multilingual stringoptional, possibly multiple (0..*)at least one mandatory, possibly multiple (1..*)

Justification: In terms of proper identification of the publication, a publication title should be provided. Although in theory, this could be enriched from elsewhere, but for accurate information it should be provided from the source systems to get title in the original publishing language. Data exchange can be done using multilingual strings to provide information on alternative languages as well.

Disclaimer: As publication title is provided in a free form text string, there is no guarantee that the title would match either the original publication title or title provided in other databases for the same publication.

Publication yearCERIF representationGuidelinesENRESSH

The year in which the publication was published for the first time as a version with full bibliographic information.

XML element PublicationDate

optional (0..1)mandatory (1)

Justification: For publishing date a year of the publication is needed for comparison and analyzing purposes. This allows the data to be e.g. analyzed between time periods.

Disclaimer: Publication year is not always definitive, but it should be based on the time when publication was published as a version with full bibliographic information available.

AuthorsCERIF representationGuidelinesENRESSH

Authors of the publication that were listed in the original publication or source database. 

XML element Authors with ordered embedded XML elements Author

XML element Author with embedded XML element Person

optional (0..1)

optional, possibly multiple (0..*)

mandatory (1)

at least one mandatory, possibly multiple (1..*)

Justification: Author information is highly relevant to be able to both identify and analyze the bibliographic metadata for research purposes. Without author data, there would be no ties to the persons and a research dimension, that are the people behind the publications, would be lost. To collect this information on the source systems, the metadata quality should be high as the different

Disclaimer: As the format and spelling of names might vary heavily between source systems, the use of identifiers e.g. ORCID is highly recommended. But as many researchers are still missing the unique identifiers or the systems are not supported by it, the author information should still be provided in text string format as well.

Organization authors / affiliationCERIF representationGuidelinesENRESSH

Authors affiliated in the reporting organisation.

XML element Person optionally followed by one or several Affiliation elements, or OrgUnit. A DisplayName may be specified, too.optional, possibly multiple (0..*)mandatory, possibly multiple (1..*)

Justification: Organizational author information is relevant as it ties the publication via affiliation information to a certain organization. Thus, an analysis or research can be made using the affiliation information. It also provides better legitimacy for the publication as the affiliated organization is known. The information about organizational units should be made as close to the source system as possible and it should be made mandatory for that reason.

Disclaimer: At this time there is no reliable identifier in place for organizations. By providing information in both human and machine readable formats, there would still be no up to date information on e.g. organizational units as they tend to change as time passes and organization structures change.

Discipline / Field of scienceCERIF representationGuidelinesENRESSH

The first, so-called primary field of science is mandatory.

XML element Subject containing the classification identifier and having a scheme attribute to specify the classification scheme identifieroptional, possibly multiple (0..*)mandatory, possibly multiple (1..*)

Justification:

Disclaimer:


Optional elements

DOICERIF representationGuidelines

The Digital Object Identifier (DOI) of the publication.

XML element DOIoptional, possibly multiple (0..*)
ISSNCERIF representationGuidelines

The ISSN number of the series publishing the journal, monograph or parent publication according to the primary printed version. If there is no printed version, the ISSN number of the electronic version will be indicated.

XML element ISSNoptional, possibly multiple (0..*)
ISBNCERIF representationGuidelines

Publication or parent publication ISBN number.

XML element ISBN

optional, possibly multiple (0..*)
Source titleCERIF representationGuidelines

The source (another Publication) where this publication appeared. E.g. a journal article lists here the journal where it appeared. To be used for a publishing channel.

XML element PublishedIn with embedded XML element Publicationoptional (0..1)
VolumeCERIF representationGuidelines

Volume of the journal or series in which the article appeared.

XML element Volumeoptional (0..1)
NumberCERIF representationGuidelines

Issue of the journal or series in which the article appeared.

XML element Numberoptional (0..1)
Start pageCERIF representationGuidelines

Publication's start page number in which the article was published in the same format as in the original article or source database.

XML element StartPageoptional (0..1)
End pageCERIF representationGuidelines
Publication's end page number in which the article was published in the same format as in the original article or source database.XML element EndPageoptional (0..1)

ENRESSH-VIRTA pilot

Core

  • Publication title
  • Publication year
  • Authors
    • Organization authors / affiliation
  • Publication type
  • Field of science

Optional (co-publication identification)

  • ISSN/ISBN
  • Source title
  • Volume
  • Number
  • Page numbers

Supporting documents

VIRTA European pilot - the data contents

https://openaire-guidelines-for-cris-managers.readthedocs.io/en/latest/cerif_xml_publication_entity.html





ENRESSH Minimum Data Model

Mandatory

Publication
Internal identifier
Publication type
Publication title
Publication date
Author
Organizational author and affiliation
Discipline

Optional

 DOI
ISSN
ISBN
Source title
Volume
Number
Start page
End page
  • No labels