How Can We Help?
Search for import candidates (Cron job)Search for import candidates (Cron job)
This cron job searches for import candidates from online import sources such as Scopus. Possible import candidates are identified based on the setup of Automated search by Persons or Organisations.
Recommended frequency
The schedule cannot be changed for this job type. The job reschedules itself after each run to ensure all organisations and persons are processed within 1 week.
How it works
When a Personal or organisation user sets up an Automated search this job will scan the selected source(s) for content that matches either the name variants or IDs. When hits are found they are presented to the user as import candidates:
If you have a name search configured under the Person/Organisation:
- The first time the job runs it will look back the amount of days you have added under Maximum days research outputs must be published within (See Job configuration below).
- The subsequent runs thereafter will look at the the current year. If the date is January 2025, then it will look at all of January 2025. If it is 31st of December 2025, then it will look at entire 2025.
- You can under an Organisation add a search string to use. If you add PUBYEAR 2018 (or any other year), then that will overwrite any year limit found in the job configurations.
- The date looked at can vary depending on what date the source allows us to look at. For Scopus it will look at the publication date.
If you have an ID search configured under the Person/Organisation:
- There is no date limit. It will look back through all years.
- You can under an Organisation add a search string to use. If you add PUBYEAR 2018 (or any other year), then what will overwrite any year limit found in the job configurations.
Job log
The job log will accumulate the number of import candidates found for each source, for each Person. In the screenshot below, no new candidates was found for PubMed, but 6 was found for Scopus, for the Person Bodil Steen Rasmussen:
In the Log entries search field above the job log, it is possible to search for an ID of a Person. This can be useful to inspect any lack of expected results, for example.
Job configuration
| Setting | Description | Notes |
|---|---|---|
| Maximum days publications must be published within | This configuration is only used when using name search; ID search always includes all research outputs. | Default is 720 days. |
| Limit automated search to current staff | When enabled, search for import candidates will only be performed for current staff | |
| Exclude future research outputs | When enabled, organization based searches will exclude research output with a publication date in the future | |
| Apply person match filtering to the found publications | When enabled, a publication will only be included in the final list if the person is matched to at least one of the publication authors | In the job log you will see the result, where all the non-relevant results have been filtered out already. It will only look at internal Persons. It will not look at Scopus ID - it will look at whether the author name in the source matches the one found in Pure. |
Published at July 11, 2025