[Esip-preserve] ESIP Citation Guidelines

[Lynnes, Christopher S. (GSFC-6102)]

On Oct 12, 2010, at 9:47 AM, Mark A. Parsons wrote:

> Yes, this is a good approach, Chris. similar to the 4 use cases outlined in the identifier paper.
> 
> We also need to consider the perspective of Joe Data User. "How do I cite a data set I used in my paper?" Like most existing data, the data set has no special identifiers.

Hopefully not for too much longer.  A consensus is forming around DOIs as special identifiers--if only we could proceed forward with a more widespread implementation (something I will be bringing up at the ESDSWG meeting in New Orleans).

Also, note the reciprocal Joe User use case:  How can I get the same data that I saw cited in the paper?

> What's the user to do? I would say follow the IPY Guidelines. 
> 
> -m.
> On 12 Oct 2010, at 6:00 AM, Lynnes, Christopher S. (GSFC-6102) wrote:
> 
>> I'm only half Scandinavian, so my view is not so pessimistic as Bruce's. However, as a would-be practitioner watching the debate, it looks like it has gone too far down in the weeds to have practical value to Joe Data Manager.  My suggestion is to divide and conquer by coming back to specific questions that can (and cannot yet) be answered.
>> 
>> For example:
>> (1) Can I prove that File A and B are the same file?  A: a cryptographic hash can do this (most of the time)
>> (2) Can I prove that File A and B contain the same data?  A: yes, if they are the same file. But see next question...
>> (3) Can I prove that File A and B do NOT contain the same data?  A: much more difficult, due to reformatting, reordering, etc.
>> (4) Are Dataset A and B the same?  A:  yes, if they have the same dataset identifier (e.g., a DOI)
>> (5) Did researcher A and B use the same data from datasets A and B?  A:  much more difficult to determine
>> 
>> What I have seen of the debate revolves mostly around questions 3 and 5.  Even though questions 1, 2, and 4 may seem too simple, degenerate or incomplete to be interesting from an academic standpoint, they do have some practical value in today's world of data management.  Perhaps you can couch any recommendations in terms of the questions can be answered easily, v. those that are difficult to answer?
>> --
>> Dr. Christopher Lynnes    NASA/GSFC, Code 610.2, Greenbelt, MD 20771
>> Phone: 301-614-5185
>> 
>> _______________________________________________
>> Esip-preserve mailing list
>> Esip-preserve at lists.esipfed.org
>> http://www.lists.esipfed.org/mailman/listinfo/esip-preserve
> 

--
Dr. Christopher Lynnes     NASA/GSFC, Code 610.2    phone: 301-614-5185