Manu_Schwendener
My feedback
179 results found
-
103 votes
An error occurred while saving the comment An error occurred while saving the comment Manu_Schwendener commented
Statement by Ex Libris about
PENH-I-28389 Increase number of possible local search/facet fields to at least 20
"Primo 2025 Enhancements cycle: This submission will not be included in the second ballot by the following Product Management statement:
As discussed previously, the current default limit of 10 such fields was introduced intentionally. We observed that many institutions were using these fields - designed for more advanced use cases - instead of simpler and more lightweight alternatives such as local fields for display purposes or the 5xx/9xx fields, which can also be configured for display and search with significantly less overhead.
By setting a default limit of 10, we encourage institutions to evaluate whether a simpler approach might meet their needs before resorting to the more complex normalization rule option. That said, we recognize that some institutions do have legitimate use cases that require more than 10 normalized search fields. As confirmed in our product direction, institutions that need additional fields beyond the default can request an increase via a Support ticket, and these requests will be approved.
At this time, we do not plan to expand the out-of-the-box limit, as the current threshold meets the needs of most institutions while encouraging efficient configuration. However, we remain committed to accommodating specific needs through the existing request process."
-
97 votes
This is currently not planned to be developed. We might evaluate it again in the future.
Currently we are removing the "Under review" status.
An error occurred while saving the comment Manu_Schwendener commented
Yael, maybe set this to "Closed" to free the votes?
An error occurred while saving the comment Manu_Schwendener commented
Ex Libris statement about PENH-I-28340
"Primo 2025 Enhancements cycle: This submission will not be included in the second ballot by the following Product Management statement:
After internal discussions, including past considerations when this enhancement was raised in NERS, we've concluded that this request is extremely complex to implement.
The main challenge lies in the variety of search scopes and tabs involved (e.g., blended, local, CDI, entire network, and deep search in Primo). Merging these into a single query presents significant technical and functional complications. Additionally, each search element—such as queries, facets, and filters—would need to be handled and reconstructed independently.
Given the scope of changes required, as well as the high cost and risk involved, we will not be able to proceed with this enhancement.
In addition to the reasons for rejections mentioned before:
* High risk of query overload: Merging multiple saved searches—including their associated filters and facets—can easily result in overly long or complex queries that exceed Solr's processing limits. This may lead to degraded performance or 0 results returned.
* Non-trivial facet logic conflicts: Saved searches often include different facet selections (e.g., multiple formats, date ranges, resource types). Merging these requires defining how to combine conflicting or overlapping filters—something that's not intuitive and prone to producing unexpected results.
* Ambiguity in user intent: It's unclear whether merging should mean combining results (logical OR), narrowing them (logical AND), or applying some prioritization. Different users may expect different behaviors, making it hard to design a consistent and satisfying user experience.
* Unsupported edge cases and fallbacks: Supporting all combinations of filters, keywords, scopes, and search types would introduce a high number of edge cases. Handling fallbacks gracefully (e.g., if facets don't exist in all merged contexts) adds significant complexity.
* Disproportionate development cost vs. value: Given the above challenges, implementing this feature robustly would require major development effort for a feature likely to be used by a small subset of advanced users—many of whom may still find the results confusing or unreliable."
An error occurred while saving the comment Manu_Schwendener commented
I think for this to work correctly, the patrons will need a way to turn FRBR off (https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/42531016-allow-patrons-to-disable-frbr-disable-frbr-in-ad).
An error occurred while saving the comment Manu_Schwendener commented
PENH-I-28340, open for voting now.
An error occurred while saving the comment Manu_Schwendener commented
NERS 8959, open for voting now.
---
Update 2.4.2024: place 4 in NERS, round 1
-
170 votes
An error occurred while saving the comment Manu_Schwendener commented
_Rapido_ CERV, now open for voting - please support this with as many votes as you can!
RAENH-I-1276 The automatic transfer of Patron Notes on Borrowing requests to the Lending library
An error occurred while saving the comment Manu_Schwendener commented
Manu_Schwendener supported this idea ·
-
1 vote
An error occurred while saving the comment Manu_Schwendener commented
+1
-
Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation
667 votesHi all,
We are currently reviewing this idea together with Alma.
We will update with any new information we have.
Best regards,
Yael.
An error occurred while saving the comment Manu_Schwendener commented
Dear Yael, your last update was over a year ago. Any news?
Kind regards
ManuAn error occurred while saving the comment Manu_Schwendener commented
(A similar problem, with another cause https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/41985421-possibility-to-disactivate-related-link-to-physica )
An error occurred while saving the comment Manu_Schwendener commented
Another example of how this problem messes up our catalog:
Publication format = Bilderbuch
https://basel.swisscovery.org/discovery/search?query=genre,contains,Bilderbuch,AND&tab=UBS&search_scope=UBS&vid=41SLSP_UBS:live&mfacet=genre,include,Bilderbuch,1&lang=en&mode=advanced&offset=0I only want to see the ones from a particular library ->
https://basel.swisscovery.org/discovery/search?query=genre,contains,Bilderbuch,AND&tab=UBS&search_scope=UBS&vid=41SLSP_UBS:live&facet=library,include,5504%E2%80%93112070590005504&mfacet=genre,include,Bilderbuch,1&lang=en&mode=advanced&offset=0But I get titles that UB Hauptbibliothek doesn't have, for example
https://basel.swisscovery.org/discovery/fulldisplay?docid=alma9948041300105504&context=L&vid=41SLSP_UBS:live&lang=en&search_scope=UBS&adaptor=Local%20Search%20Engine&tab=UBS&query=genre,contains,Bilderbuch,AND&facet=library,include,5504%E2%80%93112070590005504&mode=advanced&offset=0An error occurred while saving the comment Manu_Schwendener commented
> In which cases the relation is correct
Dear Yael
For the display and functions of Fulfillment / Getit and facets in Primo, only this example is correct
it has a MARC field 773 $w
773 0#$tPro Natura lokal Basel $g2015, Nr. 4, 31 S. $q2015/4/31 $gyr:2015 $gno:2015 $w(IDSBB)001400350DSV01
----
All the other relations should only be visible under Details in the full record display. There they can be a link which leads to the other bib record, but no other function should be generated.
An error occurred while saving the comment Manu_Schwendener commented
Basel - UB Hauptbibliothek has this title.
'Show more locations' shows me
Basel - Uni Geschichtewho do NOT have this title.
-----
"Available at ... and other locations"
This is not true. Only "Basel - Uni Philosophie" has it.
---
This is the only case where we want to show "Locations for related titles":
773 0#$tPro Natura lokal Basel $g2015, Nr. 4, 31 S. $q2015/4/31 $gyr:2015 $gno:2015 $w(IDSBB)001400350DSV01
An error occurred while saving the comment Manu_Schwendener commented
Dear Yael
This is great to hear, thank you.
An error occurred while saving the comment Manu_Schwendener commented
NERS 8781, open for voting now.
Please vote to make our catalog less frustrating for our patrons.
Manu_Schwendener supported this idea ·
-
24 votes
Manu_Schwendener supported this idea ·
An error occurred while saving the comment Manu_Schwendener commented
The ability to add logical sets from the NZ to our local search scope would be great for us.
-
61 votes
An error occurred while saving the comment Manu_Schwendener commented
This is possible by now for single titles.
For sets, see this follow up: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/49922184-alma-collections-allow-to-add-multiple-titles-fro
-
317 votes
Thank you for this idea.
We are currently examining it and will update once we have more details.
An error occurred while saving the comment Manu_Schwendener commented
A newer example:
How it should look:
https://www.merianverlag.ch/.imaging/cmv-w1200h1200-jpg-90/dam/268bd2a3-ebb5-443a-ab71-18922dd46aa0/SGB-Buchreihe-2289_1Ebene.jpgAn error occurred while saving the comment Manu_Schwendener commented
Dear Yael, could we get an update on this?
Thank you and kind regards
ManuAn error occurred while saving the comment Manu_Schwendener commented
For comparison see https://swisscollections.ch/Record/991057940819705501?sid=126841 (Alice's example), scroll to and open "Hierarchy / Context"
An error occurred while saving the comment Manu_Schwendener commented
List of fields for which this change should be made. Others please add if something is missing.
MARC 21:
773 for analytica
- my example from July 12, 2024 on this page
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma9972771758805504&lang=en&context=L
$gNo. 8 (2023) $gyr: 2023 $gno: 8Add the first $g in front of the title of the child entry:
No. 8 (2023) FashionUse the more normalized $g subfields for sorting
- Alice Robinson's example from April 2, 2022 in the older idea exchange entry
https://uzb.swisscovery.slsp.ch/discovery/fulldisplay?vid=41SLSP_UZB:UZB&docid=alma990047977300205508&lang=en&context=L=> If there is a $q, use that for sorting (but the first $g for display)
Example
$gVolume 12, Number 2 (2020), 60 $gyr:2020 $gno:12 $q12/2/2020/60---
800 when the parent title has an author in field 100
- the Brecht example in post 1
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma993707790105504&lang=en&context=L&isFrbr=true
- from an inquiry I got today:
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&tab=UBS&docid=alma996830890105504&lang=en&context=L---
810 when the parent title has a corporate name as author in field 110
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&tab=UBS&docid=alma9970764540105504&lang=en&context=L---
811 when the parent title has a congress name as author in field 111
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&tab=UBS&docid=alma9972827070905504&lang=en&context=L---
830 when the parent title doesn't have a 1xx field. This is the most common case = Series
Example https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&tab=UBS&docid=alma991036390105504&context=L---
From the older thread (https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/42926031-number-and-sort-the-volumes-in-multi-volume-works), posted May 28, 2024:
CNMARC field 200 subfield $h
An error occurred while saving the comment Manu_Schwendener commented
Here's another exmple
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma9972771758805504&lang=en&context=LHow it looks:
Related titles
Units : Construction
Units : Decoration
Units : Fashion
Units : Interiors
Units : Resources
Units : The plant-based issue[as long as it's alphabetical, "The" should not be used for sorting]
How it should look:
No. 4 (2021) The plant-based issue
No. 5 (2021) Decoration
No. 6 (2022) Resources
No. 7 (2022) Construction
No. 8 (2023) Fashion
No. 9 (2023) InteriorsAn error occurred while saving the comment Manu_Schwendener commented
NERS 8869, open for voting now.
Rephrased for better understanding:
Related titles in Primo VE bib display: sort by enumeration
When records have bib-to-bib relationships via 76X-78X and 8XX, the list of related titles is displayed in the Details section of the series/host record. The list is currently sorted alphabetically by the title of the related bib.
Instead, we would like to be able to configure Alma so that Related Titles are sorted logically by sequence or volume.For example, the current display is:
Analyzed Title A vol. 3
Analyzed Title B vol. 1
Analyzed Title C vol. 2.We would like this sorted by volume instead:
Analyzed Title B vol. 1
Analyzed Title C vol. 2
Analyzed Title A vol. 3When related via field 773, titles should be sorted by $q (enumeration).
For all other related fields 76X-78X, titles should be sorted by $g (related parts).
8XX fields should be sorted by $v (volume/sequence).How it looks at the moment:
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma993707790105504&lang=en&context=LHow it should be looking:
https://www.suhrkamp.de/werkausgabe/bertolt-brecht-werke-grosse-kommentierte-berliner-und-frankfurter-ausgabe-30-baende-in-32-teilbaenden-und-ein-registerband-leinen-w-17Manu_Schwendener supported this idea ·
-
11 votes
Manu_Schwendener supported this idea ·
-
37 votes
Manu_Schwendener shared this idea ·
-
3 votes
An error occurred while saving the comment -
155 votes
An error occurred while saving the comment Manu_Schwendener commented
> populating new book lists in our Discovery Collections
Yes, exactly
An error occurred while saving the comment Manu_Schwendener commented
> for the Collection Discovery feature
There's the facet group "New records" in Primo, with "last week", "last month" and "last three months", but they can't be used to build a set that then populates the logical collection.
Manu_Schwendener supported this idea ·
-
19 votes
Manu_Schwendener supported this idea ·
-
18 votes
Manu_Schwendener supported this idea ·
-
11 votes
An error occurred while saving the comment Manu_Schwendener commented
I agree that if you add a link behind your logo, you should also be able to describe where the link will lead.
> half the users expected the logo to go back to the main Primo VE search landing
> page rather ... (as many libraries have configured)This is the default - when you don't put an external URL behind the logo - and doesn't need configuration.
-
47 votes
An error occurred while saving the comment Manu_Schwendener commented
This should be fixed
https://knowledge.exlibrisgroup.com/Primo/Release_Notes/002Primo_VE/2025/010Primo_VE_2025_Release_Notes?mon=202504BASE"April 2025 SF: 05305640, 05310473, 05319841, 05328486, 05330867, 06027317,06259460, 06755228, 06877607, 06989963, 07214655, 07807403
When filtering by a specific date (with months) in Advanced Search, out-of-range records are returned. This has been fixed." -
425 votes
An error occurred while saving the comment Manu_Schwendener commented
You can activate stemming, which I personally loathe because it shows results that don't contain my search terms.
-
3 votes
-
133 votes
An error occurred while saving the comment Manu_Schwendener commented
What Jahn describes above leads to the following strange situation in our IZ, which is part of the same consortium.
We have deduplication deaktivated in our view.
In some cases, a link from 776 is created automatically, and works as expected
shows a link “Available in other form“, which links to this online version
https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma9972335550005504&lang=en&context=L&adaptor=Local%20Search%20Engine&query=any,contains,education&facet=tlevel,include,available_p&facet=rtype,include,journals&offset=0The field responsible for this is a 776 $t
https://basel.swisscovery.org/discovery/sourceRecord?vid=41SLSP_UBS:live&docId=alma998305080105504&recordOwner=41SLSP_NETWORK776 08$iErscheint auch als Online-Ausgabe $tAnthropology & education quarterly
---
In many cases, we add a $x to the 776 field
https://ubs.swisscovery.slsp.ch/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma99972970105504&lang=en&context=L776 08$iErscheint auch als $nOnline-Ausgabe $tRecht $x2504-1487
As we're in a consortium, all IZs see the same 776 fields. But that link only works in the IZs which _have_ the online version with ISSN 2504-1487.
What I would expect: that there is a check for this, and the link is not active, but the information stays visible, when the value in $x does not exist in the same IZ.
(Or, if that is not possible: 776 is hidden when the value in $x does not exist in the same IZ.)
What acutally happens: if no link via $x is possible, a title search is started.
Which leads to unusable results. Which means we had to suppress the display of all 776 with $x, also in the IZs where the link would work correctly.
This is an unsatisfying situation.
-
184 votes
An error occurred while saving the comment Manu_Schwendener commented
> Bluesky = priority
Yes, also for me.
An error occurred while saving the comment Manu_Schwendener commented
Bluesky logo files https://drive.google.com/drive/folders/16mlJPfWNnc6jj-3vGZ88SFysIY13GBp0 , via https://bsky.social/about/blog/press-faq
If there are difficulties for Bluesky, try contacting them on Github https://github.com/bluesky-social/social-app/issues or @ https://bsky.app/profile/pfrazee.com
Manu_Schwendener supported this idea ·
Maybe this should be set to Closed, to release the votes?