Asset Manager: Create project metadata

[dpsnowden]

Is your feature request related to a problem? Please describe.
It's not an existing problem, but the exact way in which metadata is either created or uploaded via Asset Manager is unclear.

Describe the solution you'd like

• User Interface to create and validate metadata for a new project (i.e. a new data set to be uploaded)

Describe alternatives you've considered

• Type new metadata into a web form that is based on a standard metadata schema (e.g. Makara?)
• Upload a file containing metadata in a format that complies with the standard (json/csv?)

Additional context
The amount of metadata is substantial so typing into a blank form is daunting and likely to be offputting.

• Are there tools out there that do this already?
• Is there community consensus on the standard format
• Can we provide tools that the user runs locally to help create and validate metadata
• Is the metadata already captured in other files so we can harvest from the raw audio or other config files?
• Overall we need a better understanding on where this metadata comes from operationally. What is essential at the very beginning of a project and what can be created or added during subsequent processing steps?

Streamline JSON schema so that it supports creation of Makara documents, but doesn't store same variable(s) multiple times. For instance, organization code should only be entered and stored once, but it's used to derive deployment ids.

@akbstone @xaviermouy @PedroWestendarp @tsgolden

Notes from Pedro here