1. Summary of Data Citation Work Jay Greenfield, Larry Hoyle, Sam Hume, Sanda Ionescu, John Kunze, Jeremy Iverson, Barry Radler, Wendy Thomas, Mary Vardigan, Stuart Weibel, Michael Witt, Wolfgang Zenk-Moeltgen

2. Citation vs. Source Information Source information: Package of information describing the source of an object Citation: Serialization of some of those objects; provides attribution for intellectual effort and distinguishes the object Source information can be used for other purposes, for example, description of an instrument and its calibration

3. Minimal Set of Citation Elements Creator (with role) Title Publisher Contributor (with role) Publication Date Identifier/Locator Resource Type

4. Which Need Controlled Vocabulary? Contributor Role Resource Type

5. Controlled Vocabulary for Contributor Role Prior art: Harvard/Wellcome Trust taxonomy Mapped it to the DDI Lifecycle events CV Group had a conference call with taxonomy developer Open to collaboration around the taxonomy We could potentially build a hierarchical classification scheme with the H/W taxonomy at the top level

6. Degree of Contribution Many problems with numeric metrics Harvard Wellcome group came up with Lead, Equal, and Supporting We agreed that this was a good solution

7. Recommended Set of Elements Version (number, date, responsibility) Pointer to metadata Copyright (access restrictions) License DataCite elements that support citation

8. Additional Set of Objects Needing Development Permanance/stability information (with CV) – Multiple dimensions (permanence of the object, permanence of the identifier, stability of the object); relates to streamed data and dynamic data Data Fingerprint (qualitative?) Descriptors for other types of objects, for example, capture/instrument (with CV to indicate, e.g., manufacturer)

9. Objects to Be Cited All objects that correspond to versionable objects in DDI 3.2 Citation could be done where appropriate but not all elements would make sense to cite

10. Next Steps We now have minimal and recommended sets of elements – can go to modelers Need to decide how to handle CVs – need a mechanism for constraints on the vocabulary (e.g., to validate use or to manage relationships among the vocabulary items) Ensure alignment with DataCite Group now writing a paper (or papers) to be published