-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Code Table Additions - Reproductive Data #5264
Comments
We should be removing the constraint on the number of attributes that can
be loaded through the bulkloader, so this is good timing!
Any chance you can provide the exact terms and their definitions, plus
maybe a link to some documentation on how these are obtained, so we can add
to the code table?
…On Tue, Nov 8, 2022 at 12:11 PM Jonathan Dunnum ***@***.***> wrote:
* [EXTERNAL]*
Issue Documentation is
http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html
*Is your feature request related to a problem? Please describe.*
Current structure doesn't allow for full parsing of the varied
reproductive data we collect. There is a large initiative to capture and
serve trait data. This would improve that capability.
*Describe what you're trying to accomplish*
Would like more fields for reproductive trait data. Basically all of our
data are currently in the "Reproductive data" or "Specimen remarks" fields.
*Describe the solution you'd like*
Currently Arctos has the following fields: "Reproductive data", "crown
rump length", "left gonad length", "left gonad width", "right gonad
length", "right gonad width", "gonad", "gonad weight", and "ovum".
We would like some iteration of the following: Testes - scrotal/abdominal,
testis length, testis width (we have not discriminated between left and
right historically), vagina - open/closed, nipples - small/enlarged,
lactating/not lactating, pregnant - yes/no, embryos - yes/no, placental
scars - yes/no, number of embryos/scars left horn, number of embryos/scars
right horn
*Describe alternatives you've considered*
The alternative is to leave all repro data in a single free text field.
Not ideal.
*Additional context*
Current efforts will soon be underway in many Arctos hosted collections to
capture trait data so now is a good time to standardize this and get these
data out of the free text fields if possible
*Priority*
High
—
Reply to this email directly, view it on GitHub
<#5264>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ7JBC6KH5VAU7UOE47HE3WHKQUHANCNFSM6AAAAAAR2U5BO4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Absolutely impossible, see #5193 - which might be going active in the next week or so and then will be locked for some number of years. |
Here are some definitions for the requested attributes. Reproductive attributes Feature Request - (Issue #5264) |
This also is like #4533 We need to make sure they are useful and defined well by the user community. |
These terms have been added to the list of existing terms for the RANGES team to consider. I am going to close this issue. If any of these terms needs to be requested, please request each separately using the code table request template. |
Hi @Jegelewicz, I would like to re-open this issue in advance of our RANGES (#5532) start date of 1 May 2023. There is an urgent need for the Arctos community to weigh in on trait terms and it would be great to standardize at the outset of the digitization process. When could we convene? |
Teresa J. Mayfield-Meyer |
I think this is now addressed via individual code table issues - closing. |
Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html
Is your feature request related to a problem? Please describe.
Current structure doesn't allow for full parsing of the varied reproductive data we collect. There is a large initiative to capture and serve trait data. This would improve that capability.
Describe what you're trying to accomplish
Would like more fields for reproductive trait data. Basically all of our data are currently in the "Reproductive data" or "Specimen remarks" fields.
Describe the solution you'd like
Currently Arctos has the following fields: "Reproductive data", "crown rump length", "left gonad length", "left gonad width", "right gonad length", "right gonad width", "gonad", "gonad weight", and "ovum".
We would like some iteration of the following: Testes - scrotal/abdominal, testis length, testis width (we have not discriminated between left and right historically), vagina - open/closed, nipples - small/enlarged, lactating/not lactating, pregnant - yes/no, embryos - yes/no, placental scars - yes/no, number of embryos/scars left horn, number of embryos/scars right horn
Describe alternatives you've considered
The alternative is to leave all repro data in a single free text field. Not ideal.
Additional context
Current efforts will soon be underway in many Arctos hosted collections to capture trait data so now is a good time to standardize this and get these data out of the free text fields if possible
Priority
High
The text was updated successfully, but these errors were encountered: