Skip to content

How can we improve Content?

← Content

Make Article-level Linking Immune to Provider Changes in Consortia Collections

At least in the German-speaking market (feel free to comment below if this is true for your country as well!) it is very common for consortia contracts on e-resource collections that the subscription for any title contained in the collection persists even if that title is subject to a provider change. So, typically, at the very beginning of the contract all titles of the particular collection are hosted by one and the same provider and over the time several titles get acquired by other providers without causing them to drop out of the collection - at least in terms of the subscription.
However, we currently see Ex Libris Content Operations drop such titles out of the corresponding consortia collections in the Community Zone because their quality assurance rules during the ingest of updated title lists follow a logic that is valid only for vendor collections: If a title's base-URL does not match the base-URL of the collection the title does no longer belong to the collection.

Proposal: Ex Libris, please, use your huge amount of knowledge in your Central Knowledge Base / Community Zone and try to determine automatically which vendor-specific target parser can still provide article-level linking for the title with a base-URL no longer matching the base-URL of a consortia collection!

Example: Let's assume we have a consortia collection of e-journals originally purchased from Wiley and hosted on wiley.com (= domain in the base-URL of each title). Of course, target parser Wiley::WILEY provides perfect article-level linking for all these titles. Now let's assume a title T contained in this collection is acquired by Sage. Hence, the consortium provides Ex Libris with an updated title list. For title T this list contains a new base-URL with domain sage.com. Instead of just dropping title T we would like you to match the new domain against the Central Knowledge Base / Community Zone. You'll find at least one collection hosted in that domain and, thus, can determine that target parser SAGE::Journals was the right choice to continue article-level linking for title T. The ingest process just needs to place an according target parser overwrite in the portfolio of title T.

Matching domains against the Central Knowledge Base / Community Zone could be rule-based or AI-based. If several matches are found an AI-based algorithm could take the "best" one. If no matches are found you can still place Bulk::BULKdoi as target parser overwrite on the portfolio level instead of dropping the title fro the collection.

274 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Mathias Kratzer shared this idea  ·   ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment

Content: other

Categories

Feedback and Knowledge Base

(thinking…)