...
| Field | Type | Constraints | Description |
|---|---|---|---|
subject_id | varchar(503) | NOT NULL | The internal ID of the resource initiating the relationship (ie. the subject) |
| property | varchar(503) | NOT NULL | The predicate of the relationship |
| object_id | varchar(503) | NOT NULL | The internal ID of the resource which is the target of the relationship (ie. the object) |
| source_id | varchar(503) | NOT NULL | The internal ID of the direct or indirect container containing the resource that created the relationship. |
| proxy_id | varchar(503) | NOT NULL | The internal ID of the resource that created the relationship. This is contained within the source_id |
| start_time | datetime | The datetime the relationship started. | |
| end_time | datetime | The datetime the relationship ended. | |
| last_updated | datetime | The datetime the relationship was last updated. (used for eTags) | |
| tx_id | varchar(36) | NOT NULL | The transaction id this record belongs to |
| operation | varchar(10) | NOT NULL | The type of operation this is, one of 'add' or 'delete' |
| force_flag | varchar(10) | ??? (seems to always be NULL) |
...
Inbound Reference Index
The inbound reference tables hold relationships between two resources in the repository, due to there being no single subject restriction it is possible for a 3rd resource to generate an inbound reference from a 1st resource to a 2nd resource. This relationship will persist even if the 2nd resource was deleted.
...