The Environmental Data Initiative (EDI) technical team is planning to upgrade all infrastructure servers with the latest Long Term Support version (18.04) of the Ubuntu operating system (OS) during April. This upgrade will bring parity to all servers managed by EDI and will ensure timely OS updates, which bring both new features and security to the systems. EDI will begin this process by first upgrading the development environment, followed next by the staging environment, and then finally the production environment. This sequence allows us to formulate and test a solid upgrade plan, while evaluating re-configured software applications, including the use of OS-based Tomcat and Jetty servlet containers and the Nginx front-end web server. In addition, all SSL certificates will be provisioned by LetsEncrypt, a non-profit certificate authority run by Internet Security Research Group. Our upgraded infrastructure will position EDI to operate a seamless and secure infrastructure well into the future.
- Workshop: June 4 – 6, 2019, UNM, Albuquerque, NM
- Travel days: June 3 and June 7, 2019
- Application deadline: April 26, 2019
- Participation acceptance information: May 3, 2019
EDI’s newsletter for March 2019 has been sent to our email subscribers. It can also be found here.
The Environmental Data Initiative invites you to participate in the continuing development of the Information Management Code Registry with a hackathon at UNM in Albuquerque, NM on June 10 – June 14, 2019 (Monday, June 10 and Friday, June 14 are travel days). All coders and wannabe coders who have at least some experience with R or Python and an interest in writing new code or contributing existing code to the Registry are invited to contact us. EDI will cover all travel, meal and lodging expenses. The theme of this hackathon is “Data Visualization for Assessing Data Fitness for Use.” For more information, please see here.
A pair of new EML Congruence Checks will ensure the intended data file(s) are supplied by comparing precise file size in bytes to that specified in the metadata. Already the checker compares checksums (as documented in the optional EML authentication element) to ensure the correct file was received. But for some sites that check was not useful because authentication checksums were not practical to obtain as part of the data package metadata generation process. The new file size checks are offered as a more convenient option. Continue reading “EML Congruence Checker (ECC) adds new checks for file size”