Repeatedly query all known sources for metadata during enrichment

Silvio Hermann mentioned this issue in a commit of ThULB / ansible / ubo on branch main:

Updated mycore commit to '4dd52fb8'

Given your configuration: When I start with a scopus ID, Scopus is queried once again with the DOI it returns itself? When that scopus data contains a pubmed ID, PubMed is queried twice with the DOI and that pmid? As a compromise, why not make it configurable at least per data source?
MCR.MODS.EnrichmentResolver.DataSource.Scopus.QueryAllIdentifiers=true|false

There also could be a global default
MCR.MODS.EnrichmentResolver.QueryAllIdentifiers.Default=true|false

You would set this to true and get the behavior you want.
MCR.MODS.EnrichmentResolver.QueryAllIdentifiers.Default=false
could be the default to be backwards compatible.
Others could do fine tuning by configuring it for each data source.

Of course the time for the enrichment is increasing, but I’ve been using this implementation for more than a year now, and haven’t had any complaints so far. My current configuration of datasources is as follows:

Since dois should be (and usually are) unique per publication, datasources like CrossRef, Unpaywall, DataCite, Scopus Pubmed and Pubmedcentral get queried only once anyway. Only GBV, ZDB, IEEE and ORCID are queried repeatedly if more than one issn, isbn, oclc, ppn, zdb are found.

Although I agree, that a configuration option like the one you’ve suggested would be the best solution, I still think that all ids found during enrichment deserve to be queried at least once. This, however, is not the case in the current implementation.

We should have this configurable per data source and per identifier, e.g. “enable querying ZDB with ISSN repeatedly”.

I fear the request time and the the number of calls massively increasing.

Application developer should have the choice for what data sources and which identifiers…

Well, in my opinion the current implementation of querying data sources only once is a limitation, since journals e.g. usually have more than one issn, a bunch load of oclc-ids, books often have more than one isbn, to name just a few. All of these ids often link to different records and should thus be queried during enrichment, and therefore data sources need to be queried more than once. Except for making redundant calls - which of course should be avoided for apis like scopus due to their rate limits - this is an improvement with no drawbacks since redundant information is merged anyway.