Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Code Table Request - new attribute: antler points #6175

Closed
4 tasks done
Jegelewicz opened this issue Apr 21, 2023 · 13 comments
Closed
4 tasks done

Code Table Request - new attribute: antler points #6175

Jegelewicz opened this issue Apr 21, 2023 · 13 comments
Labels
Function-CodeTables Priority-High (Needed for work) High because this is causing a delay in important collection work..
Milestone
Needs Documentation

Comments

@Jegelewicz
Copy link
Member

Jegelewicz commented Apr 21, 2023 •
edited
Loading

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.

NCWRC maintains data on deer and needs this value to be able to report expected information to those interested in deer populations. See also https://github.com/ArctosDB/data-migration/issues/889#issuecomment-1516850746 and related comments in that issue.

Proposed Value: Proposed new value. This should be clear and compatible with similar values in the relevant table and across Arctos.

antler pointstotal see #6175 (comment)

Proposed Definition: Clear, complete, non-collection-type-specific functional definition of the value. Avoid discipline-specific terminology if possible, include parenthetically if unavoidable.

Total number of points on one (method = left or right) or both (method = total) antlers that are at least 1” in length, including the tips of the beams. Total, left, or right should be included in method to provide details about what the count describes.

Units

https://arctos.database.museum/info/ctDocumentation.cfm?table=ctcount_units

Context: Describe why this new value is necessary and existing values are not.

There currently are no antler measurement attributes.

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=ctattribute_type

Collection type: Some code tables contain collection-type-specific values. collection_cde may be found from https://arctos.database.museum/home.cfm

Mamm
Teach

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.

Available for Public View: Most data are by default publicly available. Describe any necessary access restrictions.

yes

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.

@ArctosDB/arctos-code-table-administrators

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).

  • Code Table Administrator[1] - check and initial, comment, or thumbs-up to indicate that the request complies with the how-to documentation and has your approval
  • Code Table Administrator[2] - check and initial, comment, or thumbs-up to indicate that the request complies with the how-to documentation and has your approval
  • DBA - The request is functionally acceptable. The term is not a functional duplicate, and is compatible with existing data and code.
  • DBA - Appropriate code or handlers are in place as necessary. (ID_References, Media Relationships, Encumbrances, etc. require particular attention)

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.

  1. Can a suitable solution be found here? If not, proceed to (2)
  2. Can a suitable solution be found by Code Table Committee discussion? If not, proceed to (3)
  3. Take the discussion to a monthly Arctos Working Group meeting for final resolution.

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.

  1. Adding an existing term to additional collection types may proceed immediately and without discussion, but doing so may also subject users to future cleanup efforts. If time allows, please review the term and definition as part of this step.
  2. The Committee may grant special access on particular tables to particular users. This should be exercised with great caution only after several smooth test cases, and generally limited to "taxonomy-like" data such as International Commission on Stratigraphy terminology.
@Jegelewicz Jegelewicz added Priority-High (Needed for work) High because this is causing a delay in important collection work.. Function-CodeTables labels Apr 21, 2023
@ccicero
Copy link

ccicero commented May 18, 2023

@Jegelewicz At Code Table meeting 18 May 2023, we discussed having one value for 'antler points' and then putting the details (total, left, right) in methods. Is that acceptable?

This was referenced May 18, 2023
Closed
Closed
@Jegelewicz
Copy link
Member Author

@hkevans see above.

@Jegelewicz
Copy link
Member Author

Jegelewicz commented Jun 29, 2023 •
edited
Loading

@hkevans can we add a single attribute for antler points and you can put the side or total in method?

@dustymc
Copy link
Contributor

dustymc commented Jun 29, 2023

remarks

Method!

@Jegelewicz
Copy link
Member Author

Method!

It is going to be free text where-ever it goes and no matter what we say it is going to end up in both places....

@hkevans
Copy link

hkevans commented Jun 29, 2023 via email

@dustymc
Copy link
Contributor

dustymc commented Jun 29, 2023

It is going to be free text where-ever it goes and no matter what we say it is going to end up in both places....

I don't (want to) believe it, and in any case the fault should not be on "us" giving bad or inconsistent advice.

@hkevans multiple attributes of the same type.

@Jegelewicz
Copy link
Member Author

Would I add multiple attributes under the same category or one attribute and then descriptions for both sides?

I agree with @dustymc multiple attributes of the same type.

@hkevans
Copy link

hkevans commented Jun 30, 2023 via email

@Jegelewicz Jegelewicz changed the title Code Table Request - new attribute: antler points total Code Table Request - new attribute: antler points ~~total~~ Jun 30, 2023
@Jegelewicz Jegelewicz changed the title Code Table Request - new attribute: antler points ~~total~~ Code Table Request - new attribute: antler points Jun 30, 2023
@Jegelewicz
Copy link
Member Author

@ccicero I made changes to the term and definition. Please indicate code table admin approval by checking a box!

@dustymc you Ok with revisions?

@Jegelewicz Jegelewicz added this to the Needs Documentation milestone Jun 30, 2023
@dustymc
Copy link
Contributor

dustymc commented Jun 30, 2023

I'm a little hesitant about "at least 1” in length" - I'm not sure how universal that is (I think even B&C WTD has a ratio exception), but it can also be adjusted if someone has a need so my checks can stay.

@Jegelewicz
Copy link
Member Author

OK by @cicero and @Nicole-Ridgwell-NMMNHS in today's code table meeting.

@Jegelewicz
Copy link
Member Author

Added and restricted to ctcount_units

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Function-CodeTables Priority-High (Needed for work) High because this is causing a delay in important collection work..
Projects
None yet
Milestone
Needs Documentation
Development

No branches or pull requests
4 participants
@ccicero @dustymc @Jegelewicz @hkevans