Please format your affiliation data as a comma-separated or tab-separated text file.
The first row of the file must contain only headers matching any of the following allowed field names:
- Required:
- Affiliation type: i.e., a value to indicate whether to write the affiliation to education or employment e.g., "staff" or "student"
- Email: the institutional email for the individual, and where the invitation will be sent if they're not known by the Hub
- First name: if the user does not have an ORCID iD, this field together with 'Last name' and email, will be used to pre-fill ORCID registration
- Last name
- Optional:
- Identifier: this can be any identifier used in your internal systems and is to allow you to match the resulting put-code from ORCID to simplify making future updates to the item
- ORCID iD: once it has been authenticated, an ORCID iD can be used instead of an email address; however, without an email address any invitation required cannot be sent
- Organisation: if different to your home campus. NB you may only write affiliations for organisations that are related to the member, e.g., historic names and subsidiaries
- Department
- City: if different to your home campus's city otherwise that will be used
- Region
- Course or Title: for an education item, the course of study or degree name; for an employment item, the role or job title
- Start date: Affiliation start date in ISO 8601 format, to the known/desired level of precision
- End date: Affiliation end date in ISO 8601 format, leave blank or omit field for ongoing affiliations
- Country: ISO 3166-1 alpha-2 and if different to your home campus's country code otherwise that will be used, i.e. NZ.
- Disambiguation ID: if different to your home campus's ID, the identifier for the Organisation that is given by the accompanying Disambiguation Source
- Disambiguation Source: typically RINGGOLD or Fundref, and required if a Disambiguation ID is provided
- To update existing ORCID items:
- Put-Code: this is a code ORCID uses to identify the item and is returned to you in the Hub's affiliation report.
With a put-code the Hub attempts to overwrite an item; while without one, a new item is created with a new put-code
Note: each record in the the affiliation file must contain either an email address or, if an individual has already gone through the Hub, an ORCID iD.
Dates are preferred in ISO 8601 format, i.e., YYYY-MM-DD with partial dates accepted, e.g, "2017", "2017-12", and "2017-12-15" are all valid; however,
the Hub will try to interpret any dates provided.
Where a field header or value is not provided, the value from your organisation will be used if it's available, e.g., Organisation, City, Country, Disambiguation ID,
and Disambiguation Source can be omitted where redundant.