Fields for birth date and wean date?

[cjconroy]

I am cataloging some old lab colony animals. We happen to have birth, wean and death dates. The death date will be THE date for these animals. We also obviously have age in days. But, where do people stick birth or wean dates? Specimen remark? Collecting event remark? I am not lobbying for another attribute! Just thought I would put them in where others have set a precedent.

[campmlc]

We do need explicit birth and death dates for captive animals, including zoo animals. We have these data scattered across multiple fields, so not an easy way to find them. Mostly they are are collection object remarks; also in record attribute "age" remarks, also in "verbatim preservation date" - which is not the same as death date.
These would be best as record attributes - I am lobbying for that.

[dustymc]

Birth can be calculated from death and age, but I wouldn't want to try to search that. (A bot could help if we had a place for the result.)

"Best" as in least-ambiguous and capable of carrying the most information would be an Event, but that might be wild overkill.

I am not lobbying for another attribute!

That's the usual target and I don't have any better suggestions at the moment.

I suspect "correct" is something like a LIMS where you could record lots more than just dates, but that is of course way off in 'new development' land. If we ever get there, the entomologists might bring a lot to the table.

"verbatim preservation date" - which is not the same as death date.

The date the specimen ceased to grow and change, as opposed to the date when it was collected. Often the date of death. Avoid this in favor of additional specimen_event determinations.

[Jegelewicz]

Even if it seems like overkill - I would vote for events. Eventually, someone will show up (the zoo) with "I know exactly where and when this organism was born, weaned, had its own offspring, died, and whatever else happens to an organism over the course of its life". An attribute would work - but it doesn't allow for capturing place information.

Either way, these are code table requests (birth, weaning) that would need definitions.

Two new event types
or
Two record attribute types

[campmlc]

Are we allowing multiple events in an initial bulkload file? Because doing a separate events bulkload to add a single date greatly complicates data entry in terms of time, workflow, and staff resources.

…

On Mon, Apr 10, 2023 at 10:27 AM Teresa Mayfield-Meyer < ***@***.***> wrote: * [EXTERNAL]* Even if it seems like overkill - I would vote for events. Eventually, someone will show up (the zoo) with "I know exactly where and when this organism was born, weaned, had its own offspring, died, and whatever else happens to an organism over the course of its life". An attribute would work - but it doesn't allow for capturing place information. Either way, these are code table requests (birth, weaning) that would need definitions. Two new event type <https://arctos.database.museum/info/ctDocumentation.cfm?table=ctspecimen_event_type> s or Two record attribute type <https://arctos.database.museum/info/ctDocumentation.cfm?table=ctattribute_type> s — Reply to this email directly, view it on GitHub <#6110 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADQ7JBBX5GLAXDEASPCXW7DXAQYGDANCNFSM6AAAAAAWW6VHQA> . You are receiving this because you commented.Message ID: ***@***.***>

[Jegelewicz]

Are we allowing multiple events in an initial bulkload file?

If we hurry - we can change that now, otherwise it is one and done then the rest have to loaded using the event loader.

[dustymc]

No recent activity, tabling.