Arctos: cleanup request: age_class

[dustymc]

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

it's a mess

adult, juvenile
adult/juvenile
adult (queen)

egg
egg(s)

I'm not sure egg (and cyst and probably some other stuff) is a age_class at all - just a part, or we need a "development_stage," or ?????????????

[acdoll]

I've started a google sheet to work through this:
https://docs.google.com/spreadsheets/d/1fnnKQxADOVaRiLy9mQcVZgmMPSB1CL1D1-hhQ3ML5go/edit#gid=0

[dustymc]

Thanks @acdoll !

For lots, I still think there are two viable approaches

• add minimum_.... and maximum_... like we've done for total length. This is firmly in 'cataloging the wrong thing' territory, but it's explicit and not mixed in with other kinds of data. I'm not sure it's relevant for this, at least not when we're mixing concepts.

• just assert whatever's included, which facilitates searching. Age class=adult; age class=juvenile; age_class=20 more things fits in the Arctos model and provides an expected pathway to the data.

I'd probably go with the second option for uncertainty as well - "I think it's an adult (on date using technique)" and "I think it's a juvenile (on date using technique)" on the same record fit in the model, provide an expected path to the data, and adequately express what's being asserted.

[ccicero]

Discussed at Code Table WG meeting 1/21/2021. Wait until after the Bird Data Harmonization Workshop to be held in Feb by Carla Town Peterson, and John Bates. See what recommendations come out of the workshop. Carla will ask Dusty for bird age data in Arctos, which has four age attribute fields: age, age class, skull ossification, numeric age.

[campmlc]

Also need to consider invertebrate age classes. Plants?

On Thu, Jan 21, 2021 at 2:55 PM Carla Cicero [e-mail]
wrote:

• [EXTERNAL]*

Discussed at Code Table WG meeting 1/21/2021. Wait until after the Bird
Data Harmonization Workshop to be held in Feb by Carla Town Peterson, and
John Bates. See what recommendations come out of the workshop. Carla will
ask Dusty for bird age data in Arctos, which has four age attribute fields:
age, age class, skull ossification, numeric age.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/2881#issuecomment-764966534,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ7JBGEPJDOXOETBJYYINDS3CPGDANCNFSM4OR2CARQ
.

[Jegelewicz]

See also https://github.com/ArctosDB/arctos/issues/1214

[ccicero]

Maybe rather than 'age class' it should be 'life stage' per DwC? That would broaden the category across different taxonomic groups, and apply to 'egg', plants, etc.

[dustymc]

@ccicero any news?

I think perhaps we need both life stage and age class. I was going to elaborate, but I don't think I can while we have a bunch of apparent duplicates and undocumented values, so can we tackle the easy cleanup first?

Does anyone object to moving all of the two-value terms to two determinations?

adult, juvenile-->add adult, add juvenile, delete
adult/juvenile-->add adult, add juvenile, delete
adult, pupa-->add adult, add pupa, delete
adults, larva-->add adult, add larva, delete
chrysalis, juvenile shed-->add chrysalis, add juvenile (remark="shed"), delete
chrysalis, larva-->add chrysalis, add larva, delete
cocoon, larva-->add cocoon, add larva, delete
egg, larva-->add egg, add larva, delete
larva, nymph-->add larva, add nymph, delete
puparium, larva-->add puparium, add larva, delete
teneral, puparium-->add teneral, add puparium, delete

I think these are just lost:

adult (queen)-->add adult, add "queen" in https://arctos.database.museum/info/ctDocumentation.cfm?table=ctcaste, delete
queen-->move to "queen" in https://arctos.database.museum/info/ctDocumentation.cfm?table=ctcaste, delete

These seem non-contentious:

sub-adult-->change to subadult
egg(s)-->change to egg
cyst(s)-->change to cyst

May I?

[Jegelewicz]

Those all look like good ideas to me.

[ewommack]

That makes sense to me.

[dustymc]

The lowest-hanging fruit has been plucked.

I started a spreadsheet for what's left

https://docs.google.com/spreadsheets/d/1Yv3Lx6DtSdmh0P1cSIG6zW-DnYI6VDJpOkFcgQL6F8o/edit?usp=sharing

It's a little overwhelming and I'm not sure where to go next - maybe actionable definitions for everything, then figure out how many THINGS we have, then try to merge/split as necessary? That might involve writing a lot of definitions for things that should not survive this process.

I mapped some stuff to 'age class' but now I think maybe those are just all just numeric age with unnecessary complexity.

https://arctos.database.museum/info/ctDocumentation.cfm?table=ctattribute_type#age exists; suggest we push any non-research grade data to it - eg "pup" may mean something and be useful for specialists, but that doesn't mean we must have many ways of saying "very young" in this particular table.

Generally, I think we need better documentation for creating attributes, particularly on using method, and need to consider that when creating/defining authorities. (See also https://github.com/ArctosDB/arctos/issues/3516). "Juvenal" for instance seems to be "juvenile; method=feather development."

[dustymc]

How do we revive this?

[Jegelewicz]

Next Code Table committee...

[dustymc]

I'll ratchet the priority up a bit more - this minimally needs documentation, see https://github.com/ArctosDB/arctos/issues/1450