How Can We Help?
Student Organisation RelationStudent Organisation Relation
The view specifications for the student organisation relations.
This page describes the view(s) needed to make the relation between a person and an organisation of the type student.
- STUDENT_ORG_RELATION: This view specifies the relations between persons(student) _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)
STUDENT_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 STUDENT_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_StudentType_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 Synchronisation - Views | ||
| ORG_ID | Yes(**) | If defined lookup for organisation will be done by the non explicit id. Click here to expand…Synchronisation Non-explicit Id MatchingWhen 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 student. Values from: /dk/atira/pure/person/studenttype
|
|||
| AFFILIATION_ID | String | 30 | No | Id related to this affiliation: Student ID | ||
| 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. | |||
| START_YEAR | String | 30 | No | |||
| STATUS | Classification | Yes |
The type of attendance status. Values from: /dk/atira/pure/person/studentstatus
|
|||
| PROGRAMME | String | 512 | No | |||
| STUDENT_TYPE_DESCRIPTION | Classification | No |
The type of student description Values from: /dk/atira/pure/person/studenttypedescription
|
|||
| EXPECTED_STUDY_DURATION | Integer | No | ||||
| MIN_STUDY_DURATION | Integer | No | ||||
| MAX_STUDY_DURATION | Integer | No | ||||
| PROGRAMME_YEAR | String | 65 | No | |||
| STUDENT_NATIONALITY | Classification | No | The ISO-3166-1 country code. See http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements | |||
| STUDENT_RESIDENCY_FLAG | String | 1024 | No | Values must be provided as either: unknown, home or overseas. | ||
| STUDENT_COUNTRY_OF_DOMICILE | Classification | No | The ISO-3166-1 country code. See http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements | |||
| AWARD_GAINED | String | 256 | No | |||
| PROJECT_TITLE | String(*) | 1024 | No |
The PROJECT_TITLE to add. If no locale is specified in the column name, the PROJECT_TITLE 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:
If locales are specified PROJECT_TITLE must not be present in your view without a locale suffix. The language should be appended in ISO 639-1 (two-letter codes) |
||
| AWARD_DATE | Date | No | ||||
| INITIAL_SUBMISSION_DATE | Date | No | ||||
| EXPECTED_END_DATE | Date | No | ||||
| FTE | Double | No | ||||
| 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.
|
(*) To handle multiple languages _EN or _ must be added to the column name.
(**) 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.
SQL for validating STUDENT_ORG_RELATION
ORG_RELATION_FUNDING_ORGS
ONLY AVAILABLE FOR CUSTOMER ON THE UK BASE AND ON 5.12.1 OR ABOVE
| Column name | Data type | Size | Mandatory | Note | Sync? Customer chooses between: 'Yes', 'No' or 'Once' |
|---|---|---|---|---|---|
| ID | String | 1024 | Yes | The ID for this specific relation. This ID must be unique (can be thought of as a primary key). If your backend system is not capable of providing ID's for relations please talk to Elsevier. We will then use another strategy described here. | |
| STUDENT_RELATION_ID | String | 1024 | Yes | The ID of the student organisation relation for this funding to be associated with. This ID must match one of the ID's from the STUDENT_ORG_RELATION view specified above this table | |
| ORG_ID | String | 1024 | No | Id to match for the organisation associated with the funding. Click here to expand…Synchronisation Non-explicit Id MatchingWhen using non explicit id matching, the lookup for the content is handled in the following way and order:
|
|
| ORG_ID_HINT | String | 1024 | No | Click here to expand…Synchronisation Non-explicit Id HintsWhen using non explicit id matching, the lookup can be configured to prefer a specific set of ids through a hint. This means that if multiple content are found with the same id the one with the id in the specific area of the hint is returned. The following hints are supported:
|
|
| EXT_ORG_ID | String | 1024 |
No |
Id to match for the external organisation associated with the funding. Click here to expand…Synchronisation Non-explicit Id MatchingWhen using non explicit id matching, the lookup for the content is handled in the following way and order:
|
|
| EXT_ORG_ID_HINT | String | 1024 | No | Click here to expand…Synchronisation Non-explicit Id HintsWhen using non explicit id matching, the lookup can be configured to prefer a specific set of ids through a hint. This means that if multiple content are found with the same id the one with the id in the specific area of the hint is returned. The following hints are supported:
|
|
| EXT_ORG_NAME | String | 1024 | No | ||
| EXT_ORG_TYPE | Classification | No | |||
| EXT_ORG_COUNTRY | Classification | No | |||
| ACADEMIC_YEAR | String | 20 | No | ||
| AMOUNT | Double | No | |||
| AMOUNT_CURRENCY | Classification | No | |||
| COST_CENTRE_CODE | String | 40 | No | ||
| ANALYSIS_CODE | String | 40 | No | ||
| PERCENT | Double | Number between 0 and 1. | |||
| FUNDER_TYPE | String |
Supports the following fields:
|
|||
| PROJECT_ID | String | 1024 | No | Id to match for the project associated with the funding. Click here to expand…Synchronisation Non-explicit Id MatchingWhen using non explicit id matching, the lookup for the content is handled in the following way and order:
|
|
| PROJECT_ID_HINT | String | 1024 | No | Click here to expand…Synchronisation Non-explicit Id HintsWhen using non explicit id matching, the lookup can be configured to prefer a specific set of ids through a hint. This means that if multiple content are found with the same id the one with the id in the specific area of the hint is returned. The following hints are supported:
|
Published at March 18, 2024