Data schemas in this context are simply a structured representation of data, formats and query parameters describing how data will be interchanged.
Standard data schemas are at the heart of DataLinker’s streamlined approach. We organise and group farm data into useful datasets, and define the type, format and means of requesting and delivering data so that you code once and can re-use with multiple parties.
Take Killsheet data for example:
All processors return carcass data to their farmers, and while there’s some variation in the information provided, much of it is common across all processors.
For a farm budgeting tool to retrieve that data direct from a processor, it has to code and map that processor’s data to receive it into their system. For another farmer using the same budgeting tool but a different processor, it has another coding and mapping task . And so on, across the sector.
Faster, Cheaper, Easier
With a standard DataLinker schema, processors agree to send their killsheet data in a standard format. The schema defines some fields as required and others as optional, so if there’s a unique data field provided by one processor but not others that can still be included. Your farm budget tool codes once to receive data in this format, and it doesn’t matter which processor provides the data.
And DataLinker extends this approach to all types of farm data – production, animal, land, feed, and financial.
Work with us and with your own partners to construct schemas for your business needs. We’ll help you to define the data sets and we align these with the Farm Data Standards. Once agreed, DataLinker publishes the schema and it’s ready to use.
Have a look at the schemas published till now -- https://www.datalinker.org/context/entrypoints
There’s no limit to the number of schema – the key is in making each schema broad enough for multiple party use, and tight enough to allow organisations to manage their licence terms effectively.
GET and Update
Some DataLinker schema will allow for Update functions like PUT or POST. This means that a farmer can authorise the Consumer to send updates back to the Provider if their data changes. These schema effectively enable a two way exchange of data between systems, with both systems synching to the most current data.