ORCID Support

Using ORCIDs for institutional Parties in Mint

If you have ORCIDs associated with your parties in your source of truth (e.g. University Office or Research Master), you can harvest them into Mint and use it as the record's identifier. To set it up:

    1. Add a column for the ORCID to the Party csv file used in the harvest.

      1. ID,Given_Name,Other_Names,Family_Name,Pref_Name,Honorific,Email,Job_Title,GroupID_1,GroupID_2,GroupID_3,ANZSRC_FOR_1,ANZSRC_FOR_2,ANZSRC_FOR_3,URI,NLA_Party_Identifier,ResearcherID,openID,Personal_URI,Personal_Homepage,Staff_Profile_Homepage,Description

      2. ,ORCID

    2. Edit your Party people harvest configuration to include the new ORCID column in the includedFields

                  1. {

                  2. "harvester": {

                  3. "type": "csv",

                  4. "csv": {

                  5. ...

                  6. "includedFields" : ["ID", "Given_Name", "Other_Names", "Family_Name", "Pref_Name", "Honorific", "Email", "Job_Title", "GroupID_1", "GroupID_2", "GroupID_3", "ANZSRC_FOR_1", "ANZSRC_FOR_2", "ANZSRC_FOR_3", "URI", "NLA_Party_Identifier", "ResearcherID", "openID", "Personal_URI", "Personal_Homepage", "Staff_Profile_Homepage", "Description","ORCID"]

                  7. }

                  8. },

                  9. ...

                  10. }

      1. This will ensure the ORCIDs are recognised and stored against the party record.

    1. Now that records are being stored, curation of parties by Mint is no longer needed and the ORCID should be provided for references. In the harvest configuration file set the alreadyCurated flag to true

                  1. {

                  2. ...

                  3. "curation": {

                  4. "neverPublish": false,

                  5. "alreadyCurated": true

                  6. },

                  7. ...

                  8. }

      1. and change the idColumn value to the name of the new ORCID column. If the ORCID column contains the complete ORCID string (e.g. orcid.org/0000-0000-0000-0001), empty the recordIdPrefix value.

                  1. {

                  2. "harvester": {

                  3. "type": "csv",

                  4. "csv": {

                  5. "fileLocation": "${fascinator.home}/data/People_Sample.csv",

                  6. "idColumn": "ORCID",

                  7. "recordIDPrefix": "",

                  8. "headerRow": true,

                  9. "delimiter": ",",

                  10. "ignoredFields": [],

                  11. "includedFields" : ["ID", "Given_Name", "Other_Names", "Family_Name", "Pref_Name", "Honorific", "Email", "Job_Title", "GroupID_1", "GroupID_2", "GroupID_3", "ANZSRC_FOR_1", "ANZSRC_FOR_2", "ANZSRC_FOR_3", "URI", "NLA_Party_Identifier", "ResearcherID", "openID", "Personal_URI", "Personal_Homepage", "Staff_Profile_Homepage", "Description","ORCID"]

                  12. }

                  13. },

                  14. ...

                  15. }

      1. Referencing external researchers

      2. From ReDBox 1.9, a search interface has been added to the existing Name lookup widget so that ORCIDs for external parties can be discovered and referenced in data collection records.