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

feedIntake in milkVisitEvent #171

Closed
dirbSEGES opened this issue Oct 21, 2020 · 8 comments
Closed

feedIntake in milkVisitEvent #171

dirbSEGES opened this issue Oct 21, 2020 · 8 comments
Assignees
Labels
stale-issue Identifies that an issue is stale and will be closed unless reactivated.

Comments

@dirbSEGES
Copy link

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.

@cookeac
Copy link
Collaborator

cookeac commented Oct 22, 2020

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.

@erwinspeybroeck
Copy link
Collaborator

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

@dirbSEGES
Copy link
Author

it is fair solution. Mayby include reference to Feedintake in MilkVisit?

@cookeac cookeac added the this-release Scheduled to be implemented for this release in development label Nov 5, 2020
@ahokkonen
Copy link
Contributor

Would separate resources be a better solution for linking FeedIntake and MilkingVisit?
Some sort of FeedIntakeAndMilkingVisitLinkResource where you can set explicitly link between feed intake and milking visit? Is many-to-many connection needed?

@ghost
Copy link

ghost commented Mar 24, 2021

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 cookeac removed the this-release Scheduled to be implemented for this release in development label Apr 22, 2021
@cookeac
Copy link
Collaborator

cookeac commented Jul 15, 2021

@cookeac to suggest semantics from another standards group that might be relevant.

@cookeac
Copy link
Collaborator

cookeac commented Sep 23, 2021

A generalised solution is described in #248

@stale
Copy link

stale bot commented Dec 22, 2021

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 Dec 22, 2021
@stale stale bot closed this as completed Jan 21, 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.
Projects
None yet
Development

No branches or pull requests

4 participants