Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Whole organism part name - needs discussion #4771

Closed
Jegelewicz opened this issue Jun 16, 2022 · 4 comments
Closed

Whole organism part name - needs discussion #4771

Jegelewicz opened this issue Jun 16, 2022 · 4 comments
Labels
Aggregator issues e.g., GBIF, iDigBio, etc CodeTableCleanup Our bad data leads to more bad data. Fix it! Function-CodeTables

Comments

@Jegelewicz
Copy link
Member

Please read through #4758

Our current use of and definition for the part name whole organism is not being consistently applied.

whole organism - A contiguous alive or once living physical entity; entity or being that is or was living; an individual living or once living thing, such as one animal, plant, fungus, or bacterium. Wikidata

Issues to note are:

  1. Herbaria use "whole organism" for almost anything that is on a herbarium sheet, whether it is an entire plant or a branch with some leaves. There may be 5 sheets from the same plant in a single catalog record, so while the count of "whole organism" parts = 5, the individual count = 1
  2. @DerekSikes says - Some people think the key word is 'whole' as in 'undivided' whereas I think of it as meaning "the majority of the organism" so that if we take a leg off an insect and put it in a cryovial we'll have two parts: whole organism on a pin, leg in a vial.
  3. In most vertebrate collections, there is no whole organism part, just skin and skeleton or something like that. (Although it was the "whole organism" that was collected)
  4. It has been observed in may philosophical discussions of the TDWG Material;Sample Task Group that one can never really have a whole organism. An organism is more like a concept that describes a living thing from conception to dissolution via decay. Please read Primary Deliverable - MaterialSample definition tdwg/material-sample#2 (comment) and also Primary Deliverable - MaterialSample definition tdwg/material-sample#2 (comment) (and everything in between if you have a lot of time on your hands...)

So while Derek sees denormalization in creating both a whole organism with lot count of 1 and an individual count attribute of 1, I think the issue is really that we have confusing terms and definitions.

Using "whole organism" as a part name is not describing what we actually have for the majority of cases in which it is used (actually all, if you consider the organism to be what is described in 4 above).

Our definition for individual count is describing organisms NOT parts. Do we need to make that more clear?

individual count - The number of individual organisms represented by the catalog record. Github

To Derek's point, should we have something other than "whole organism" to appropriately describe the insect missing a leg, the fish in a jar missing a fin, or the herbarium sheet with only a branch, leaves, and flower on it? Should we even use this term as a part name at all?

Let the philosophizing begin....

Also - note that individual count is what shows up at aggregators in dwc:individualCount and is required for proper publication of DMNS:Inv data to OBIS. As far as I am aware, no other aggregators require this information, but given that this is the only place to precisely say - this record applies to x number of individual organisms - it would probably be good for all the biological collections to make good use of it.

@Jegelewicz Jegelewicz added Function-CodeTables Aggregator issues e.g., GBIF, iDigBio, etc CodeTableCleanup Our bad data leads to more bad data. Fix it! labels Jun 16, 2022
@DerekSikes
Copy link

DerekSikes commented Jun 16, 2022 via email

@dustymc
Copy link
Contributor

dustymc commented Jun 16, 2022

Should we even use this term as a part name at all?

I don't have a problem with it. I'm not a fan of the wiki definition, but I don't really have a better one to offer either. (We know it when we see it...) I'm not sure it's ever quite correct, even barring the always-extreme TDWG viewpoint, but it's a handy, accessible proxy to "most of the thing."

Moving "whole" to some part attribute would be a bit more correct and a bit less accessible - I don't see any reason to force that at this time.

The wiki definition is blocking any chance of getting a better one again, but I'm relatively certain that body is not intended to be interchangeable with "whole organism" - it's something about being skinned or something, and I think somehow differs from carcass, which is maybe-similar and also has an uninformative definition. I suppose we should do something drastic with #4368 if nobody wants to defend any of that.

most people would think

Users should not have to guess at our terminology. We have documentation, it should be read and understood by both people entering data and those trying to find stuff. That's not to say intuitive terms aren't awesome, but everyone should have the ability to KNOW what we mean by any term at any time.

@DerekSikes
Copy link

DerekSikes commented Jun 21, 2022 via email

@dustymc
Copy link
Contributor

dustymc commented Jun 21, 2022

individual

If we're changing, it would be nice to find something that works better for clonal organisms and such. Maybe body, but I'm not sure how the botanists might feel about that, nor what the current intention is. I'll start another Issue for that....

Something that incorporates object would be even better, but maybe that's too far.

@ArctosDB ArctosDB locked and limited conversation to collaborators Jul 18, 2022
@dustymc dustymc converted this issue into discussion #4833 Jul 18, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Aggregator issues e.g., GBIF, iDigBio, etc CodeTableCleanup Our bad data leads to more bad data. Fix it! Function-CodeTables
Projects
None yet
Development

No branches or pull requests

3 participants