[Esip-preserve] Version--more

Mark A. Parsons parsonsm at nsidc.org
Thu Nov 17 13:02:46 EST 2011


By all means, Joan, use what you can. I'm glad to see some convergence in all this.

-m.

Sent from my iPad. Pardon my brevity.

On Nov 17, 2011, at 9:49 AM, Joan Starr <Joan.Starr at ucop.edu> wrote:

> Hi Mark,
> 
> I've just gotten off a conference call with the DataCite Metadata Working Group and we have agreement to alter the description substantially for the version property and to insert some discussion into the documentation about how to address dynamic datasets. As reference documents, we used your work and also a recent publication of the DCC, http://www.dcc.ac.uk/resources/how-guides/cite-datasets.
> 
> The group member from Canada's Institute for Scientific and Technical Information (CISTI) was especially impressed with the language in your guidelines and suggested that we borrow some of it. So I am going to be writing a new description for the version property as well as new copy for the overview.
> 
> May I draw from the work your organization has done?
> 
> Thanks,
> 
> Joan
> 
> -----Original Message-----
> From: Mark A. Parsons [mailto:parsonsm at nsidc.org] 
> Sent: Thursday, September 29, 2011 6:15 PM
> To: Joan Starr
> Cc: Cook, Robert B.; John Kunze; Piwowar Heather
> Subject: Re: Version
> 
> Yeah, versioning is complicated. NSIDC did an an initial study as described in the ESIP guidelines that suggests a major.minor, software style versioning scheme, but more research is needed. See  http://wiki.esipfed.org/index.php/Interagency_Data_Stewardship/Citations/provider_guidelines#Note_on_Versioning_and_Locators
> 
> Cheers,
> 
> -m. 
> On 29 Sep 2011, at 5:39 PM, Joan Starr wrote:
> 
>> Hi Mark,
>> 
>> I think the *intention* of the definition is to focus on what works for the dataset citation, and I'll claim to know something about the intention because I've been in all the conversations as chair of the metadata working group. :)
>> 
>> So...help me understand how to think about how to cite one of these dynamic datasets. Does "version" even come into the equation? 
>> 
>> I know that we did not think about this when we laid out the language below, and so this is a good opportunity to revise it to meet this need. I will definitely bring this forward to my colleagues on the working group, but it would be a great help to me if you'd offer any guidance.
>> 
>> Best,
>> 
>> Joan
>> 
>> -----Original Message-----
>> From: Mark A. Parsons [mailto:parsonsm at nsidc.org] 
>> Sent: Thursday, September 29, 2011 3:31 PM
>> To: Joan Starr
>> Cc: Cook, Robert B.; John Kunze; Piwowar Heather
>> Subject: Re: Version
>> 
>> Thanks for clarifying, Joan. Unfortunately, I do not think this definition handles Earth science data very well. A resource may be updated and therefore change every few seconds. It is impractical (and not useful) to assign a new DO to every one of those changes.
>> 
>> Cheers,
>> 
>> -m. 
>> On 29 Sep 2011, at 3:10 PM, Joan Starr wrote:
>> 
>>> Here is what the DataCite Metadata Schema documentation says about the Version property:
>>> 
>>> "If the primary resource has changed, the version number increases. Register a new DOI (or primary identifier) when the version of the resource changes to enable the citation of the exact version of a research dataset (or other resource).  May be used in conjunction with properties 11 and 12 (AlternateIdentifier and RelatedIdentifier) to indicate various information updates."
>>> 
>>> I think the effort is to tie the change to the requirements of citation.
>>> 
>>> --Joan


More information about the Esip-preserve mailing list