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

Missing types in MovementBirthEventResource #183

Closed
dirbSEGES opened this issue Jan 25, 2021 · 5 comments
Closed

Missing types in MovementBirthEventResource #183

dirbSEGES opened this issue Jan 25, 2021 · 5 comments

Comments

@dirbSEGES
Copy link

dirbSEGES commented Jan 25, 2021

Hi,

where are missing som types to descripe following:

StateofbirthType:
Defective calf
Live calf
Live calf, born prematurely
Died within 1 day
Died after 1 day
Stillborn
Abortion
Culled at birth

SizeatbirthType:
Little
Below average
Above average
Big

It is not possible for us to receive Birthregistration without theese information

BR

@dirbSEGES dirbSEGES reopened this Jan 25, 2021
@cookeac
Copy link
Collaborator

cookeac commented Jan 25, 2021

The ReproParturition event is to capture information relating to the birth, while the MovementBirth event is to register the progeny (for systems that do this separately from providing progeny details as part of a parturition event).

The ReproStatusObserved event is to capture information relating to abortions.

It would appear there are two suggestions here:

  • Ability to capture additional (but ideally structured) information about the parturition - the first list above.
  • Ability to capture "size" as opposed to birth weight, for the progeny (or is this intended as an observation related to the dam, rather than the progeny - how is it used in animal evaluation?)

If these are international needs, and we can define the set of values, they could be added as enumerations. Otherwise my suggestion is for a localised use they can be added as an extension (the specification and JSON support this).

@dirbSEGES
Copy link
Author

Ok, i understand. We have the same system with separate registrations.

Yes - i have 2 suggestions. About the suggestions, we use the informations in the calculations of breedingvalues.

I have a 3. suggestions to describe the "calvingprocess". (Maybe it is what calvingEase in the ReproParturitionressource describes, but there are not any selections yet) Also used in the calculation of breedingvalues.

Easy without help
Easy with help
Difficult without veterinary care
Difficult with veterinary care
Cesarean section

I'm not sure if it's a international need, but it is a requirements in our system when a calving is registered.

Can there be a guidence how to make a local extension for the ReproParturition?

@ahokkonen
Copy link
Contributor

Personally I see that this should be defined as part of "calvingEase" codes.
Currently in icarReproParturitionEventResource this field is defined as "open" string type, but in my opinion it should be defined with own enum type including values proposed by @dirbSEGES

@erwinspeybroeck
Copy link
Collaborator

We are talking about the calvingEase field indeed. We discussed it in the past, but I think there was no consensus to make it an enum as such, since vaues can differ regarding country.

@dirbSEGES
Copy link
Author

We will make local additions for Birthsize and Stateofbirth. And use the enumeration for calvingEase that will be defined in the discussion in #185

I will close this discussion. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants