How to Use the Person ID Import JobHow to Use the Person ID Import Job

What

A Person has a number of IDs associated. To populate any of IDs the "Person ID Import" job is used to import IDs to a source defined in the CSV file.

How

You’ll have to create a CSV file to use for this job. It needs these headers:

• PureID,ExternalID,Type

Please note that this is case sensitive.

• The PureID is the ID on the person:
  
• The ExternalID is the value you want to add (Eg. Scopus ID)
• The Type is where you want the value added. The default value is Scopus ID, so if you have a spelling error, case sensitive error or no definition, then the value from ExternalID will be added as a Scopus ID.
• You need to verify that the classification used in Type is under the “personsources” classification schema /dk/atira/pure/person/personsources
  If the expected classification does not exist, then it will default to Scopus ID.
• The Type value is also case sensitive and it must match the URI (not the term). Either the full URI or the last part of the URI
  
• This could be an example:
  
  Note that the values should be separated by a colon (semi colon would not work).
• Once the CSV file is created you’ll have to upload it in the job. Here there are two configuration settings that you must take note of:
  • “Select whether existing values should be overwritten” when toggled on, the job will overwrite existing data in the Type value in your CSV file.
  • “Allow multiple IDs from the same source” when toggled on, the job allows you to have several IDs of the same Type in the CSV file. This will then add several IDs of the same type on the person. Be aware that if the person already has several ID’s of the same Type and you only have one in the CSV file, then all the others will be removed and only the new one will be added.
    

If the persons you want to update does not have any Scopus ID or Employee ID, it is suggested that you leave the configuration as default.
You can choose to put both Employee ID and Scopus ID for the same person in the same file and run the job once or you can run twice once with the Employee ID and once with the Scopus ID.

You cannot use Person ID Import job to bulk import ORCID IDs. Please use Bulk Change IDs on Content Job 

More information

Bulk change Source IDs on content
Setting up the ORCID ID on a Person
How to get Multiple Scopus Author IDs in Pure 
Adding Person Source Ids in Pure (Master list vs. Sync) 
Bulk upload ORCID IDs  
Bulk change IDs on content 
Note: Some of this information is for internal use only and might not be accessible.