6.4.2.4 SourceChannel
6.4.2.4.1 Purpose¶
How values reach us: read directly from a device, through management software, through a third-party platform, typed in our app or uploaded as a file. The channel is independent of the origin, so the same robot reading can arrive through two channels.
6.4.2.4.2 Questions it answers¶
- Through which route did this data arrive?
- Which channels does an Organization use?
6.4.2.4.3 Fields¶
| Field | Type | Cardinality | Description |
|---|---|---|---|
id |
string (uuid) |
1..1 |
Key. |
name |
string |
1..1 |
Unique. |
organization |
Organization | 0..1 |
|
created_at |
datetime |
1..1 |
|
updated_at |
datetime |
1..1 |
6.4.2.4.4 Subtypes¶
Discriminator type: every SourceChannel is exactly one of the subtypes below (disjoint and complete).
DirectDeviceChannel¶
Our software reads the device itself (e.g. on the farm server).
No fields beyond those of the parent.
ManagementSoftwareChannel¶
Through the farm management software, e.g. Lely Horizon, AfiFarm, DelPro, DairyComp.
No fields beyond those of the parent.
ThirdPartyPlatformChannel¶
Through a vendor cloud, a breed association or another platform (e.g. SiAlleva).
No fields beyond those of the parent.
MoonitoringAppChannel¶
Entered by a user in our application.
No fields beyond those of the parent.
FileChannel¶
Through a file uploaded or exchanged (CSV, PDF, spreadsheet).
No fields beyond those of the parent.
6.4.2.4.5 Relationships¶
References
SourceChannel.organization→ Organization (0..1)
Referenced by
IntegrationIdentifier.source_channel(1..1)ChannelVersion.source_channel(1..1)SourceFeed.source_channel(1..1)SourceAdapter.source_channel(1..1)FeedDetection.source_channel(1..1)AdapterMapping.source_channel(1..1)IntegrationGap.source_channel(0..1)
Subtypes
- by
type: DirectDeviceChannel, ManagementSoftwareChannel, ThirdPartyPlatformChannel, MoonitoringAppChannel, FileChannel
6.4.2.4.6 Rules & constraints¶
- How the value reached us. Independent from the origin.