Table of Contents

icarCarcassResource

Description

A carcass (also called carcase) identifies a single animal which is processed at a plant. A carcass has identifying information and attributes describing the animal from the processor perspective.

The icarCarcassResource schema inherits from icarResource.

Properties

Name Description Required Type
ProcessingLot The lot in which the carcass was processed. Yes icarProcessingLotType
KillDateTime Date/time the animal was killed. Ideally this should be a precise date and time. However, older systems may only be able to supply the date. No date-time
BodyNo A unique identifier on the chain and kill date assigned to the carcass by the processor. Yes Integer
Identifiers Identifiers for the carcass including the animal's id Yes Array of  icarIdentifierType
Sex The sex of the animal as assessed at the processing plant. No icarAnimalGenderType
BirthDate Assessed date of birth of the animal represented using RFC3339 (UTC). No date-time
BirthDateConfidence A 3-character string representing Year, Month, and Day (YMD). Each character can have the value A (actual), E (estimate), U (unknown). e.g. AEU. No string
PrimaryBreed Primary breed of the animal as visually categorised by the plant, represented using ICAR breed codes. No icarIdentifierType
PlantBoningRun Allocation of the carcass to a plant boning run (if any). No Integer
PlantBoningRunTemplate Where a Boning Run Template is allocated by the plant, the name or ID of the template. No string
DestinationCode Plant-specific destination codes that are used for company requirements and to link to boning run processing. No string
ProcessorGrid Reference to a processor-specific grid used to calculate the price paid to the producer No string
Self Uniform resource identifier (URI) of the resource (rel=self). No string
Meta Meta-data for the resource. Mandatory if you wish to support synchronisation. No icarMetaDataType
Location Unique location scheme and identifier combination. No icarIdentifierType

Examples

Example 1