EMLassemblyline 3.5.5

BUG FIXES

• template_geographic_coverage() now accepts numeric values to the
  site.col parameter (#121).
• EMLassemblyline now does a better job of distinguishing metadata template
  files from other files in the same directory.

EMLassemblyline 3.5.4

Now imports taxonomyCleanr >= 1.6.2. The EDIutils package was still listed
for taxonomyCleanr 1.6.1 (#113).

EMLassemblyline 3.5.3

BUG FIXES

• Now imports taxonomyCleanr >= 1.6.1 so the EDIutils package is not required (#112).

MINOR IMPROVEMENTS

• To identify EML files created with EMLassemblyline, the application and version number are now included in the additionalMetadata element (#109).

EMLassemblyline 3.5.2

Enhancements

• Updated the get_eol() function - The get_eol() function was refactored for efficiency and clarity in the hymetDP package. The refactored function, unit tests, and updated implementation have been ported here.
• Updated provenance.txt documentation - Added some minor details to the provenance.txt documentation.

Bug fix

• Fixed keyword resolver - Keywords were not resolving to the LTER vocabulary due to a regression that occurred during the EDIutils deprecation. The missing functions have been added back to EAL.

EMLassemblyline v2.5.0

Version 2.5.0 contains substantial improvements for users and developers. See NEWS.md.

EMLassemblyline v2.4.6

Version 2.4.6 (December 2017 - April 2018) contains substantial improvements since v1.0.0, is stable, and is being archived prior to release of v2.5.0, which is a substantial refactoring of that is fully backwards compatible.

EMLassemblyline v1.0.0

EMLassemblyline v1.0.0 (June 2017 - December 2017) was developed to improve the EML creation work flow of the Environmental Data Initiative's (EDI) data curation team and it generated some interest from data managers in the Long-Term Ecological Research network. This initial version demonstrated potential to be a user friendly EML generation tool to help scientists and project technicians make EML their data. In November 2017 this version was tested on a group of scientists and technicians, revealing several weaknesses and short comings. This feed back resulted in several changes to the code thereby make this tool more robust, streamlined, and user friendly. This new version (v2.0.0) will soon be released.