The data life cycle, as described by DataONE's best practices (https://www.dataone.org/data-life-cycle), has eight components for managing and preserving data for use and reuse. The following describes how the components are implemented at the Arctic LTER.
In preparing a bibtex export of publications for the 40th LTER anniversity review the export needs to include in the keywords - LTER-XXX, where XXX= three-letter site acronym.
UPDATE #2:
So now we are not adding the ltersite field but we will need to add LTER-XXX as a keyword. So a simple wayis to:
The DOI field in Data Set content is a text field not a link field type. With Dispaly Suite Fields one can add a code field that will linked the DOI to doi.org.
The trick here is to use tokens to display the DOI and to link to.
So: Administration -> Structure -> Display Suite-> Fields and Add a code field.
Give it a Label and check Entities-> Node and at the bottom check Tokens
The token for the DOI field is: [node:field_doi]. You can browse the available tokens to find all the available tokens.
The update of the revision number when data sets are saved was not useful since the number can get out of hand when doing multiple saves. In the eml module the "drupal_root"/profiles/deims/modules/custom/eml/lib/EmlDataSet.php has a funtion to update the revision. I modified as such: (Note that below code uses the a patch file - and + notations.)
public function incrementEMLRevisionID() { $revision_id = $this->getEMLRevisionID(); - if (!empty($revision_id)) { - $revision_id++; - }
