Allow meta data to be configured for Deployments

[mihow]

Deployment owners want to add info about their hardware, the habitat, height of camera, etc.

A Deployment object is tied to a Site (and possibly one or more Plots within a site). The Site model should capture metadata about its ecology, size and other attributes. It is suggested that we use an existing standard called the Ecological Metadata Language (EML) to define those metadata fields.

Resources: https://eml.ecoinformatics.org/ https://www.gbif.org/standards#:~:text=EML%3A%20Ecological%20Metadata%20Language&text=All%20of%20the%20descriptions%20of,The%20Knowledge%20Network%20for%20Biocomplexity https://www.gbif.org/sites/default/files/gbif_resource/resource-80640/gbif_metadata_profile_guide_en_v1.pdf

[annavik]

@mihow what backend changes are needed here? Do we need to specify the exact fields, or are you thinking we could save a generic object?

Example:

metadata: [
  { title: 'Habitat', value: 'Grassland' },
  { title: 'Camera height', value: 'Something' }
]

[mihow]

@annavik I think some of both. There will likely be a few standard fields that we can use throughout the interface for filtering, charts, etc. But additionally a generic object with any field the project owner's want to track.

If we start with a generic way of adding fields to a deployment that could be a good start. Another option is to start with a tagging system. Tags could be helpful for other data types like Occurrences & SourceImages as well.

Here is the notes doc for the Standards & Metadata working group. That's where we can decide on the standard fields: https://docs.google.com/document/d/17iTTSsXj36cW1FjXt1nviwZgWSTRSgfPpSDeMOBEj4Y/edit#heading=h.qd96mdxod0zo

I'm calling this ticket "in progress" as we discuss approaches and the fields.