Review metadata

[dfalster]

This is happening next Tuesday at 10am. Can everyone take a look at the existing metadata and think about what more we might like to include? (ping @rachaelgallagher @snubian @jamesrlawson)

[dfalster]

One thing I'm wondering about is whether we want to include proper (i.e. structured) bibliographic information. My answer preferences is yes, but interested to know what others think.

We could include this the metadata.yml, e.g.

primary:
  author: Daniel S. Falster and Mark Westoby
  title: Alternative height strategies among 45 dicot rain forest species from tropical Queensland,  Australia
  journal: Journal of Ecology
  year : 2005
  volume: 93
  pages: 521--535
  doi: 10.1111/j.0022-0477.2005.00992.x

Or in a separate bibtex file, e.g.

@article{FALSTER2005,
  author = {Daniel S. Falster And Mark Westoby},
  title = {Alternative height strategies among 45 dicot rain forest species from tropical Queensland,  Australia},
  journal = {Journal of Ecology}
  year  = {2005},
  volume = {93},
  pages = {521--535},
  doi = {10.1111/j.0022-0477.2005.00992.x},
}

It doesn't much matter which one, as it's easy enough to convert. My preference would be to keep it in the metadata.

The benefits of including proper structured information are that:

1. We can set it up so that people can directly import the references into their own bib systems.
2. Allows formation styke to be customised (e.g. for different journals)
3. Makes it easier to parse information about studies (they're data rather than text blob

Using the existing DOIs we should be able to retrieve information for many studies using some online tools, e.g. crossref or doi2bib.

[dfalster]

Discussion re bib data now in #64

[dfalster]

Following review we agreed to:

1. Condense min, max into same trait name (done, via 3dc436d)
2. Add better source info (see Add full citation details for primary and secondary references #64)
3. Construct a table of methods and add infrastructure for collating these (Construct a table of methods #67)
4. Add instructions for converting traits & subs to csv table and back again (Add instructions for converting traits & subs in metadata to csv table and back again #68)
5. Big code delete (done, Purge unused/redundant code #63)