Papers › LEI: Livestock Event Information Schema for Enabling Data Sharing

LEI: Livestock Event Information Schema for Enabling Data Sharing

26 Oct 2023arXiv:2310.17684links table onlyarchive 2025-07-28

Mahir Habib, Muhammad Ashad Kabir, Lihong Zheng, Shawn McGrath

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Data-driven advances have resulted in significant improvements in dairy production. However, the meat industry has lagged behind in adopting data-driven approaches, underscoring the crucial need for data standardisation to facilitate seamless data transmission to maximise productivity, save costs, and increase market access. To address this gap, we propose a novel data schema, Livestock Event Information (LEI) schema, designed to accurately and uniformly record livestock events. LEI complies with the International Committee for Animal Recording (ICAR) and Integrity System Company (ISC) schemas to deliver this data standardisation and enable data sharing between producers and consumers. To validate the superiority of LEI, we conducted a structural metrics analysis and a comprehensive case study. The analysis demonstrated that LEI outperforms the ICAR and ISC schemas in terms of design, while the case study confirmed its superior ability to capture livestock event information. Our findings lay the foundation for the implementation of the LEI schema, unlocking the potential for data-driven advances in livestock management. Moreover, LEI's versatility opens avenues for future expansion into other agricultural domains, encompassing poultry, fisheries, and crops. The adoption of LEI promises substantial benefits, including improved data accuracy, reduced costs, and increased productivity, heralding a new era of sustainability in the meat industry.

PaperPDFCode

Code

mahirgamal/lei-schema officialmentioned in paper report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections