[Esip-preserve] Current Data Citation Mappings

Ted Habermann thabermann at hdfgroup.org
Mon Aug 20 17:07:28 EDT 2018


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

Ted

==== 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.

cheers,

-m.


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:

All,

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…

Ted

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 ====

<crosswalk.html>_______________________________________________
Esip-preserve mailing list
Esip-preserve at lists.esipfed.org<mailto:Esip-preserve at lists.esipfed.org>
https://lists.esipfed.org/mailman/listinfo/%<https://lists.esipfed.org/mailman/listinfo/%25>
(_internal_name)s

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


More information about the Esip-preserve mailing list