EDI’s December 2019 update has been sent to our email subscribers. The information is also available here.
If you would like to join our email list, please follow this link.
A new version of the Ecological Metadata Language (EML 2.2) was released recently with several significant additions. EDI is working with our community to explore the potential benefits of new EML features and how these work best for the data we handle, and to outline their incorporation into EDI systems. Feedback from a webinar indicated that several new EML features were high priority, and we have already adapted our data package views to display new content in a basic manner for project funding sources, taxonomic identifiers and semantic annotations at the dataset- and measurement- level. We also are migrating our harmonization format for community survey data (ecocomDP) to include annotation, and anticipate adapting ecocomDP creation code to include identifiers that we expect to appear in Level 0 (raw) data. We have begun the revision process of our Best Practices for EML Metadata material – anticipating new recommendations for EML 2.2 – by first migrating current versions to a more dynamic system using GitHub pages. Continue reading “EDI plans for EML 2.2”
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.