General configurability

[aazaff]

We need the ability to submit configurable files that will validate

• [ ] Table names
• [ ] Field names
• [ ] Field Values - type (i.e., string) and vocabulary (i.e., geomaterials)
• [ ] Symbology

Technical components required would be...

• A way to cache config files/dictionaries client-side for real-time validation (is this really necessary?)
• A way to turn off real-time warnings and do ex post validation
• A persistent web service to query configuration files
• a format for configuration files.

Long term, we could seek funding to create an upload system, wherein other surveys using this tool could add their own dictionaries and glossaries to the master database.

[aazaff]

A full list of dictionaries that we expect to be included as validation sources. Some must be provided by AZGS and others can be taken from partners. Dagger (†) denotes a REQUIRED dictionary to be minimally compliant with GeMS or with our obligations to NGGDPP

Vocabularies

• GeoMaterials†
• Macrostrat Lithologies
• GeoSciML Lithologies†
• Mindat Minerals
• AZGS Glossary†
• Stratigraphic Names†
• Interval Names
• Taxonomic Names

Table Names and Attributes

Symbology

• FGDC Symbols†
• AZGS Symbols†