Assessment:Citations: Difference between revisions

From DLF Wiki
Jump to navigation Jump to search
No edit summary
Line 34: Line 34:
* other?
* other?


How can we best support appropriate citations?
==Questions to Address==
 
== To what extent do common citation formats support this? ==
 
 
 
== What are the limitations of current digital library software systems, for displaying citation information? ==
 
 
 
== What are best practices for displaying citation information for reference manager software capture? ==


# How can we best support appropriate citations?
# To what extent do common citation formats support this?
# What are the limitations of current digital library software systems, for displaying citation information?
# What are best practices for displaying citation information for reference manager software capture?


Reference resource:  ANSI/NISO Standard Z39.29-2005 (R2010) <em>[http://www.niso.org/apps/group_public/download.php/12969/Z39_29_2005_R2010.pdf Bibliographic References]</em>


We have formed a working group on these issues, that we hope will have progress to share at the next [http://www.diglib.org/forums/2015forum/ DLF Forum]!
We have formed a working group on these issues, that we hope will have progress to share at the next [http://www.diglib.org/forums/2015forum/ DLF Forum]!

Revision as of 09:30, 3 February 2015


What should a citation consist of?

The California Digital Library's Datapub blog has a good summary of data citation basics, which document the following "core" and "recommended" components of dataset citations:

Minimal components of a data citation:

Creator (Year) Title. Publisher. Identifier

Core Elements

  • Creator(s): Individual(s) or organization responsible for creating the dataset.
  • Year: Year the dataset was published, not necessarily created.
  • Title: Should be as descriptive as possible.
  • Publisher: Organization that provides access to the dataset (e.g. Dryad, Zenodo).
  • Identifier: Persistent, unique identifier (e.g. a DOI).

Additional Elements

  • Location / Availability: The web address of the dataset is essential when the identifier can’t be used to reach the dataset.
  • Version / Edition: Version of the dataset used in the present publication. Needed to reproduce analysis of versioned dynamic datasets.
  • Access Date: Date of access for analysis in the present publication. Needed to reproduce analysis of continuously updated dynamic datasets.
  • Format / Material Designator: e.g. database, CD-ROM.
  • Feature Name: A description of the subset of the dataset used. May be a formal title or a list of variables (e.g. concentration, optical density).
  • Verifier: Used to confirm that two datasets are identical. Most commonly a UNF or MD5 checksum.
  • Series: Used if the dataset is part of series of releases (e.g. monthly, yearly).
  • Contributor: e.g. editor, compiler


Digitized Special collections bring more to the table, however. ' For example, many institutions prefer to include citation information for:

  • the containing collection and holding institution.
  • Series/subseries/box/folder information
  • other?

Questions to Address

  1. How can we best support appropriate citations?
  2. To what extent do common citation formats support this?
  3. What are the limitations of current digital library software systems, for displaying citation information?
  4. What are best practices for displaying citation information for reference manager software capture?

Reference resource: ANSI/NISO Standard Z39.29-2005 (R2010) Bibliographic References

We have formed a working group on these issues, that we hope will have progress to share at the next DLF Forum!

If you are interested in helping us develop best practices and guidelines for measuring benefits of digital libraries, please join our Digital Library Assessment Google Group and speak up!  :-)