Petra Gratzl
My feedback
15 results found
-
45 votes
Petra Gratzl
supported this idea
·
-
60 votes
Petra Gratzl
supported this idea
·
-
266 votes
Dear colleagues,
Thank you for raising this idea.
This was part of the CERV cycle in 2025, but did not make it to the final list.
During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:
Option 1: New dedicated process type
- It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
- Items marked as "unavailable" will be considered as "not in place"
- The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules
Option 2: Mark a location as "unavailable"
- It will be possible to mark a location as "unavailable"
- All items in this location will be considered as "not in place"
- The difference from option 1 is that when an item…
Petra Gratzl
supported this idea
·
-
157 votes
An error occurred while saving the comment
Petra Gratzl
shared this idea
·
-
34 votes
An error occurred while saving the comment
Petra Gratzl
commented
We support this idea but would like to have the possibility in Primo Classic!
Petra Gratzl
supported this idea
·
-
17 votes
Petra Gratzl
shared this idea
·
-
79 votes
Petra Gratzl
supported this idea
·
-
5 votes
An error occurred while saving the comment
Petra Gratzl
commented
Hi Kirstie, I just played around in our Primo sandbox. We use formatting of PNX fields only in full display, but of course it is also possible for displaying fields in the results list. You can either add HTML tags (<b>) through normalization rules or use span tags and change display with the help of CSS. Of course you have to be careful and have to consider the consequences for export functions. So maybe you could use a local lds-field for the brief results and display it only there.
-
93 votes
Petra Gratzl
supported this idea
·
An error occurred while saving the comment
Petra Gratzl
commented
We, too, think that the configuration options for the Excel export are far too limited. We would like to remove the EL Permalink as well and also the PNX field "Vernacular Title" as in our Primo the title in original alphabet is part of display/title. But the field cannot be removed in the View Wizard.
Furthermore there are tags like <b> in CDI data. And also the tags of search words (<span class="searchword">) are exported to Excel...
The implementation of this 2020 feature leaves room for improvements. -
21 votes
Petra Gratzl
supported this idea
·
-
238 votes
Petra Gratzl
supported this idea
·
An error occurred while saving the comment
Petra Gratzl
commented
Also our users ask for more sorting options so that they can easily get a better overview of their active loans. Sorting options are indeed very limited and should be expanded.
-
61 votes
Petra Gratzl
supported this idea
·
-
77 votes
An error occurred while saving the comment
Petra Gratzl
commented
We'd also had feedback from users that exporting RIS format in the NUI takes many more clicks than before and should be UTF-8 encoding by default.
Petra Gratzl
supported this idea
·
-
47 votes
Petra Gratzl
supported this idea
·
An error occurred while saving the comment
Petra Gratzl
commented
In general the restriction to BIB and HOL data in Alma publishing is very displeasing. At Vienna University Library we have troubles in several fields to reach the status of services and the range of functions from before going live with Alma (coming from an Aleph system). Especially regarding deep links we miss the opportunity to use fields of the item records in the course of normalization. Therefor e.g. we had to find a rather complex workaround to build the new acquisitions lists on sublibrary level by writing the inventory date of the item into the respective holdings record based on a daily Analytics report.
Thus to only call for the content of the "public note" field of the items is by far not enough and is only part of the wishlist. We suggest to let Alma users decide which item fields (alternative call number, description, inventory date etc.) they need for Primo and to make it configurable which item fields to include into the Alma publishing process.
There is already another idea which is due to be implemented:
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/17509633-publishing-of-alternative-call-number-from-alma-to
There my colleague Christian already remarked in a comment that we also need fields like item description. -
56 votes
Petra Gratzl
supported this idea
·
Dear Stacey, we also thought that this inconsistency is a defect and opened a case for that (07163092: 'All Titles/Electronic Portfolios: Different display of ISBN in results list depending on type of search [ubwpeg]' ). Unfortunately we were told to create an idea as it is an enhancement... Another idea on that (with only 3 votes) was closed by EL in April this year :-( https://ideas.exlibrisgroup.com/forums/308173-alma?query=request%20for%20uniform