Skip to content
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

Closed
jldunnum opened this issue Nov 8, 2022 · 8 comments
Closed

Code Table Additions - Reproductive Data #5264

jldunnum opened this issue Nov 8, 2022 · 8 comments
Labels
Enhancement I think this would make Arctos even awesomer! Function-CodeTables

Comments

@jldunnum
Copy link

jldunnum commented Nov 8, 2022

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

@jldunnum jldunnum added the Enhancement I think this would make Arctos even awesomer! label Nov 8, 2022
@campmlc
Copy link

campmlc commented Nov 8, 2022 via email

@dustymc
Copy link
Contributor

dustymc commented Nov 8, 2022

constraint on the number of attributes that can be loaded through the bulkloader,

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.

@jldunnum
Copy link
Author

jldunnum commented Jan 5, 2023

Here are some definitions for the requested attributes.

Reproductive attributes Feature Request - (Issue #5264)
testes: scrotal/abdominal [scrotal - testes descended into scrotum; abdominal – testes undescended, still in abdomen]
testis length: [number] mm [length of longest aspect of testis]
testis width: [number] mm [length of shortest aspect of testis]
vagina: open/closed [open - vagina perforated; closed – vagina sealed]
nipples: small/enlarged
lactating: yes/no [milk expressible from nipples]
pregnant: yes/no
placental scars: yes/no [Placental scars are pigmented areas found at former sites of implantation in the uterine wall]
embryos in left uterine horn: [number]
embryos in right uterine horn: [number]
placental scars in left uterine horn: [number]
placental scars in right uterine horn: [number]

@Jegelewicz
Copy link
Member

This also is like #4533

We need to make sure they are useful and defined well by the user community.

@Jegelewicz Jegelewicz changed the title Feature Request - Code Table Additions - Reproductive Data Jan 10, 2023
@Jegelewicz
Copy link
Member

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.

@bryansmclean
Copy link

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?

@bryansmclean bryansmclean reopened this Apr 13, 2023
@Jegelewicz
Copy link
Member

Arctos RANGES Team,

Bryan has asked that we meet - please provide your availability in this When2Meet By tomorrow afternoon so that I can select a time when most of you can attend.

Adios,

Teresa J. Mayfield-Meyer

@Jegelewicz
Copy link
Member

I think this is now addressed via individual code table issues - closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement I think this would make Arctos even awesomer! Function-CodeTables
Projects
None yet
Development

No branches or pull requests

5 participants