Traitdataform Versions Save

A package to manage and compile functional trait data into predefined templates

v0.6.0

3 years ago

Major changes:

  • update internal terms to v0.10 of the Ecological Trait-data Standard (ETS). In ETS v0.10 the assignment of user-defined and standardised measurement values and trait and taxon assignments has been updated, to match labelling practice in DwC and provide a more intuitive content for those fields. Accordingly
  • the v0.9.1 terms scientificName, traitName, traitValue, and traitUnit have been renamed into verbatimScientificName, verbatimTraitName, verbatimTraitValue, and verbatimTraitUnit with new identifiers.
  • the terms scientificNameStd, traitNameStd, traitValueStd, and traitUnitStd have been renamed into scientificName, traitName, traitValue, and traitUnit and now form the default suggested content for trait data complying with the ETS. Definitions have been harmonized. The original *Std identifiers now resolve to these new terms.

This causes the output file to differ from earlier outputs. To maintain compatibility with earlier versions, an option conformsTo has been added to as.traitdata() to return the data table in terms of version 0.9. By default, output is returned in ETS version 0.10. Data releases created by traitdataform should always be labelled with the version of ETS that applies to the data!

v0.5.0

5 years ago

first stable release. Intended for submission to CRAN. From this point on, backward compatibility will be maintained.

minor changes (since v0.4):

  • complete package vignette
  • improved unit handling
  • solid demo data import

v0.3.0

5 years ago

v0.2.0

6 years ago

Release with full documentation website: https://ecologicaltraitdata.github.io/traitdataform/

Major changes

  • updated terms to traitdata standard v0.6.
  • datasets are not loaded by default, but wait for a prompt using data(). Also added documentation for all datasets and added more datasets.
  • adding function method rbind.traitdata() for merging standardised datasets into a unified table. includes handling of metadata object in attributes
  • metadata can be stored in the attributes of a dataset and will be preserved when updating the dataset. Information will be handled when merging or combining multiple datasets.
  • trait thesauri can be added more easily from a data frame or from a list of 'trait' objects.

Minor changes

  • update vignette: add section on merging and combining data.
  • added print methods for traits and thesaurus objects.