Make consistent the use of CDI record data in Primo UI
Current CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.
The negative impact of this design decision includes:
* a user is confused by the Primo results list, as there is no indication as to why results were returned, even when the user has specifically targeted data such as an Advanced Search by a specific subject that is then nowhere to be found in the records displayed
* a user can't effectively filter results by facets, because when they do so and look at the records, they can see no relationship between their actions and the resulting records
* a user can't take advantage of lateral links, to generate an Advanced Search query of all the entries for the search term to expand their initial results set, such as all records in a specific subject, because there is no lateral link displayed in the record
* a user is missing key data when exporting by RIS to EndNote, RefWorks, BibTex etc, such as keywords not included, as well as this information not being included in other Send to options of Export to Excel, Print, and Email
Ex Libris design should be reviewed and made holistic and meaningful, to either:
1. Hide all the data ie if data is hidden from display, it should also be hidden from search and facets (and any other elements)
2. Show all the data ie if data is used in search and facets, then it should also be shown in display
Stacey van Groll
shared this idea
-
Stacey van Groll
commented
The set of 3 ideas which would drastically improve irrelevant and meaningless CDI results, by restoring and adding search tools which empower our users to target their search and their results, and and fixing the design decisions which make these tools very necessary:
-
Stacey van Groll
commented
Some user-focused reasons to vote:
* Do you get queries from confused users who have searched in specific fields like Subject, Title, and Author, and then get results that have no sign of their search terms in those fields?
* Do your users wonder why they don’t see features like lateral links to find more records in these results, and don’t get the expected data they searched also exported to EndNote? -
Peta Hopkins commented
There goes my last Primo vote. Thanks for sharing this idea.