Manu Schwendener
My feedback
-
374 votes
An error occurred while saving the comment An error occurred while saving the comment Manu Schwendener commented
NERS 7888, open for voting now
An error occurred while saving the comment Manu Schwendener commented
Alphabetical sort will not be fully possible as long as only 50 facets can be displayed.
An error occurred while saving the comment Manu Schwendener commented
[for those who can vote in NERS: 6414]
-
121 votes
An error occurred while saving the comment Manu Schwendener commented
> for the first one you have to click 'include', before you can exclude it
Just found out that this behaviour is not consistent – for some facets Exclude works as expected, also if you only exclude one (Primo VE).
An error occurred while saving the comment Manu Schwendener commented
Excluding several facets at once is possible, but for the first one you have to click 'include', before you can exclude it.
An error occurred while saving the comment Manu Schwendener commented
Change background of the exclude icon (thank you, FF):
.available-facets .section-content .md-chips .md-chip .md-button:before
{background-color: #fff; }----
If somebody knows how to right align the icons, please let me know.
An error occurred while saving the comment Manu Schwendener commented
Change border colour of the include check box:
md-checkbox .md-icon {
border-color: #DDD;
}---
Change background colour of 'Apply Filters':
.multiselect-submit .multiselect-submit-inner .md-button.md-primary, .prm-positive-bg {
background-color: #008488;
}.multiselect-submit:hover .multiselect-submit-inner:hover .md-button.md-primary:hover, .prm-positive-bg:hover {
background-color: #A5D7D2;
}
---Change the colour of the exclude icon:
.available-facets .section-content .md-chips .md-chip .button-exclude {
color: #ECECEC;
}---
Thank you, JC!
An error occurred while saving the comment Manu Schwendener commented
Thank you, Nancy!
An error occurred while saving the comment Manu Schwendener commented
swisscollections.ch has an elegant solution
(Not Primo / Primo VE)
An error occurred while saving the comment Manu Schwendener commented
I see that Buffalo has made the first of the steps by making include static:
https://search.lib.buffalo.edu/discovery/search?query=any,contains,discovery&tab=LibraryCatalog&search_scope=MyInstitution&vid=01SUNY_BUF:catalog&offset=0
(Primo VE)---
And as Anne mentioned, Washington shows both include and exclude (Primo)
https://alliance-primo.hosted.exlibrisgroup.com/primo-explore/search?search_scope=all&tab=default_tab&institution=01ALLIANCE_UW&vid=UW&displayMode=full&bulkSize=10&highlight=true&dum=true&pcAvailabiltyMode=true&query=any,contains,facets&displayField=all&queryTemp=facetsAn error occurred while saving the comment Manu Schwendener commented
There's another problem with the UX as it is at the moment:
When you do an OR selection by putting a checkmark left to several facets at once, this only works correctly for facets within the same facet type.
If you combine facets from different types, the search that is done is AND, not OR.An error occurred while saving the comment Manu Schwendener commented
"making the filter options static - including the persistent (lock) option- would go a long way to improving the usability of facets for users."
This is also true in Primo VE.
An error occurred while saving the comment Manu Schwendener commented
[Keren is right in her reply]
-
700 votes
Thank you for this idea. We are currently reviewing it and discussing it also with the Alma team.
Manu Schwendener supported this idea ·
An error occurred while saving the comment Manu Schwendener commented
Did not make it through round two of NERS.
I'm glad it's under review, this is a difficulty for our patrons.
An error occurred while saving the comment Manu Schwendener commented
NERS 7896, round 2 open for voting now.
An error occurred while saving the comment Manu Schwendener commented
NERS 7896, open for voting now
"Unify Primo My Library Card display of loans/requests from all institutions in the network"
An error occurred while saving the comment Manu Schwendener commented
> You have to change "All Institutions" at the top of the list to "Has Activity." But, it defaults
> back to "All Institutions" the next time you login to your account.Yes, this is bad UX.
"Has activity" should be the only option, anyway (until they're all shown on one page).
-
384 votes
Manu Schwendener supported this idea ·
-
35 votes
Manu Schwendener supported this idea ·
An error occurred while saving the comment Manu Schwendener commented
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.
-
562 votes
Thank you - this idea is now merged with the Alma idea -
An error occurred while saving the comment Manu Schwendener commented
Via the Alma mailing list:
"... we agreed on including NERS #7880 in this year’s enhancements and having the extra points removed from those available in 2023."
Meaning this should be possible by autumn 2023.
An error occurred while saving the comment Manu Schwendener commented
Cross your fingers: this got to place 5 of the 2022 NERS voting, round 2.
From the announcement via Alma mailing list:
"Members of the Alma Product Working Group will meet with Ex Libris representatives in July to discuss options regarding the enhancement that ranked fifth in the final vote."
An error occurred while saving the comment Manu Schwendener commented
Now in Alma idea exchange by Anonymous: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/45152647-enable-alma-collections-items-linked-to-logical-se
An error occurred while saving the comment Manu Schwendener commented
Plus 529 votes from Primo idea exchange https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/40856926-update-collections-automatically-with-changes-to-l
An error occurred while saving the comment Manu Schwendener commented
> Could you please close the Idea and reopen as an Alma idea?
a) we can't close an idea ourselves (which I understand)
b) starting over in Alma would mean loosing the 522 votes this idea has
An error occurred while saving the comment Manu Schwendener commented
Did not make it through round 2 of Alma NERS voting.
An error occurred while saving the comment Manu Schwendener commented
_Alma_ NERS 7185, open for voting now.
An error occurred while saving the comment Manu Schwendener commented
This will come to NERS voting in 2021, but under Alma.
An error occurred while saving the comment Manu Schwendener commented
+1
-
206 votes
Thank you for this idea. We are currently examining it.
An error occurred while saving the comment Manu Schwendener commented
Thank you for the update, Yael
Manu Schwendener supported this idea ·
An error occurred while saving the comment Manu Schwendener commented
There's an additional UX aspect to it:
Our default sort is 'Relevance'
https://basel.swisscovery.org/discovery/search?query=any,contains,gr%C3%BCne%20heinrich%20gute%20schriften%201945&tab=41SLSP_DN_CI&search_scope=DN_and_CI&vid=41SLSP_UBS:live&lang=en&offset=0Once the patron clicks on the first title, the sort changes to 'Date - newest' without the patron actively changing the setting – this should just not happen.
(Also wrong: why do I see the author's name three times?)
An error occurred while saving the comment Manu Schwendener commented
> I believe this a flaw in Primo VE design. If you search for Iliad Lattimore in a
> Back Office site, open the FRBR group, and change the results sort to be by
> Relevance, then the Lattimore versions will be right at the top of the list. If you
> do the same thing in a Primo VE site, the results ranking is clearly changed
> somehow, but there is no obvious meaning to this change. It is not by
> relevance to the term searched, [...] Lattimore is nowhere in the top 50 results.Another example:
https://twitter.com/th_schmid/status/1501923145804140544I search for his terms, with the additional step to re-sort the list of versions to 'Relevance' -> what he's looking for is shown as hit number 10.
=> But when I switch from FRBR Generic to FRBR Preferred *, Primo VE is perfectly able to show the work the patron is looking for, see screenshot.
* we probably won't do that, because it's confusing in other ways
An error occurred while saving the comment Manu Schwendener commented
Only made it to rank 60 in NERS 2022.
If you have a case open with Ex Libris about this, please add that it's a parity issue and needs to be fixed for Primo VE.
Thank you.
An error occurred while saving the comment Manu Schwendener commented
NERS 7843, open for voting now.
An error occurred while saving the comment Manu Schwendener commented
In Primo VE there is no option to sort the FRBR versions by Relevancy
An error occurred while saving the comment Manu Schwendener commented
> I believe this a flaw in Primo VE design
I completely agree.
If I switch from FRBR Generic to FRBR Preferred, I get to see "the highest ranked record from the results set" in the short title list.
This is the record that should be the FIRST title in the list of versions, also with the Generic setting.
This is very much not the case.
An error occurred while saving the comment Manu Schwendener commented
> An alternate approach to this might be to enable "search within" the FRBR group titles,
> with results limited to those matching termsI do not agree. I search for something = I only want to see results that contain my search terms.
There should not be an additional step "now show me the things I actually was searching for".
An error occurred while saving the comment Manu Schwendener commented
> FRBR groups and the display of versions within them does not consider the relevancy of
> the terms searched.
This makes our catalog basically a joke. We are a university library and you can't search for an exact title.An error occurred while saving the comment Manu Schwendener commented
I think the way FRBR groups work at the moment is not logical and should be changed.
> a user is searching for ... Homer's Iliad translated by Richmond Lattimore
114 versions found.
It's ok to bundle different versions in a FRBR group, but only those works that contain the search terms.
Even advanced search isn't helping.
And the author facet isn't helping because it can't show more than 50 entries and Lattimore is not among them.
An error occurred while saving the comment Manu Schwendener commented
Related: Allow patrons to disable FRBR https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/42531016-allow-patrons-to-disable-frbr-disable-frbr-in-ad
-
8 votes
An error occurred while saving the comment Manu Schwendener commented
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)
-
1 vote
An error occurred while saving the comment -
78 votes
An error occurred while saving the comment Manu Schwendener commented
+1
-
245 votes
An error occurred while saving the comment Manu Schwendener commented
> 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 Manu Schwendener commented
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 Manu Schwendener commented
> 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
-
49 votes
Thank you for this idea. We are currently reviewing it and waiting also for the Primo product working group confirmation on this.
Best regards,
Yael.
An error occurred while saving the comment Manu Schwendener commented
> none of the rules for controlling your own metadata in any respect (facet,
> display, search, addata, links, browse, sort, etc) should be hardcoded.I agree of course.
An error occurred while saving the comment Manu Schwendener commented
> VE sites must ask Ex Libris to make this change
This is what we did in 2020, but to no avail.
We got told that it was 'in internal discussion' at Ex Libris.
An error occurred while saving the comment Manu Schwendener commented
We have been trying to get this solved since before we went live in December 2020.
Manu Schwendener shared this idea ·
-
5 votes
An error occurred while saving the comment Manu Schwendener commented
> If I use "*" and set the year 0001-2025
I just was able to do that in a CDI only search profile, getting facets for the results. But now I can't reproduce it.
An error occurred while saving the comment Manu Schwendener commented
NERS 7373, open for voting now.
An error occurred while saving the comment Manu Schwendener commented
Follow up of https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35373859-ability-to-run-blank-search-with-limiters-primo.
If I use "*" and set the year 0001-2021 I get the result list, but I what I'm mainly interested in are the facets.
Manu Schwendener supported this idea ·
-
1 vote
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment -
36 votes
Manu Schwendener supported this idea ·
-
10 votes
An error occurred while saving the comment Manu Schwendener commented
'Requesting flexibility in local resource type configuration [Primo VE]' made it through round two of NERS and should be possible by autumn 2023.
An error occurred while saving the comment Manu Schwendener commented
+1
-
104 votes
An error occurred while saving the comment Manu Schwendener commented
'Filter resource type by magazines' did not make it though round two in NERS.
-
269 votes
Thank you posting this idea. Moving it to under review for further analysis.
An error occurred while saving the comment Manu Schwendener commented
Did not make it through round two of NERS.
An error occurred while saving the comment Manu Schwendener commented
NERS 7893, round two open for voting now.
An error occurred while saving the comment Manu Schwendener commented
+1
-
20 votes
An error occurred while saving the comment Manu Schwendener commented
Did not make it through round two of NERS.
An error occurred while saving the comment Manu Schwendener commented
NERS 7697, round two open for voting now.
An error occurred while saving the comment Manu Schwendener commented
Not only should they be mutually exclusive, home delivery shouldn't be hidden under pickup options. It's the opposite of pickup.
NERS 7256, open for voting now.
Did not make it through round 2 of NERS 2022.