ICAR Animal Data Exchange Working Group – Technical meeting 28 August 2020

• In attendance: Andrew C, Anton H, Beate M-F, Conny G, Craig V, Erwin S, John M, Kor O, Thomas D, Thomas P.

Agenda:

1. "Do not breed" instruction
2. Reproductive and Lactation Status Change (and PUT/PATCH)
3. Other topics

1. "Do not breed" instruction (#138)

A Do Not Breed event and collection has been added in the last two weeks. At the last meeting we had left open the question of how to represent "Do not breed" for an animal.

• doNotBreed could be a separate boolean field, because as an instruction from the farmer it is separate from (and in parallel to) the animal's current reproductive status.
• We also discussed whether this could be achieved by generic flags, or by maintaining membership of a group (Animal Set). Outcome: The group had reviewed this and recommended the we should add "DoNotBreed" as a value in the reproductionStatus enumeration.

2. Should we have an event when you observe a reproductive status change, or just PUT/PATCH (#140)

At the last meeting, we discussed whether:

• There should be a generic "status change" event to change the reproductive status. OR
• One could use PUT to an Animal resource to try and update animal properties (and it would be up to the system receiving the PUT to interpret).

Some of the attendees' systems could just change the animal with a PUT, while other systems always required an event to change a status. Some recording systems do not allow a PUT to animal record, but instead ingest animal events and use these to change the animal record. We discussed scenarios such as:

• Receiving data from a system (or a mobile app) that generates the data OR
• Synchronising data between peer systems We noted that it is possible that some systems will PUT/PATCH and some systems will not support this. Outcome: We agreed that we do want to have events for an observed change to Reproduction and Lactation. We noted that we do want to provide a URL scheme for POST/PUT/PATCH but this would be done in ADE 1.2, not ADE 1.1

3. Reproductive and lactation status (#111)

This has been implemented with a Pull Request. An outstanding task was to consult with experts in our organisations to see if there are examples of invalid combinations that we should worry about. Thomas and Beate confirmed they did not know of any invalid Reproduction/Lactation combinations, so we will close this issue now.

4. Categorising the new APIs in the Example URL Scheme

We need to properly categorise the new collections/API end points in the Example URL Scheme for the ADE 1.1 release.

• Management - put animal sets in here
• Health - put animal health treatments and diagnosis here
• Reproduction - add gestations here
• Milk - add test days here
• Performance - confirmation scores, weight, breeding values here Outcome Erwin will update the OpenAPI file.

5. Other items for ADE 1.1

• List of filters - this is being developed in the Wiki and does not need to be part of the release

6. Roadmap for ADE 1.2

• We would like to cover feeding, but might need more expert input, and consideration for units and other parameters.
• GEA has some other suggestions they will prepare.
• We asked if there are any areas of collaboration with AgGateway or other initiatives.
• We would like to address URL schemes for PUT/POST

Next meeting scheduled for 11 September 2020 at 9am CET