Closed KatherineLAnderson closed 3 months ago
Here is the macrostrat: https://macrostrat.org/sift/#/strat_name_concept/31429
@Nicole-Ridgwell-NMMNHS this is outside the US - should we set up any rules for that stuff?
The British Geological Survey has a lexicon, we can use that: https://webapps.bgs.ac.uk/lexicon/lexicon.cfm?pub=OXC
added under special exemption
Initial Request
Goal
Add Oxford Clay Formation to the lithostratigraphic formation code table
Context
It doesn't yet exist in the code table!
Table
https://arctos.database.museum/info/ctDocumentation.cfm?table=ctlithostratigraphic_formation
Proposed Value
Oxford Clay Formation
Proposed Definition
A Jurassic marine sedimentary unit that underlies southeast England. British Geological Survey: https://webapps.bgs.ac.uk/lexicon/lexicon.cfm?pub=OXC
see https://en.wikipedia.org/wiki/Oxford_ClayCollection type
paleo
Attribute Extras
Attribute data type
n/a
Attribute controlled values
n/a
Attribute units
n/a
Part preservation attribute affect on "tissueness"
n/a
Priority
high priority (needed for data migration)
Example Data
Available for Public View
yes
Helpful Actions
[x] Add the issue to the Code Table Management Project.
[x] Please reach out to anyone who might be affected by this change. Leave a comment or add this to the Committee agenda if you believe more focused conversation is necessary.
@ArctosDB/arctos-code-table-administrators @Nicole-Ridgwell-NMMNHS
Approval
All of the following must be checked before this may proceed.
_The How-To Document should be followed. Pay particular attention to terminology (with emphasis on consistency) and documentation (with emphasis on functionality). No person should act in multiple roles; the submitter cannot also serve as a Code Table Administrator, for example._
Rejection
If you believe this request should not proceed, explain why here. Suggest any changes that would make the change acceptable, alternate (usually existing) paths to the same goals, etc.
Implementation
Once all of the Approval Checklist is appropriately checked and there are no Rejection comments, or in special circumstances by decree of the Arctos Working Group, the change may be made.
[x] Review everything one last time. Ensure the How-To has been followed. Ensure all checks have been made by appropriate personnel.
[x] Add or revise the code table term/definition as described above. Ensure the URL of this Issue is included in the definition. URLs should be included as text, separated by spaced pipes. Do not include HTML in definitions.
Close this Issue.
DO NOT modify Arctos Authorities in any way before all points in this Issue have been fully addressed; data loss may result.
Special Exemptions
In very specific cases and by prior approval of The Committee, the approval process may be skipped, and implementation requirements may be slightly altered. Please note here if you are proceeding under one of these use cases.