Manu Schwendener
My feedback
230 results found
-
37 votes
-
104 votes
An error occurred while saving the comment An error occurred while saving the comment 60 and and 136 votes in the two ideas Floriane links to.
-
101 votes
An error occurred while saving the comment I do not understand why all other elements can be moved, but not this one.
https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/050Display_Configuration/010Configuring_Discovery_Views_for_Primo_VE#Ordering_the_ServicesAn error occurred while saving the comment NERS 7458, open for voting now.
An error occurred while saving the comment +1
-
13 votes
An error occurred while saving the comment Hi Christian
> define the e-mail field as a mandatory
As far as I know this shold come with the March 2023 release.
-
34 votes
An error occurred while saving the comment In the meantime you could use https://developers.exlibrisgroup.com/blog/report-a-broken-link-in-primove
-
802 votes
Thanks for the examples - we will review them and discuss our options.
Best,
Tamar
An error occurred while saving the comment Related: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45614302-fill-the-gap-of-open-access-cdi-records-not-marked: Make the open access icon more accurate
An error occurred while saving the comment +1
-
19 votes
An error occurred while saving the comment To prevent confusion:
> As well as with the current e-mail functionality of bibliographic citations, we
> would expect the e-mail to be automatically pre-filled when a user is logged
> inIn Primo BO, the email address of the logged in user is filled in as _receiver_ email address, not the _sender_.
---
-
47 votes
An error occurred while saving the comment Filtering for year is not precise, either:
If I search for corona OR covid published in 2023, I get 28 titles.
Most of them have 2023 as the date, but not all of them
https://basel.swisscovery.org/discovery/search?query=any,contains,corona%20OR%20covid,AND&pfilter=dr_s,exact,20230101,AND&pfilter=dr_e,exact,20231231,AND&tab=41SLSP_CDI&search_scope=CentralIndex&vid=41SLSP_UBS:live&mode=advanced&offset=0An error occurred while saving the comment > still broken in CDI
If it can't be fixed, remove the fields for month and day in advanced search.
(If it can be fixed, but only applies to CDI, it should only be visible for search profiles that include CDI)
---
Example: unlikely that there have been 113'450 CDI titles published about Covid or Corona in the first half of August 2022 (number is the same if I change to 1.1.2022-17.8.2022)
---
Additional point: if I look at the year facet, the range is from 2014 to 2023; this seems to be just a display error in the facet, though: when I change it to 2022-2022, the number of hits doesn't drop.
---
On the plus side: facets "From last week" and "From last month" should work correctly now
-
64 votes
An error occurred while saving the comment Hi
Is this solved by now?
(sorry, won't get notified if you reply)
-
167 votes
An error occurred while saving the comment As this won't happen in Primo VE for performance reasons, maybe the thread could/should be closed as "won't do" to release the votes?
An error occurred while saving the comment Did not make it though round 2 of NERS.
An error occurred while saving the comment NERS 7855, round 2 open for voting now.
An error occurred while saving the comment > This is functionality that I see in other library catalogs
And it's apparently a parity issue compared to Primo BO.
Via the Primo mailing list:
"BO has a top level “Available in the Library” facet to limit your results to just items that are available on shelf, while VE has a similarly named “Held By Library” facet that limits items to physical titles – whether or not they are on shelf."
An error occurred while saving the comment NERS 7855, open for voting now
An error occurred while saving the comment +1
-
42 votes
An error occurred while saving the comment Just to add:
I can do the search from
https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Long_combinations_of_Boolean_operators_and_truncated_terms_(wildcards)_return_0_resultsin our Primo VE (local records only) without triggering "No results found"
https://basel.swisscovery.org/discovery/search?query=any,contains,segregat*%20OR%20isolat*%20OR%20supermax*%20OR%20violen*%20OR%20effect*%20OR%20organ*%20OR%20media*%20OR%20influe*&tab=DiscoveryNetwork&search_scope=DiscoveryNetwork&vid=41SLSP_UBS:live&lang=en&offset=0 -
136 votes
An error occurred while saving the comment -
66 votes
An error occurred while saving the comment I understand this wish, but I would rather say:
In addition to the interface language of Primo, also let the patrons choose the language they want to be contacted in.
Reason: just because your interface has several languages doesn't mean that all the texts of your letters/emails have been translated to the same languages.
For example:
Our interface could be in German Italian French and English,
but maybe our letters only have German and English texts.---
The feature also needs to take in account patrons that are managed externally.
-
29 votes
An error occurred while saving the comment -
61 votes
An error occurred while saving the comment This is a parity issue:
While in Primo BO field 250 is not indexed for search out of the box, either (although it should be), it is easy to just add the field to general search.
An error occurred while saving the comment Very much agree.
Not only is it not searchable out of the box (which it should be), it can't easily be added for search.
-
22 votes
An error occurred while saving the comment Hi Jesse
As a workaround, have you tried
Ranking configuration – Resource type boosting?"To specify a negative boost, enter a value between 0.0 and 1.0 (such as 0.01)."
---
At least in Primo VE the change should take effect almost immediately, no need to re-index.
(Sorry, I won't get notified if you reply here)
-
0 votes
An error occurred while saving the comment -
255 votes
An error occurred while saving the comment > can be customized via Primo VE Normalization Rules
My guess is that this was hardcoded in 2018, but no longer is.
Could the idea be closed to free the votes?
An error occurred while saving the comment Sarah, is this still an open enhancement request? If yes, could you link to an example in your Primo VE catalog?
Thank you
(I won't get notified of your reply though, sorry)
An error occurred while saving the comment > 655 $a should be displayed in Primo as "Genre", not "Subject"
Please also vote for https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45177370-remove-655-from-the-subject-facet
-
1 vote
An error occurred while saving the comment -
60 votes
@Florianne you do already have the link Stacey is talking about (if I understand it correctly): it's at the end of the details section, called 'Collection path' / 'Chemin d'accès à la collection'
So all Ex Libris would need to do is show this link on the page of the collection, for ecample above the single titles.
(of course it should be a setting that the institution can choose to show or hide)