Code Table Request - New part atribute type (ctpreparation_method): 10–30 µmol photons m−2 s−1

RJSS8 commented 5 months ago

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.

Add a new preparation method needed for the parts in our collection.

Context

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

Being that it's specific to its part and a piece of integral information needed and also used for organization between our collection specimens.

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

Proposed Value

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

10–30 µmol photons m−2 s−1

Proposed Definition

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

The term “µmol photons m⁻² s⁻¹” refers to the number of photosynthetically active photons (individual particles of light in the 400-700 nm range) delivered to a specific area over a 24-hour period. It is commonly used to describe the light environment for plants. In this case, it represents the light intensity interval which strains in our collection are kept in

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.

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

[ ] Add the issue to the Code Table Management Project.
[ ] 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). No person should act in multiple roles; the submitter cannot also serve as a Code Table Administrator, for example._

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

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.

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

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.

dustymc commented 5 months ago

I'm not sure how (or if) this is related to https://github.com/ArctosDB/arctos/issues/7905.

Perhaps a meeting to flesh out the big picture would be useful.

At first glance this looks like it might belong in https://arctos.database.museum/info/ctDocumentation.cfm?table=ctcoll_event_attr_type

Jegelewicz commented 5 months ago

I don't think this has anything to do with collecting event - it is the way a cell culture is maintained.

dustymc commented 5 months ago

way a cell culture is maintained

water temperature [ link ]

relative humidity [ link ]

It's (maybe!) the same sort of information at those things, maybe it belongs in the same place.

Jegelewicz commented 5 months ago

It does not happen during the event - it is an attribute of how the culture is maintained or stored over time.

Nicole-Ridgwell-NMMNHS commented 5 months ago

This seems more akin to container environment?

Jegelewicz commented 5 months ago

This seems more akin to container environment?

IF you are using object tracking....and they are not.

RJSS8 commented 5 months ago

@dustymc we can set up a meeting for you to understand what going on and why I'm making so many requests and these specific requests. Please let me know when you're available. Please take into account that I live in Portugal and as such there is quite a time difference but I'm sure we can make it work.

Jegelewicz commented 4 months ago

@ArctosDB/arctos-code-table-administrators this collection would like to get some data entered, but needs new terms. I am unable to make the meeting on Thursday due to family obligations. Can we discuss this asynchronously and get them moving?

dustymc commented 4 months ago

@ArctosDB/arctos-code-table-administrators discussed https://docs.google.com/document/d/1eZ_S8VTp-m5Wrbb6cAK96ODPZpt2-Hvnvt6yfU9qVwg/edit#heading=h.b75kqv2tbpim

yes this is ideally container environment (where the container is a room), but collection does not use object tracking, this is (or very nearly is) the only value.

These data are very much like https://arctos.database.museum/info/ctDocumentation.cfm?table=ctspecpart_attribute_type#storage_temperature.

@RJSS8 is also open to condition report, suspect searching the data isn't critical

Conclusion: close this, new condition report issue, closing.

ArctosDB / arctos