Multiple CDI records for one article by the languages of its metadata
Please do not use language filter when CDI merges records. It creates multiple records for one article, which confuses our patrons. (Case 00881023, 00824833) If CDI cannot merge them well, please provide a kind of "See Also" link to other records which have the same DOI. (CDI e-book records already display "Chapters of this book" link under the availability status.)
Many of non-English articles have English version metadata too because many journals oblige it. Western aggregators index English metadata whereas local aggregators index local language metadata. The problem is most of times they don't care about the language of the full-text but of metadata. So in those cases the language facet is useless because when our patrons open the full-text of a English record the full-text is actually written in non-English language.
When one of the records (or both) has linking problems, the situation gets worse. One of my patron was so upset and pointed out it's hard to imagine that somewhere on the search result list there might be another record in different language for the same article. It's understandable, because only the volume and issue number and the page ranges are identical on the list.
If Primo provides the link to the other records for the same article, it will be more discoverable. The chance is low that the original article and its translated version (if it exists) share the same DOI, so it could be used to create the link.
Anonymous
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 30 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Primo.
Best regards,
Primo Product Team