When exporting ORCID users for use in research intelligence reporting, we may want to just get the list of users known to sul-pub who have been through the Stanford integration, without also querying for read/wrote scope or querying the ORCID API for other potential Stanford researchers who have not been through the Stanford integration. Both of these other queries require iterating over many results and issuing lots of API calls, and they are time consuming, while just getting a list of users with known ORCIDs is fast.
This changes the rake task to that you can specify if you want the time consuming parts to really run (the both default to false here and will be skipped).
Why was this change made?
When exporting ORCID users for use in research intelligence reporting, we may want to just get the list of users known to sul-pub who have been through the Stanford integration, without also querying for read/wrote scope or querying the ORCID API for other potential Stanford researchers who have not been through the Stanford integration. Both of these other queries require iterating over many results and issuing lots of API calls, and they are time consuming, while just getting a list of users with known ORCIDs is fast.
This changes the rake task to that you can specify if you want the time consuming parts to really run (the both default to false here and will be skipped).
How was this change tested?
On UAT.