-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add fields to support data papers #269
Comments
Added support for inline citations in markdown and new citation fields in commit sha 3beb10b. |
mbjones
added a commit
that referenced
this issue
Apr 25, 2018
These include a new ability to use Bibtex citation format both within the `citation` element, and within a new `bibtex` element, to create lists of refs using these in a literatureCited element (#300), as well as in usageCitation (#259), and referencePublication (#277) elements. All of this helps support data papers (#269), for which pandoc-style citation keys can be used to cite these references in the text of Markdown blocks in the EML document. Added these features as demonstrations in the eml-data-paper.xml sample document.
Completed, assuming that Appendices are just added as additional entities within the EML. Open new tickets to deal with specific issue that arise in evaluating data paper field changes. |
See example document here: https://github.com/NCEAS/eml/blob/BRANCH_EML_2_2/src/test/resources/eml-data-paper.xml |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ESA and other societies are moving towards the publication of data papers that include more complete narratives about a data set and its importance and use. An ESA committee has recommended that a new data paper publication be created, and that it use EML and other related metadata standards to create the papers. To support that, EML would need to be extended to support descriptive fields desired in data papers but not yet in EML. These would be optional to support backward compatibility. Below is a list of the fields required for a data paper, and notes on each as to its disposition in EML.
Proposed fields
/eml/dataset/title
/eml/dataset/creator
/eml/dataset/keywordSet
/eml/dataset/coverage/geographicCoverage
/eml/dataset/coverage/temporalCoverage
/eml/dataset/referencePublication
holds the canonical citation in addition to the dataset citation that is present in the various fields. This, for example, would be set to the EcoSphere citation when the datapaper is in EcoSphere.//citation/creator
(Note: ensure this is consistent with/eml/dataset/creator
)//citation/pubDate
(Note: ensure this is consistent with/eml/dataset/pubDate
)//citation/article/journal
//citation/article/volume
//citation/article/issue
/eml/@packageId
packageId
/eml/dataset/abstract
/eml/dataset/introduction
TextType
, and would enable one to point to theid
for entities to be inline displayed. One way to handle this would be via adding DocBook's inlinemediaobject to the TextType (see issues in Revisit TextType to include Markdown #275). Alternatively, these could be links in TextType that allow pointing to theid
field for entities in the data set./eml/dataset/methods/sampling/studyExtent/description
/eml/dataset/methods/sampling/samplingDescription
/eml/dataset/methods/methodStep
/eml/dataset/methods/qualityControl
/eml/dataset/purpose
to include the data synopsis (see sha c32cbe9)/eml/dataset/gettingStarted
/eml/dataset/acknowledgements
/eml/dataset/literatureCited
/eml/dataset/usageCitation
/eml/dataset/dataTable
and related entity typesMatrix
andImage
/eml/dataset/creator/@userId
/eml/dataset/creator/electronicMailAddress
/eml/dataset/creator/address
Other fields that could be added:
The text was updated successfully, but these errors were encountered: