We’d like your feedback on a new EMLassemblyline feature that supports annotation of both new and existing EML documents. Continue reading “RFC: Annotating EML with the EMLassemblyline R package”
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.
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.
Dear EDI user,
The Environmental Data Initiative
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.
The software team at the Environmental Data Initiative has recently added a “PASTA+ upload report” tool to the EDI Dashboard website (https://dashboard.edirepository.org/dashboard/reports/upload_report) that allows you to query and display a list of data packages for a given scope value and for a specific period of time. The list information includes the data package identifier, DOI (if present), upload date and time, and title (if requested). The list may also be downloaded as a CSV formatted file. Requesting the title for each data package may require additional processing time if older versions of a data package are in the list. This is because metadata for older revisions is not stored in our Solr search index and, therefore, require downloading and parsing of the EML metadata to obtain the title. Read more about the EDI Dashboard.