Skip to content

Dataset Metadata - Metadata fields need to be organized properly, grouped together, hidden if empty, denoted if required #197

@eaquigley

Description

@eaquigley

Author Name: Mike Heppler (@mheppler)
Original Redmine Issue: 3609, https://redmine.hmdc.harvard.edu/issues/3609
Original Date: 2014-03-03
Original Assignee: Kevin Condon


The dynamic fields seem to be lacking any organization. Fields should be organized properly, grouped together, hidden if empty, denoted if required.

Special/grouped formatting is required for fields like Version Date or Geographic Bounding Box, with additional help text (ie: date format examples) or even different field input types, depending on the type of data they're expecting.

[eleni: For the requirements of these fields please consult the following tables. The requirements for: order of the fields, if they're required*, should be shown in the UI, type of field, etc is all represented in the tables:

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions