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

Resource for ReproPreExamintion? #233

Closed
dirbSEGES opened this issue Aug 5, 2021 · 4 comments · Fixed by #256
Closed

Resource for ReproPreExamintion? #233

dirbSEGES opened this issue Aug 5, 2021 · 4 comments · Fixed by #256
Labels
stale-issue Identifies that an issue is stale and will be closed unless reactivated. this-release Scheduled to be implemented for this release in development

Comments

@dirbSEGES
Copy link

Hi,

When an animal haven´t startet the reproductive cycle. The AI technician can examinate the animal and conclude a status like, the animal is cystic or another remark. The remarks are also sometime registered related to a unsuccesful insemination, ex. in case the animal was post heat and have bleed.
These remarks would be good have in a ressource, the remarks are valuable information for the management of the reproduction in the herd.

The resource could be like this:

"allOf": [{
"$ref": "../resources/icarEventCoreResource.json"
},
{
"type": "object",
"properties": {
"remark": {
"type": "array",
items": {
"type": "string" (or maybe a ID and Sheme or an enum?)
}
}
}

I can see that ReproStatusObservedEventResource maybe could be used with the same purpose, but I miss the possibility to add remarks also.

Or how do you suggest us to display this kind of info?

@cookeac
Copy link
Collaborator

cookeac commented Aug 9, 2021

I agree that icarReproStatusObservedEventResource would be ideal, but in the context of this and other requests, I think there would be value in adding a remark : string field to icarEventCoreResource so that it is available for all resources.

@dirbSEGES
Copy link
Author

Yes, that will be valuable. I like this solution.

@erwinspeybroeck
Copy link
Collaborator

We started collecting remarks in one of our apps since a year now. The remarks are not stored in our backend. We wanted first to get some insight in how the customer would use this remark. We are planning an analysis of what has been entered until now. We want to see if we can standardize remarks instead of black box strings. The advantage of standized remarks would be that you can also do something with this remark for managment information purpose.
We implemented remarks there for most of the events (in the app, not yet in the API), so indeed a remark in the core resource ould suite best.

@cookeac cookeac added the this-release Scheduled to be implemented for this release in development label Oct 7, 2021
@cookeac cookeac linked a pull request Oct 21, 2021 that will close this issue
@stale
Copy link

stale bot commented Jan 5, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Jan 5, 2022
@stale stale bot closed this as completed Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale-issue Identifies that an issue is stale and will be closed unless reactivated. this-release Scheduled to be implemented for this release in development
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants