Bug #2037
openPromoting Data/Metadata
0%
Description
Promoting Data/Metadata
- Please add any clarifications/comments that any of you may have **
A) as part of the UI Generation process, need to:
1) inspect incoming table(s) for temporal fields
2) determine which if any go to temporal metadata [**SEE NOTE 1**]
3) repeat for spatial fields
4) repeat for taxonomic coverage
5) temporarily record these assignments in "additional metadata" section of the
EML doc
B) as part of the merging process, need to:
1) during the merge, use this info that was put into "additional metadata" to
pull out the correct values from the predefined data table columns, and use
them to populate the metadata (ie temporal, geographic and taxonomic coverage
sections)
2) IMPORTANT: on finish, delete the "additional metadata" section that we added
**NOTE 1: we are anticipating that the form designer (through the use of rules)
would somehow define which columns should subsequently be used for promoting to
metadata. Note that there are some potential difficulties with these definitions
- for example, timestamps may be spread over sevaral columns (for example -
separate columns for year, month, day, time), so the rules and the markup added
to "additional metadata" should be rich enough to define such combinations of
columns etc, and define which values to use (eg "the minimum value of combined
cols a, b and c" etc). Needs some careful consideration
**NOTE 2: As a first pass, restrict designer to using fields that are explicitly
included in the data (denormalized) - not data referenced via foreign key
constraints etc
Related issues