[Esip-preserve] Current Data Citation Mappings

Ted Habermann thabermann at hdfgroup.org
Tue Aug 28 11:33:42 EDT 2018

Rama et al.,

As I created this table I tried to be careful about the blanks… Let’s take them one at a time:

  1.  Resource Identifier / Type are not included in CSDGM – CSDGM was invented before we understood the importance of identifiers in metadata. It does not include any identifiers.
  2.  DataCite does not include URL’s for resources because they are implied by the DOI which is a handle that identifies the landing page. Information about data access, quality, … can be on the landing page. In fact, landing pages are sort of like metadata supplements for DOIs.
  3.  Publisher location – All publishers are located on the web these days… good old geographic location – so 1900’s!
  4.  Contributor role – CSDGM does what I called Role-by-Position (see http://wiki.esipfed.org/index.php/ISO_People) and does not include the idea of a soft-typed role.
  5.  Parent Identifier – CSDGM – see 1 above. DataCite – This is my mistake – I think a parent identifier in DataCite is a relatedIdentifier with a relationType of isPartOf. I will update my crosswalk…

Too late for recommendations regarding CSDGM – I included this as a connection to the previous guidelines. I do not think it is appropriate to include it in the next version.

Thanks for the question Rama,

==== Ted Habermann ========================
Director of Earth Science, The HDF Group
Voice: (217) 531-4202
Email: thabermann at hdfgroup.org
==== HDF: Software That Powers Science ====

From: Hampapuram Ramapriyan <hampapuram.ramapriya at ssaihq.com>
Date: Monday, August 27, 2018 at 6:57 PM
To: Ted Habermann <thabermann at hdfgroup.org>, "Parsons, Mark" <parsom3 at rpi.edu>
Cc: "esip-preserve at lists.esipfed.org" <esip-preserve at lists.esipfed.org>
Subject: RE: [Esip-preserve] Current Data Citation Mappings

I do have a question. I can see from the mapping you have done that there are blanks in the CSDGM and DCITE columns for certain mandatory or suggested concepts from ESIP’s data citation guidelines. What are the implications of that? Does it mean CSDGM and DCITE cannot accommodate those concepts (fields) at this time? Would they be recommendations for improvements  we make to CSDGM and DCITE?

From: Esip-preserve [mailto:esip-preserve-bounces at lists.esipfed.org] On Behalf Of Ted Habermann via Esip-preserve
Sent: Monday, August 20, 2018 2:07 PM
To: Parsons, Mark
Cc: esip-preserve at lists.esipfed.org
Subject: Re: [Esip-preserve] Current Data Citation Mappings

+1 – please do not hesitate to ask questions or suggest improvements (mapping always an evolving process)…


==== Ted Habermann ========================
Director of Earth Science, The HDF Group
Voice: (217) 531-4202
Email: thabermann at hdfgroup.org<mailto:thabermann at hdfgroup.org>
==== HDF: Software That Powers Science ====

From: "Parsons, Mark" <parsom3 at rpi.edu>
Date: Monday, August 20, 2018 at 3:05 PM
To: Ted Habermann <thabermann at hdfgroup.org>
Cc: "esip-preserve at lists.esipfed.org" <esip-preserve at lists.esipfed.org>
Subject: Re: [Esip-preserve] Current Data Citation Mappings

Thanks Ted, I’ll take a look.

More importantly, those of you who actually manage data (i.e. not me and Ted), should see if this aligns with your current practice.



On 20 Aug 2018, at 13:39, Ted Habermann via Esip-preserve <esip-preserve at lists.esipfed.org<mailto:esip-preserve at lists.esipfed.org>> wrote:


Attached pls find draft mapping of ESIP Data Citation Recommendation to several metadata dialects. I am using conceptual paths in ISO for simplicity. Comments/questions/suggestions welcome of course…


Some general notes:
Version: I map version to edition as the definition of edition is “a particular form or version of a published text” and the definition of version is “a particular form of something differing in certain respects from an earlier form or other forms of the same type of thing”.

Title: unambiguously maps to title rather than edition

Archive or Distributor: the mapping to publisher is very citation centric, i.e. it exists in standard citations when it is a simple name of the publisher. In this case, the publisher is included in the citation. Archive or distributor is a bit different, more like a URL which is the next item. In that case, this information goes in a different part of the metadata record.

Locator, Identifier, of Distribution Media: This item is overloaded at this point. The DataCite identifier is different than the onlink or othercit. I imagine identifier will be broken out into a single field and locator will be merged with the Archive or Distributor… BTW, having an identifier for anything (resource, individual, or organization) requires an identifierType of some sort these days.

Editor: Can’t use the same CSDGM element for editor and author. Also, if contributor is used, must have contributor role defined somehow.

Publication Place: CSDGM mapping seems right, description does not really work for DataCite.

Distributor, Associate Archive, or other Institutional Role: How is this “Distributor” different than the one listed above? It is interesting that the CSDGM mappings are different. “Othercit” is more incorrect than publish.

Data within a larger work: othercit is for other citation information about citing the resource. lworkcit cites the larger work. When we use something like RelatedIdentifier we must specify attributes (e.g. relationType) to be useful.

General note: mapping to characterStrings. When we map something to a characterString (e.g. Description) it will be difficult to use if 1) other things are there and/or no specific guidance on how to put that information in the string.

==== Ted Habermann ========================
Director of Earth Science, The HDF Group
Voice: (217) 531-4202
Email: thabermann at hdfgroup.org<mailto:thabermann at hdfgroup.org>
==== HDF: Software That Powers Science ====

Esip-preserve mailing list
Esip-preserve at lists.esipfed.org<mailto:Esip-preserve at lists.esipfed.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-preserve/attachments/20180828/cc286b77/attachment-0001.html>

More information about the Esip-preserve mailing list