Metadata schemas for VAMS databases

[archieco]

Description of changes:

Earlier this year, VAMS gained a feature enabling users to store metadata about their Assets. The metadata was in the form of an arbitrary set of keys and values as determined by the user. While this model helps users store helpful information, it does not manage consistency of information across assets. With this change, VAMS administrators can define a metadata schema enabling consistent information to be collected across assets. Metadata fields are defined by the admin on a VAMS database-by-database level. So, different databases can support different metadata schemas.

The types of fields supported include the following:

• text or strings
• long text or text area fields
• numeric fields
• date fields
• boolean fields or checkboxes
• select lists
• locations

Moreover, select lists can take the form of controlled lists, sometimes called controlled vocabularies, with interdependent selections across the fields. As an example, location data may be provided as the dataset of controlled values enabling the administrator to enable users to select from a limited list of cities after they have selected a country. Or, to define variables automatically on the user's behalf by automatically selecting values from the dataset after the user has selected another option, like automatically selecting a country once a city is selected.

A controlled list dataset is defined by the VAMS administrator in the form of a CSV file upload in the context of the metadata schema definition.

Polygons may be drawn on a map to specify a location using react-map-gl, amplify geo, and Amazon Location Service. Coordinate data is captured for the center of the map, zoom level, and coordinates of the polygon points.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.