Stacey van Groll
My feedback
-
7 votesStacey van Groll
supported this idea
·
-
6 votes
An error occurred while saving the comment Stacey van Groll
supported this idea
·
-
22 votesStacey van Groll
supported this idea
·
-
10 votesStacey van Groll
supported this idea
·
-
49 votes
An error occurred while saving the comment Stacey van Groll
commented
Doesn't that CSS code just hide the suggestion, Manuela? The DYM index is taking effect on the results in Primo VE, right? So the results would still be highlighted as 'light', using the original example.
I often think that the downfall of this feature is what seems to be the unnecessary complexity, so it is almost impossible to explain.
For example, if I test this on one of my local data sources with Hmong consumers, I get two results with among and consumers highlighted. If I choose the suggestion for 'among consumers', then I get 19 results, some of which have among and consumers also clearly in the data, including the title. But the key is that the two which showed up originally have apparently been triggered by the Levenshtein distance aspect of the distance between the two words (it's not documented what that is specifically that I can find), whereas in the other records the words among and consumer are further apart.
Try explaining that to a user!
And there's also the issue that only the local index is used to build the index from title and authors, which drastically reduces the value because it's missing out on more unique and newer terms that might only be in emerging research topics which only have articles thus far in CDI, which are actually more likely for users to misspell and need help with. -
161 votesStacey van Groll
supported this idea
·
-
416 votes
Thank you for this idea. we will further analyze the option to allow secondary resource type to cover the use cases raised here.
Stacey van Groll
supported this idea
·
-
296 votesStacey van Groll
supported this idea
·
-
56 votesStacey van Groll
supported this idea
·
-
18 votes
An error occurred while saving the comment Stacey van Groll
commented
Hi Manu - it should just be 'User interface' category, as this is not specific to VE model but for Primo as a product.
-
68 votesStacey van Groll
supported this idea
·
-
10 votesStacey van Groll
supported this idea
·
-
19 votesStacey van Groll
supported this idea
·
-
181 votes
Hello all,
We are actively discussing the 506 field with the Community Zone Management Group to determine the best next steps for this metadata for ebook content.
As we make progress, I will update here what our plans are.
Thank you for your contribution!
Best,
Rael
An error occurred while saving the comment Stacey van Groll
commented
I agree with other comments here that this should just be automatic, and we shouldn't have to ask for it (and spend valuable votes). This is a deliberately integrated item between Alma and Primo to trigger the OA icon and facet in both, and there is an expectation that Ex Libris ensures such features stay in alignment by necessary metadata.
-
1 vote
An error occurred while saving the comment Stacey van Groll
commented
A proviso please to make this configurable. We have use cases where we need users without accounts to view this information, such as for our licenses allowing access by walk-in users to our physical locations. We also make an effort to have as many Open Access and Open Educational Resources (OER) resources as possible, and we would like users here also without accounts to be able to see the information we choose to add to associated licenses.
-
Primo Analytics - Add Actions for clicks on View It links, for both Link in Record and Link Resolver
99 votesAn error occurred while saving the comment Stacey van Groll
commented
The Ex Libris statement in response to recommendation of National Information Standards Organization (NISO) Open Discovery Initiative (ODI) states that Primo is compliant with "Report on total number of click-throughs per month." 3.3.4.2 (3) by "Primo and Summon provide this information. On Primo this is counted with the combination of the link resolver and the links in record reports, Summon provides one report for both."
This is not correct, as is seen in this submission, as there are no analytics recorded for Link in Record reports in Primo Analytics.
https://exlibrisgroup.com/open-discovery-initiative/Stacey van Groll
shared this idea
·
-
7 votes
An error occurred while saving the comment Stacey van Groll
commented
I'm sorry to have no more votes, but I heartily support this idea, especially when there is the known gap of electronic collections not married to their bibliographic record in Analytics, so therefore no way to tell the suppression aspect.
-
7 votes
An error occurred while saving the comment Stacey van Groll
commented
Hi Saleena - did Francois's post on the listserv not meet your needs for adjusting the display, not the source data?
-
13 votesStacey van Groll
supported this idea
·
-
1 vote
An error occurred while saving the comment Stacey van Groll
commented
Hi - This idea is already submitted here with currently 78 votes: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/36909595-a-z-option-in-primo-ve-journal-search
Great idea. We sorely need Ex Libris to recognise that automation is not always awesome and we need to be able to stop Alma from "helping" when it is not helpful.