Code Table Request - Add "processed for phytoliths"

WaigePilson commented 5 months ago

Initial Request

Goal

Add a preparation method of "processed for phytoliths" to the code table for preparation method (part attribute)

Context

Our UWBM Paleobotany and Paleobotany Reference collections contain numerous sediment/soil/plant specimens which have been used to extract phytolith (microscopic biogenic silica contained in plant tissues) content. This is a standardized set of lab procedures I need to be able to add this attribute to slide or residue parts which have been processed from the sediment sample to distinguish those parts from the geosample part parent, to note the date and name of the person who did the processing, etc.

Table

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

Proposed Value

processed for phytoliths

Proposed Definition

chemical and physical processing of rock, soil, or plant samples to produce residue of phytolith (biogenic amorphous silica) content; exact preparation methods may vary by lab (see e.g., Piperno, 1988; Strömberg, 2003), describe any precise method details in method.

Priority

High priority, I cannot import legacy parts data until this is resolved

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

[x] 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
[x] 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
[x] DBA - The request is functionally acceptable. The term is not a functional duplicate, and is compatible with existing data and code.
[x] 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.

Can a suitable solution be found here? If not, proceed to (2)
Can a suitable solution be found by Code Table Committee discussion? If not, proceed to (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.

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

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

WaigePilson commented 5 months ago

See also related issues #7799, issues #7800, issues #7801

Jegelewicz commented 5 months ago

Suggest simplifying to

processed for phytoliths

WaigePilson commented 5 months ago

Suggest simplifying to

processed for phytoliths

Agreed! I have updated

Jegelewicz commented 5 months ago

And also change

chemical and physical processing of rock, soil, or plant samples to produce residue of phytolith (biogenic amorphous silica) content; exact preparation methods may vary by lab (see e.g., Piperno, 1988; Strömberg, 2003), describe any precise method details in ~~remark~~ method.

WaigePilson commented 5 months ago

And also change

chemical and physical processing of rock, soil, or plant samples to produce residue of phytolith (biogenic amorphous silica) content; exact preparation methods may vary by lab (see e.g., Piperno, 1988; Strömberg, 2003), describe any precise method details in remark method.

done!

Nicole-Ridgwell-NMMNHS commented 5 months ago

I support this.

Jegelewicz commented 5 months ago

@dustymc this just needs your approval.

WaigePilson commented 4 months ago

@dustymc does this have approval? thank you!

Jegelewicz commented 4 months ago

added

ArctosDB / arctos