-
Notifications
You must be signed in to change notification settings - Fork 31
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
feedIntake in milkVisitEvent #171
Comments
Our preference so far has been to keep the events separate - which would not stop in-parlour milking equipment sending both the milking visit and the feed intake event for an animal. This does raise a question whether there should be some way of linking simultaneous or related events by reference. |
This would mean that in the feed intake event we have to include a reference to a milking event, probably by the unique id of that event |
it is fair solution. Mayby include reference to Feedintake in MilkVisit? |
Would separate resources be a better solution for linking FeedIntake and MilkingVisit? |
I think having a sperate resource is a good idea. The main question for me is whether we need it in the upcoming release. Nevertheless, the linking resource is simple enough so we could just add it (with the overhead of creating the examples, collecitons, etc...). Background: Chicken and egg problem: does the milkvisit come first or the feedvisit. With a separate resource you don't have to decide, you just add it after both happened. And the place where the decision that these two events belong together is made is independent of the event creation. |
@cookeac to suggest semantics from another standards group that might be relevant. |
A generalised solution is described in #248 |
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. |
Hi,
Could feedIntake be added in milkVisitEvent. I´m thinking the feedconsumption related to a milkVisitEvent. (when concentrate is given in parlour or AMS)
I can see there is a discussion in issue #93 about the description.
The text was updated successfully, but these errors were encountered: