News, Technical

Journal citations associated with EDI data packages

The EDI technical team recently modified the view of user contributed journal citations associated with a specific version of a data package so that the citation is now displayed on all versions of the data package, not just the version for which the citation is relevant. This enhancement allows users who browse the data package metadata landing page to see all citations related to data package series regardless of what version of the data package they are viewing. User contributed journal citations provide an easy way for the author of a data paper (or others) to increase the impact factor of the data package by directly linking the published manuscript to the supporting data package found in the EDI data repository. In fact, older manuscripts that utilize an EDI data package may be added to the list of journal citations even if the data package DOI was not available at the time of publication. We are currently exploring options for updating the DataCite DOI metadata of the data package with these citations so that downstream services may take advantage of this crowd-sourced information.

For an example, check out the “Journal Citations” for this data package on the EDI repository landing page:

Beaufort Lagoon Ecosystems LTER and V. Lougheed. 2020. Carbon flux from aquatic ecosystems of the Arctic Coastal Plain along the Beaufort Sea, Alaska, 2010-2018 ver 7. Environmental Data Initiative. https://doi.org/10.6073/pasta/e6c261fbd143e720af5a46a9a131a616. Accessed 2020-05-22.

 

Technical

Cite: A lightweight citation service for data packages in the EDI data repository

The EDI technical team has released Cite, a lightweight web-service that generates citations for data packages archived in the EDI data repository. Cite is simple to use and requires only the EDI data package identifier appended to the end of the Cite URL: “https://cite.edirepository.org/cite/”. For example, the URL “https://cite.edirepository.org/cite/edi.460.1”, when entered into a web-browser query field, returns the following ESIP-stylized citation:

Armitage, A.R., C.A. Weaver, J.S. Kominoski, and S.C. Pennings. 2020. 
Hurricane Harvey: Coastal wetland plant responses and recovery in Texas: 2014-2019 ver 1.
Environmental Data Initiative.
<a href="https://doi.org/10.6073/pasta/e288ccaf55afceecc29bdf0a341248d6">
https://doi.org/10.6073/pasta/e288ccaf55afceecc29bdf0a341248d6</a>.

Citations are generated from information found in the data package’s EML document, including the title and creator elements, and from resource information in the EDI data repository, namely the repository name, archive date, data package revision value, and digital object identifier (DOI). This information is then stylized (think “layout”) according to recommended best practices published by community organizations, such as ESIP. Citations are formatted (think “presentation”) based on the mime-type set into the HTTP request accept header field. In the above example, the citation is formatted with HTML attributes, as demonstrated by the anchor tags and HREF surrounding the DOI URL string, since the web-browser automatically requests that responses be returned as “text/html”. Cite also supports additional citation styles (Dryad, BibTex, and raw JSON) and output mime-type formats (text/plain and application/json). Design of the Cite service framework allows new styles and formats to be added with relative ease. The motivation for Cite is to provide a consistent and simple interface for generating citations from data packages found in the EDI data repository. Cite is now being used in the EDI Data Portal to display citations on the data package metadata summary pages (aka, “landing pages”). Details of the Cite web-service can be found at https://github.com/PASTAplus/cite.

Technical

Privacy Acceptance Policy

Dear EDI user,

You may have read in our October 2019 EDI News that we will be releasing an updated authentication interface on the EDI Data Portal. In conjunction with this release, we have adopted a new Privacy Policy statement that provides you with critical information regarding the data we collect about you and your rights pertaining to that data. As part of this roll-out, we ask that you acknowledge our Privacy Policy by accepting it when prompted during login. This is a “one-time” process* and covers your use of any EDI managed resources, including the EDI data repository, Data Portal, and project website, and on any of our tiered systems (production, staging, or development). If, however, you decline to accept our Privacy Policy, you will not be allowed to operate as an authenticated user on EDI’s resources; you may proceed to access all “public” content as an anonymous user in this state. We believe it is important that transparency exists when it comes to collecting and processing personal data, especially as we provide additional means for self-identification. If you have any comments or concerns about our Privacy Policy, please send them to support@environmentaldatainitiative.org. Thank you.

*Revisions or modifications to our Privacy Policy may require another acknowledgement acceptance.

Sincerely,
The Environmental Data Initiative

Technical

New Authentication Processing coming to EDI Data Portal

The EDI technical team is excited to begin a new phase in our user identity and authentication processing capabilities for the EDI data portal. Beginning this November, users will have the opportunity to identify themselves through 3rd-party identity service providers, including Google, GitHub, and ORCID, by using the OAuth/OpenID Connect protocols these organizations support. Users who login through one of these providers will eventually (late this year) be able to register their email address for data package tracking and notifications – a valuable feature to alert users of updates for data packages that they are following, such as if a new revision of a data package is added to the data repository or if a data package is found to contain erroneous or misleading data. These logins will not, however, replace the current EDI or LTER LDAP user accounts, which are still required to upload data packages and access certain tools from the EDI Data Portal. Following email registration, we will add “identity mapping” as another new feature so that you may link together identities, including those from the EDI and LTER LDAP accounts, to use whichever identity is most convenient for you. Look for identity mapping early next year.