How Can We Help?
Honorary Staff Organisation RelationHonorary Staff Organisation Relation
The view specifications for the honarary staff organisation relations.
This page describes the view(s) needed to make the relation between a person and an organisation of the type honarary staff.
- HONORARY_STAFF_ORG_RELATION: This view specifies the relations between persons(honarary staff) _and _organisations. There can be multiple entries pr person in this, i.e. a person can be related to multiple organisations (both active and historical)
HONORARY_STAFF_ORG_RELATION
| Column name | Data Type | Size | Mandatory | Note | Sync? Customer chooses between: 'Yes', 'No' or 'Once' |
|---|---|---|---|---|---|
| ID | String | 1024 | Yes | The ID for the HONORARY_ORG_RELATION. This ID must be unique for this specific relation (can be thought of as a primary key). One way to generate an ID in your backend system is to combine multiple values such as: PersonID_OrganisationID_EmploymentType_Start date | |
| PERSON_ID | String | 1024 | Yes | The ID of the person for this relation. This ID must match one of the PERSON_ID's from the PERSON_DATA view specified in Unified Person Synchronization - Views | |
| ORG_ID | Yes(**) | If defined lookup for organisation will be done by the non explicit id. When using non explicit id matching, the lookup for the content is handled in the following way and order:
|
|||
| ORG_PURE_ID | Long |
Yes(**) |
If defined lookup for organisation will be done by the organisation pure id. | ||
| ORG_SOURCE_ID | String | 1024 |
Yes(**) |
If defined lookup for organisation will be done by the organisation source id. | |
| ORG_CLASSIFIED_IDS_ID | String | 1024 |
Yes(**) If used, must be supplied together with a valid id source ORG_CLASSIFIED_IDS_TYPE |
If defined lookup for organisation will be done by a classification defined id. | |
| ORG_CLASSIFIED_IDS_TYPE | Classification |
Yes Is used when matching on ORG_CLASSIFIED_IDS_ID, otherwise not. |
The source where the ORG_IDS_ID is related to. Provide the last part of the uri (key) of the classification | ||
| EMPLOYMENT_TYPE | Classification | No |
The type of employment. Values from: /dk/atira/pure/person/employmenttypes
|
||
| AFFILIATION_ID | String | 30 | No | ||
| PERIOD_START_DATE | Date | Yes | |||
| PERIOD_END_DATE | Date | No | |||
| PRIMARY_ASSOCIATION | Boolean | No | Please be aware that only one association in total (staff, student, visiting and honorary) can be the primary association. Whenever one is set as primary, other primary markers are removed. | ||
| JOB_TITLE |
|
No |
The type of job title. Values from: /dk/atira/pure/person/jobtitles
|
||
| JOB_DESCRIPTION | String(*) | 1024 | No |
The JOB_DESCRIPTION to add. If no locale is specified in the column name, the JOB_DESCRIPTION is added to all supported locales. If locales are provided, all supported locales must be specified To provide a locale you need to suffix the language to the column name and create a column for each supported locale. In the case of French and English this would result in the following columns: JOB_DESCRIPTION_EN JOB_DESCRIPTION_FR If locales are specified JOB_DESCRIPTION must not be present in your view without a locale suffix. The language should be appended in ISO 639-1 (two-letter codes) |
|
| MANAGED_IN_PURE | Boolean | No | Indicates whether or not an organisation association should be managed inside Pure. If set to TRUE the synchronisation will only import the organisation association and not lock any fields/relations. In subsequent synchronisation runs, the synchronisation will not update the organisation association, unless the MANAGED_IN_PURE state is changed to FALSE. If changed the organisation association will be picked up by the synchronisation and handled as a synchronised content and fields and relations will be locked based on the configuration. The default behaviour for the synchronisation is to consider MANAGED_IN_PURE as FALSE if data us not supplied for it. If the person that holds the organisation association is set to MANAGED_IN_PURE TRUE, the organisation association will inherit this value and only be imported. This feature is available in the 5.3.0 / 4.22.0 release of Pure |
(**) Only one means of identification of other content must be used. Do not fill in data into more than one column per relation, unless otherwise noted.
Updated at July 27, 2024