Visiting Scholar Organisation Relation
The view specifications for the visiting scholar organisation relations.
This page describes the view(s) needed to make the relation between a person and an organisation of the type visiting scholar.
- VISITING_SCHOLAR_ORG_RELATION: This view specifies the relations between persons(visiting_scholar) _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)
VISITING_SCHOLAR_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 VISITOR_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 | String | 1024 | Yes(**) | If defined lookup for organisation will be done by the non explicit id. Click here to expand…Synchronisation Non-explicit Id Matching
|
||
| 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. | |||
| PURPOSE_OF_STAY | String | 512 | No | |||
| VISITOR_FROM_ID | String | 1024 | No(**) | If defined lookup for external organisation will be done by the non explicit id. Click here to expand…Synchronisation Non-explicit Id Matching |
||
| VISITOR_FROM_PURE_ID | Long |
No(**) |
If defined lookup for external organisation will be done by the external organisation pure id. | |||
| VISITOR_FROM_SOURCE_ID | String | 1024 |
No(**) |
If defined lookup for external organisation will be done by the external organisation source id. | ||
| VISITOR_FROM_NAME | String | 1024 | No(**) | If defined lookup for external organisation will be done by the external organisation name. | ||
| VISITOR_FROM_TYPE | Classification |
No Is used when doing name matching. Otherwise not. |
Search by name is narrowed down by limiting to the type. If not defined "Unknown" type is used by default. The type of external organisation. Values from:
|
|||
| VISITOR_FROM_COUNTRY | Classification |
No Is used when doing name matching. Otherwise not. |
Search by name is narrowed down by limiting to the country. If not defined search ignores country. The ISO-3166-1 country code for the External Organisation country. See http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements |
|||
| JOB_TITLE | Classification |
|
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.
|
(**) 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.