Flag individual articles in Alma as being unavailable.
ExLibris cannot verify accuracy between supplied metadata and a referenced database. As a result, there are times when an article is listed in Primo as available online; However, when the patron tries to retrieve the article, the database returns a not found error. This has been frustrating for our patrons.
Currently there is no way to flag an individual article as being unavailable. As a result, this becomes a recurring error for our patrons; with no option to correct.
Suggest providing a way to:
1. flag individual articles as available / not available by database
2. date and notes on why the article was flagged
3. ability to delete the flag when no longer needed.
William Fischer
shared this idea
-
Stacey van Groll
commented
I'm wondering about the nature of the solution and if it would be better enhancing the matching process en masse, rather than adding a mechanism for manual individual flagging.
Can you advise the situation with example, which Ex Libris states currently has no technical solution? One of those instances where I wish we could still see cases so I could look up the details myself!
Is it something like an aggregator which just randomly doesn't have a particular article? -
William Fischer
commented
Good question on why the metadata could not be corrected. Below is the case comment from ExLibris that initiated my enhancement suggestion.
======
Dear William,
Thank you for your patience.
I would like to update you that I have consulted this issue with our Content Operations team. We have checked all the technical options and for now, there is no functionality that addresses this kind of situation.
In our products, our goal is to reflect the provider’s content and metadata, and therefore we cannot know whether the particular record is available in the target platform or not.
The system calculates the availability of all the resources in CDI based on an ISSN/ISBN match and coverage, and this is also true for records that are defined as an article since the identifier is ISSN, regardless of metadata source and therefore you are getting this record as available.
The next step is to pursue this as an enhancement. We strongly recommend that you pursue this enhancement through the IGELU enhancement voting process. I have attached a Knowledge Article titled “Enhancement Process - Common Q&A” that provides more information on IGELU enhancement voting.
Ex Libris also offers an Ideas Exchange (http://ideas.exlibrisgroup.com). The Ideas Exchange is a place where you can submit new ideas, and comment on or support (vote for) ideas posted by other users.
For more information on the Ideas Exchange, please see our FAQ: http://ideas.exlibrisgroup.com/knowledgebase/articles/690945-ex-libris-idea-exchange-faq. -
Stacey van Groll
commented
This seems like a metadata issue to me that would be best reported with a request for metadata correction in CDI and/or Alma, to ensure CDI records are not marked as available online per Alma coverage information when this is not true.
It would be helpful to have the details from the stated cases to understand why the metadata correction is not possible. -
William Fischer
commented
Refer to Case: 07004864 and Case: 06954204 for examples of this issue