Difference between revisions of "Data Discovery (DataCite 4.0)"
(Created page with "[https://www.datacite.org/ DataCite] is an organization whose objective is to develop and support methods of locating, identifying and citing data and other research objects. ...") |
|||
Line 3: | Line 3: | ||
In the context of the terminology we use (described below), DataCite is an organization that created a set of recommendations at three levels (described in the schema description document) and an XML schema (a dialect) for implementing those recommendations. The dialect is currently being used in the DataCite [http://search.datacite.org/ui search portal] and in creating DOI landing pages. The dialect can be useful to communities that are trying to improve the way they share metadata; and the recommendations are useful for communities looking for expert guidance about metadata elements that are applicable to data discovery. The work we are doing explores how those recommendations can be useful for communities that are already using other dialects. | In the context of the terminology we use (described below), DataCite is an organization that created a set of recommendations at three levels (described in the schema description document) and an XML schema (a dialect) for implementing those recommendations. The dialect is currently being used in the DataCite [http://search.datacite.org/ui search portal] and in creating DOI landing pages. The dialect can be useful to communities that are trying to improve the way they share metadata; and the recommendations are useful for communities looking for expert guidance about metadata elements that are applicable to data discovery. The work we are doing explores how those recommendations can be useful for communities that are already using other dialects. | ||
− | The DataCite Metadata Schema is a list of metadata elements DataCite feels are necessary to maintain accurate and consistent identification of a resource for citation and retrieval purposes. The DataCite Metadata Schema also supplies recommended use instructions. The resource that is being identified can be of any kind, but it is typically a dataset. *Note: ''DataCite uses the term "dataset" in its broadest sense - including both numerical data, as well as any alternate research data outputs.'' The recommendation has three parts (termed spirals): mandatory concepts, recommended concepts, and optional concepts. From the schema | + | The DataCite Metadata Schema is a list of metadata elements DataCite feels are necessary to maintain accurate and consistent identification of a resource for citation and retrieval purposes. The DataCite Metadata Schema also supplies recommended use instructions. The resource that is being identified can be of any kind, but it is typically a dataset. *Note: ''DataCite uses the term "dataset" in its broadest sense - including both numerical data, as well as any alternate research data outputs.'' The recommendation has three parts (termed spirals): mandatory concepts, recommended concepts, and optional concepts. From [https://schema.datacite.org/meta/kernel-4.0/doc/DataCite-MetadataKernel_v4.0.pdf the schema]: |
"There are three different levels of obligation for the metadata properties: | "There are three different levels of obligation for the metadata properties: |
Revision as of 10:40, October 31, 2016
DataCite is an organization whose objective is to develop and support methods of locating, identifying and citing data and other research objects. They develop and support the standards behind persistent identifiers for data; and are the originators of Digital Object Identifiers (DOIs).
In the context of the terminology we use (described below), DataCite is an organization that created a set of recommendations at three levels (described in the schema description document) and an XML schema (a dialect) for implementing those recommendations. The dialect is currently being used in the DataCite search portal and in creating DOI landing pages. The dialect can be useful to communities that are trying to improve the way they share metadata; and the recommendations are useful for communities looking for expert guidance about metadata elements that are applicable to data discovery. The work we are doing explores how those recommendations can be useful for communities that are already using other dialects.
The DataCite Metadata Schema is a list of metadata elements DataCite feels are necessary to maintain accurate and consistent identification of a resource for citation and retrieval purposes. The DataCite Metadata Schema also supplies recommended use instructions. The resource that is being identified can be of any kind, but it is typically a dataset. *Note: DataCite uses the term "dataset" in its broadest sense - including both numerical data, as well as any alternate research data outputs. The recommendation has three parts (termed spirals): mandatory concepts, recommended concepts, and optional concepts. From the schema:
"There are three different levels of obligation for the metadata properties:
● Mandatory (M) properties must be provided,
● Recommended (R ) properties are optional, but strongly recommended for interoperability and
● Optional (O) properties are optional and provide richer description.
Those clients who wish to enhance the prospects that their metadata will be found, cited and linked to original research are strongly encouraged to submit the Recommended as well as Mandatory set of properties. Together, the Mandatory and Recommended set of properties and their sub‐properties are especially valuable to information seekers and added‐service providers, such as indexers. The Metadata Working Group members strongly urge the inclusion of metadata identified as Recommended for the purpose of achieving greater exposure for the resource’s metadata record, and therefore, the underlying research itself."
xPath Note: The xPaths included in this table use several wildcards. // means any path, so //gmd:CI_ResponsibleParty indicates a gmd:CI_ResponsibleParty anywhere in an XML file. /*/ indicates a single level with several possible elements. This usually indicates one of several concrete realizations of an abstract object. For example /*/gmd:identificationInfo could be gmd:MD_Metadata/gmd:identificationInfo or gmi:MI_Metadata/gmd:identificationInfo and gmd:identificationInfo/*/gmd:descriptiveKeywords could be gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords or gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:descriptiveKeywords. Fit: The fit of the dialect path with the concept is estimated on a scale of 1 = excellent two-way fit, 2 = one-way fit or some other problem, 3 - extension required.