dustymc
commented
1 year ago I will plan on proceeding with this about 2023-03-23 if there are no objections.
I will proceed immediately upon approval of each of the involved collections.
Data: temp_ucb_espm__university_of_california_berkeley.csv
Summary:
guid_prefix | numrecs
-------------+---------
MVZ:Bird | 2
Users:
ghaddr
@mkoo @ccicero
Instructions
This is a template to facilitate communication with the Arctos Code Table Committee. Submit a separate request for each relevant value. This form is appropriate for exploring how data may best be stored, for adding vocabulary, or for updating existing definitions.
Reviewing documentation before proceeding will result in a more enjoyable experience.
Initial Request
Goal: Describe what you're trying to accomplish. This is the only necessary step to start this process. The Committee is available to assist with all other steps. Please clearly indicate any uncertainty or desired guidance if you proceed beyond this step.
All UCB (ESPM): University of California Berkeley should be replaced with other ID type = other identifier and issued by agent University of California, Berkeley Environmental Science Policy and Management Teaching Collection
Proposed Value: Proposed new value. This should be clear and compatible with similar values in the relevant table and across Arctos.
Proposed Definition: Clear, complete, non-collection-type-specific functional definition of the value. Avoid discipline-specific terminology if possible, include parenthetically if unavoidable.
Context: Describe why this new value is necessary and existing values are not.
Table: Code Tables are http://arctos.database.museum/info/ctDocumentation.cfm. Link to the specific table or value. This may involve multiple tables and will control datatype for Attributes. OtherID requests require BaseURL (and example) or explanation. Please ask for assistance if unsure.
Collection type: Some code tables contain collection-type-specific values.
collection_cdemay be found from https://arctos.database.museum/home.cfmPriority: Please describe the urgency and/or choose a priority-label to the right. You should expect a response within two working days, and may utilize Arctos Contacts if you feel response is lacking.
Available for Public View: Most data are by default publicly available. Describe any necessary access restrictions.
Project: Add the issue to the Code Table Management Project.
Discussion: 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.
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).
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.
Review everything one last time. Ensure the How-To has been followed. Ensure all checks have been made by appropriate personnel.
Make changes as described above. Ensure the URL of this Issue is included in the definition.
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.