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

Referencing other resources (especially possibly deleted ones or ones in other locations) #178

Closed
thomasd-gea opened this issue Dec 11, 2020 · 0 comments
Labels
this-release Scheduled to be implemented for this release in development

Comments

@thomasd-gea
Copy link
Contributor

thomasd-gea commented Dec 11, 2020

While talking about the feeding, I came across the point that you could reference a feed that is on location A in a ration that is on location B. I think it will be hard to avoid that by a specification in the schema, but maybe we should give a strict advice to users of the standard? This can of course also happen with an animal event that references an animal on another location (e.g. because it was moved).

A similar thing are references to possibly deleted entities. If you have a ration that references a feed which you don't want to have in your resource list anymore (because you have sooooo many feeds already in there and you don't want to buy this specific feed anytime in the future anymore), then you can not delete the feed as the ration would then become invalid. If the ration becomes invalid, all resources/events that reference it will also become invalid, and the same happens if you just delete the ration as well. On the other hand, if you don't delete things, you will end up with a system containing (possibly) more outdated and unused data than used data. I think we should also think about guidance in this part and (although I know it will get tricky with that) thinking about the deletion of referenced resources in general. Including moved animals.

cookeac added a commit that referenced this issue Jan 28, 2021
Active field in feed resources - closes #178
@cookeac cookeac added the this-release Scheduled to be implemented for this release in development label Jan 28, 2021
@cookeac cookeac closed this as completed Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
this-release Scheduled to be implemented for this release in development
Projects
None yet
Development

No branches or pull requests

2 participants