Jegelewicz
commented
2 months ago Patrick,
In an attempt to normalize our part names and remove confusing information, we are looking to remove sternal from the part name list in Arctos. Your collection is the only one using this term. Please see the Github issue here.
If you have a strong objection to this change, please comment there, otherwise let us know if we can make this change for you, or if you make the change, let us know so that we can remove the term from the code table.
Thank you!
Teresa J. Mayfield-Meyer
KatherineLAnderson
Nicole-Ridgwell-NMMNHS
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.
Remove confusing or duplicate part names
Context
Describe why this new value is necessary and existing values are not.
Sternum and sternal are overlapping and people won't find what they are looking for, in addition, sternal also exists in the part modifier table.
Sternal is only used in four records:
https://arctos.database.museum/guid/UTEP:ES:32-143 https://arctos.database.museum/guid/UTEP:ES:60-31 https://arctos.database.museum/guid/UAM:ES:12835 https://arctos.database.museum/guid/UAM:ES:13436
For the UTEP records, I changed the parts to sternum and added the part modifier sternal, if we can change the UAM parts, the part would no longer be in use and could be removed from the code table.
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.
https://arctos.database.museum/info/ctDocumentation.cfm?table=ctspecimen_part_name
Proposed Value
Proposed new value. This should be clear and compatible with similar values in the relevant table and across Arctos.
sternalProposed Definition
Clear, complete, non-collection-type-specific functional definition of the value. Avoid discipline-specific terminology if possible, include parenthetically if unavoidable.
N/A - remove from the code table
Collection type
_Some code tables contain collection-type-specific values.
collection_cdemay be found from https://arctos.database.museum/home.cfm_Attribute Extras
Attribute data type
If the request is for an attribute, what values will be allowed? free-text, categorical, or number+units depending upon the attribute (TBA)
Attribute controlled values
If the values are categorical (to be controlled by a code table), add a link to the appropriate code table. If a new table or set of values is needed, please elaborate.
Attribute units
if numerical values should be accompanied by units, provide a link to the appropriate units table.
Part preservation attribute affect on "tissueness"
if a new part preservation is requested, please add the affect it would have on "tissueness": No Influence, Allows, or Denies
Priority
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.
let's not let this get used again
Example Data
Requests with clarifying sample data are generally much easier to understand and prioritize. Please attach or link to any representative data, in any form or format, which might help clarify the request.
Available for Public View
Most data are by default publicly available. Describe any necessary access restrictions.
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 @mvzhuang
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.
[ ] Review everything one last time. Ensure the How-To has been followed. Ensure all checks have been made by appropriate personnel.
[ ] 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.