How Can We Help?
QABO Publication Import Settings: How to Update Research OutputQABO Publication Import Settings: How to Update Research Output
What
Sometimes the data in Pure does not match what is in the QABO workspace. In these cases, we have a few settings in the QABO Publication Import that can be set to relook at publications and persons in Pure and update them to match what is in the QABO workspace.
As a note, the QABO Publication Import is a child job of the QABO Publication Import and Cleanup cron job. This is located under Administrator > Jobs > Cron Job scheduling the pressing edit under configuration. After doing this you will see a list of jobs, here you will want to focus on the QABO Publication Import.
How
There are a few different configurations within the QABO Publication Import job that can help relook at the QABO workspace so that both Pure and the QABO workspace match.
| Setting | Summary |
|---|---|
| QABO experts filtering date | This is used to limit the experts being updated to only those that have been changed since the date noted in the configuration. If the job runs for the first time (or has never run successfully) then all experts are updated. After a successful run, the job will only update experts that have been changed since last run. Therefore, the date will be changed if the job runs successfully (with no errors) AND has no limits set (i.e. run without limited to specific expert Ids/scopus Publication Ids). |
| Force Run on All Experts (en_US version)/ Ignore QABO filtering date (en_GB version) | This setting ensures all publications are looked at again within the QABO workspace (e.g. bypassing the QABO experts filtering date); without force only publications that have been updated in QABO will be looked at. As a note, enabling this setting will not override manually edited content. (see KB-297 for more information). |
| Limit to expert IDs | This setting is used to update one or a select group of persons against the QABO workspace. This field is based on SciVal IDs (please see KB-53 for more details). |
| Limit to the following publication IDs | Use this setting to update one or a select group of publications against the QABO workspace, field is based on Scopus IDs. |
| Update persons and organisations on existing research outputs according to Scopus data | This setting looks at all existing research outputs and updates persons and organisations (both internal and external) to reflect how they would look like if they where imported from Scopus, Note: is should only be used to correct invalid data and will automatically be switched OFF after the job has been executed. This will delete manually entered data on the research output for the fields. |
However, even though you have run the QABO Publication Import with one or more of the above noted settings, you still might not get the desired results.
-
Manual Edits to QABO data: If the job detects that there has been manual changes on content, it will skip that field and assume the field will be manually updated moving forward. This will be seen as a warning in the job log, i.e.: publication id:123 contains user modifications to authors/organisations and need to be cleaned up manually. It can't be determined if the Scopus data or data in Pure is the correct version (see KB-14 for more details).
Note: If you run the QABO Publication Import with the Update persons and organisations on existing research outputs according to Scopus data ON this configuration disables this (will override manual edits) so you need to make sure this is not turned on. Default setting is OFF. - No changes sensed between runs; If the job does not find any new updates based on what is in the QABO workspace it'll skip that content. This can be an issue when using the internal/ external toggle. For example, if you had this toggled OFF when content was added to Pure (which then would add an internal affiliation where maybe it should be external) then later toggle it ON, the QABO Publication Import will not update the affiliations because it does not detect an update (based on what was in the QABO workspace at the time it was imported- the affiliation never actually changed). In this case running the Force Run on All Experts (en_US version)/ Ignore QABO filtering date (en_GB version) would be a possible solution to help make Pure and the QABO workspace match.
- Depublication process in Pure; You cannot make a direct correlation between publications in QABO and publications in Pure. Pure de-duplicates publications based on DOI and PubMed id.
Other issues might require a data dump and/or log. If this is the case, please refer to KB-117 for more specific details on how to do this.
More information
KB-14: PRS customers manually changing Research Output
KB-42: How QABO matches authors
KB-53: Running QABO Publication Job for only one person (IDs)
KB-105: QABO Publication Import job - to update publication with newly created affiliation
KB-117: When to use dump and log and how to get them
KB-409: QABO Publication author correction job
Note: Some of this information is for internal use only and might not be accessible.
Updated at July 27, 2024