[Esip-preserve] Fwd: [ESIP-all] Please review Draft ESIP Data Citation Guidelines

Wed Aug 10 11:11:42 EDT 2011

FYI

-m.

Begin forwarded message:

> From: William Rossow <wbrossow at gmail.com>
> Date: 10 August 2011 8:37:23 AM MDT
> To: "Mark A. Parsons" <parsonsm at nsidc.org>
> Subject: Re: [ESIP-all] Please review Draft ESIP Data Citation Guidelines
> 
> Mark, Looks good....
> 
> On Tue, Aug 9, 2011 at 8:33 PM, Mark A. Parsons <parsonsm at nsidc.org> wrote:
>> Thanks for your helpful comments, Bill. I made revisions as described below that I believe address your concerns. See if you agree.
>> 
>> Stay tuned for more revisions and developments.
>> 
>> Cheers,
>> 
>> -m.
>> 
>> On 28 Jul 2011, at 8:09 AM, William Rossow wrote:
>> 
>>> Mark, Here are a few comments. As someone who encountered this issue
>>> 30 years ago, I can suggest adding one additional recommendation to
>>> this: data "creators" should be urged to publish something, usually a
>>> project and data product description, in the regular literature that
>>> can be cited, too.... so add to the citation recommendation that a
>>> user ALSO cite such a publication IN ADDITION to what is proposed in
>>> these guidelines.
>> 
>> I agree. I added a bit to the data author section to address this. As a side note, one of the notes of resistance I get to data citation is that it may detract from the citation of the sort of data papers you describe. This is mostly driven by the arbitrary and dated citation number limits imposed by some journals.
>> 
>> 
>>> 
>>> An editorial comment is that the document is too long and wordy. The
>>> fix, I believe is to remove most of the justification and rationale
>>> material that is actually repeated.... I would suggest removing the
>>> Introduction and keeping the Executive Summary... such a short
>>> document does not need a summary, just use it as the Introduction...
>>> but keep the sentence about "lack of consistent recommendations on how
>>> to cite...".
>> 
>> Done.
>> 
>>> 
>>> As is always the case, no fixed set of guidelines covers all cases,
>>> but are a few places where these guidelines do not cover.... maybe
>>> this can be resolved by "accumulation", ie, the element evolves over
>>> time. For instance, "author"... for really long-lived data products,
>>> especially those that become operational, there may not be a single
>>> author. However, there might be a recognizable "creator". My project
>>> (ISCCP) is a case in point... I am clearly the creator but will not be
>>> the author some years from now. Either names get added or this item
>>> should limited to the creator. Likewise, "release date" is summarized
>>> at the beginning in a way that does not encompass data products being
>>> added to over time... this is described in the expanded discussion,
>>> but maybe the "release date" should be defined as the first date of
>>> some of that version of the data.
>> 
>> I think the authorship issue you describe can be addressed with the author/creator role coupled with the "editor" role. I've added a note to that effect. Versioning also helps. Different versions may have different authors.
>> 
>> The release date is "when the particular version of the data set was first made available for use (and potential citation) by others." I think that hits your point. The detailed section talks about update dates.
>>> 
>>> For Title, how do you handle a data product with multiple parts...
>>> these usually have names, too, but the way this is described is not
>>> clear. For instance, the ISCCP product is actually 14 distinct
>>> datasets... and soon to be more. These days the files usually have a
>>> "dataset name" that handles this situation, so I think that the text
>>> only needs to be revised to make clearer that the "title" is the full
>>> dataset name, not some overarching project name, for example.
>> 
>> I added: "Note this is the title of the data set, not the project or a related publication. It is important for the data set to have an identity and title of its own."
>>> 
>>> That's it....
>>> 
>>> 
>>> 
>>> On Thu, Jul 21, 2011 at 7:40 PM, Mark A. Parsons <parsonsm at nsidc.org> wrote:
>>>> Hi all,
>>>> 
>>>> Creating a great data set can be a life’s work (consider Charles Keeling). Yet, scientists do not receive much recognition for creating rigorous, useful data. At the same time, in a post “climategate” world there is increased scrutiny on science and a greater need than ever to adhere to scientific principles of transparency and repeatability. The Council of the American Geophysical Union (AGU) asserts that the scientific community should recognize the value of data collection, preparation, and description and that data “publications” should “be credited and cited like the products of any other scientific activity.” Currently, however, authors rarely cite data formally in journal articles, and they often lack guidance on how data should be cited. The ESIP Federation Preservation and Stewardship Cluster has been working this issue for some time now. We started with a townhall meeting at AGU in 2009 and have had subsequent sessions at ESIP meetings and the GeoData2011 Conference as well as extensive e-mail and telecon discussion.
>>>> 
>>>> We have written some draft citation guidelines that we believe address the vast majority of data citation scenarios. We have presented these guidelines in multiple fora, including two ESIP meetings, for feedback and believe they are pretty solid. Now we ask all interested ESIPers to please review these guidelines closely and send feedback directly to the wiki or to the Cluster (esip-preserve at lists.esipfed.org). We plan to finalize the guidelines this fall for submission to the ESIP Assembly for formal approval at the winter meeting, so please comment soon.
>>>> 
>>>> The guidelines are at: http://wiki.esipfed.org/index.php/Interagency_Data_Stewardship/Citations/provider_guidelines
>>>> 
>>>> There is also an overview presentation on data citation at: ftp://sidads.colorado.edu/pub/ppp/conf_ppp/Parsons/How_to_Cite_an_Earth_Science_Data_Set.pdf
>>>> 
>>>> Thanks,
>>>> 
>>>> -m.
>>>> 
>>>> 
>>>> 
>>>> ---
>>>> Mark A. Parsons
>>>> Lead Program Manager
>>>> National Snow and Ice Data Center
>>>> University of Colorado, 449 UCB, Boulder, Colorado 80309-0449, USA
>>>> +1-303-492-2359, +1-303-492-2468 (fax)
>>>> skype: mark.a.parsons
>>>> http://nsidc.org, http://eloka-arctic.org
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> ESIP-all mailing list
>>>> ESIP-all at lists.esipfed.org
>>>> http://www.lists.esipfed.org/mailman/listinfo/esip-all
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Dr. William B. Rossow
>>> Distinguished Professor of Remote Sensing
>>> CREST at The City College of New York
>>> Steinman Hall (T-107)
>>> 140th Street and Convent Avenue
>>> New York, NY 10031
>>> 1-212-650-5389
>>> wbrossow at ccny.cuny.edu
>> 
>> 
> 
> 
> 
> -- 
> Dr. William B. Rossow
> Distinguished Professor of Remote Sensing
> CREST at The City College of New York
> Steinman Hall (T-107)
> 140th Street and Convent Avenue
> New York, NY 10031
> 1-212-650-5389
> wbrossow at ccny.cuny.edu