Closed campmlc closed 1 year ago
Changed the code table to https://arctos.database.museum/info/ctDocumentation.cfm?table=ctexamined_detected
Looks fine. Checked.
I was writing an update to the definition
Acari is an historical Arachnid subclass that includes mites and ticks. Use a more specific value (mite or tick) if known.
Do we actually need this? I mean does someone have data or are mite and tick enough? I'm unchecking until I feel like this option is required....
Yes, we have data. It is very difficult for anyone not a trained specialist to tell larval ticks and adult mites apart. Most of the mite/ticks being cataloged right now are getting named as Acari, even though it is legacy in the sense that there are multiple groups that cannot be given a more phylogenetically correct name based on current taxonomy. Any you know what the state of current mite taxonomy is. This option is required: please proceed with this so I can finalize this version of the TPT project.
canonical name: Acari
name string: Acari Leach 1817
Classification:
display_name: Acari
nomenclatural_code: ICZN
scientific_name: Acari
source_authority: ITIS
taxon_status: valid
Classification:
aphiaid: 1349
display_name: Acarina
nomenclatural_code: ICZN
remark: Autogenerated from relationship "synonym of." Authority: WoRMS. Source Classification: WoRMS (via Arctos)
scientific_name: Acarina
source_authority: WoRMS (2018). Acarina. Accessed at: http://www.marinespecies.org/aphia.php?p=taxdetails&id=1349 on 2018-12-17
taxon_status: invalid
Classification:
display_name: Acarina
nomenclatural_code: ICZN
remark: Autogenerated from relationship "synonym of." Authority: WoRMS. Source Classification: Arctos
scientific_name: Acarina
source_authority: U. S. Nat. Parasite Collection
taxon_status: valid
Classification:
canonical name: Acari
name string: Acari
Classification:
canonical name: Acari
name string: Acari
Classification:
canonical name: Acari
name string: Acari
Classification:
canonical name: Acari
name string: Acari
Classification:
TPT Taxon ID: acari_1
managed_by: jegelewicz
preferred_name: Acari
remark: TPT scientificName: Acari
source_authority: https://github.com/njdowdy/tpt-taxonomy/blob/main/Acari/Acari-standardized-v2.csv
Classification:
canonical name: Acari
name string: Acari (awaiting allocation)
Classification:
canonical name: Acari
name string: Acari Leach 1817
Classification:
canonical name: Acari
name string: Acari Leach 1817
Classification:
aphiaid: 292684 [refresh]
author_text: Leach, 1817
display_name: Acari Leach, 1817
nomenclatural_code: ICZN
scientific_name: Acari
source_authority: WoRMS (2018). Acari. Accessed at: http://www.marinespecies.org/aphia.php?p=taxdetails&id=292684 on 2018-12-18
taxon_status: extant
taxon_status: valid
Classification:
canonical name: Acari
name string: Acari Leach, 1817
Classification:
I'm with @Jegelewicz on this, I'd like to see data that's ready to use this, not anything theoretical or mired in some inappropriate place.
I will suggest that "mite or tick" is an appropriate way to say "mite or tick." Acari (as a taxon name) clearly implies some constantly-evolving circumscription, this (I thought) was meant to be something else, now I'm not sure.
Here are data that have already been cataloged: https://arctos.database.museum/search.cfm?guid_prefix=MSB%3APara&customoidoper=LIST&taxon_name=acari But there are many more hidden in various collection object and part remarks fields.
If you want to replace "Acari" with "ectoparasite: mites or tick" or "mites/ticks" - that could work.
@dustymc approve as edited?
added
Initial Request
Goal:
Add ectoparasite: Acari to the Examined_Detected code table:
Proposed Values:
ectoparasite: Acariectoparasite: mite or tick
Proposed Definitions:
ectoparasite: Acari : "Legacy Arachnid subclass of mites and ticks, unspecified. Use a more specific value (mite or tick) if known."Unable to determine if the detected item is a mite or tick. Use a more specific value (mite or tick) if known.
Context:
These values are being added the Examined_Detected code table to capture existing data in Arctos, to accommodate ongoing research which will be populating these attributes going forward, and for TPT digitization and host linkage. The current attributes "ectoparasite examination" and "ectoparasite detected" will be migrated to these new attributes. Splitting from https://github.com/ArctosDB/arctos/issues/6260 .
Table:
https://arctos.database.museum/info/ctDocumentation.cfm?table=ctattribute_code_tableshttps://arctos.database.museum/info/ctDocumentation.cfm?table=ctexamined_detectedPriority:
High. Needed for TPT Arctos and MSB funding, and for upcoming presentation at American Society of Parasitology meetings July 13-15, 2023.
Available for Public View:
Yes
Project:
Add the issue to the Code Table Management Project.
Discussion:
@jldunnum @campmlc @acdoll @bryansmclean
https://github.com/orgs/ArctosDB/teams/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).
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.
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.
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.