Add a metadata correction layer for PCI
Many times when we found wrong metadata in PCI and reported to Ex Libris for correction, it took them a long time to contact the data vendors to make the corrections. Sometimes they never can get response or correction from the vendors, and the wrong metadata stayed in PCI without any changes. The wrong metadata is really misleading and cannot generate the correct OpenURLs for users to reach the full text articles. I would suggest Ex Libris to build an internal metadata correction layer for the PCI data to improve its quality. With this layer, even the vendors don't correct the wrong metadata, Primo and Primo VE still can display the correct metadata and generate the correct OpenURLs.
François Renaville commented
This feature should also allow Ex Libris staff to hide/suppress CDI records that should definitely not show up in Summon/Primo, but that have been delivered by the data provider to Ex Libris, like test records, dummy records or records from Open Access collections with a Link in Record availability type but where no file can be downloaded from (no file or in restricted access). From our experience, it can take ages before data providers make the necessary changes and Ex Libris's Index reflects the updates.
Louise Driscoll commented
This would be an excellent feature. A correction layer could crowd source corrections to the benefit of all PCI/CDI users
Ellen Augustiniak commented
Excellent! I asked in June 2019 (after a CDI webinar) for something related because, in my experience, it can take up to 6 months for corrections to be made. In my case, it was about deduplication. But the general idea is sound: it'd be great for libraries to get faster turnaround when metadata issues are identified.
My note: "I understand that failed grouping results can lead to a rather in-depth review to determine if the failure is a symptom of a critical issue.
However, I propose that there could be systems built in to the grouping process to more routinely and quickly handle exceptional results that your customers identify. I am one of the people in my library who trains librarians on using Primo, so I am familiar with Central Index metadata-match issues (unfortunately, rather more familiar than a non-developer really wants to be), as well as how much ExLibris relies on vendor data.
I am sympathetic to your developers and to Ex Libris’s need to set reasonable development priorities. I am also glad to know that my 6-months-long delay is unusual. Still, if it’s a common enough problem, I hope you all are looking at routinizing the handling of ... [metadata problems that customers identify]"
Shanyun Zhang commented
Since the Ex Libris Central Discovery Index (CDI) will replace the Primo Central Index and the Summon Index soon, I hope ExLibris can consider to have a metadata correction layer in the new CDI.
Shanyun Zhang commented
Thanks for the suggestion. I tried to edit the idea post, but cannot see a way to do it. It only gives option for Delete.
Galen Jones commented
I have voted for your idea but have a suggestion. Can you adjust your idea so that it also applies to the CDI (Central Discovery Index) please?