Nikol Stepan, SLSP
My feedback
14 results found
-
30 votesNikol Stepan, SLSP
supported this idea
·
An error occurred while saving the comment -
4 votesNikol Stepan, SLSP
supported this idea
·
-
28 votesNikol Stepan, SLSP
supported this idea
·
-
6 votesNikol Stepan, SLSP
supported this idea
·
-
25 votesNikol Stepan, SLSP
supported this idea
·
-
62 votesNikol Stepan, SLSP
supported this idea
·
-
129 votesNikol Stepan, SLSP
supported this idea
·
An error occurred while saving the comment Nikol Stepan, SLSP
commented
I agree with my colleagues that we should have the ability to determine which records are automatically marked for publication. Currently, there are cases where batches of records require special handling to correct the wrongly set management tag. Without proper monitoring and execution, this results in erroneous publication to OCLC, which requires corrective measures afterwards.
-
12 votesNikol Stepan, SLSP
supported this idea
·
-
47 votes
Thank you again for sharing your idea and for the thoughtful input you've provided. When we first discussed it, I was optimistic about exploring it further,
While I had hoped to prioritize this enhancement, it hasn’t gained the traction we typically look for to move forward. As a result, it’s unlikely to be implemented in the foreseeable future. That said, your feedback remains valuable, and I’ll continue to keep it in mind as our roadmap evolves.
An error occurred while saving the comment Nikol Stepan, SLSP
commented
It would be great if this development could also be applied to Primo VE. Users really struggle with the booking functionality. It would therefore be time to improve its usability. Many thanks for taking this into consideration!
Best regards
Nikol (SLSP) -
104 votesNikol Stepan, SLSP
supported this idea
·
-
172 votesNikol Stepan, SLSP
shared this idea
·
-
48 votesNikol Stepan, SLSP
supported this idea
·
-
131 votesNikol Stepan, SLSP
supported this idea
·
-
64 votes
Hi all,
This is to update that this issue is currently not planned. We will evaluate it again for next year's road map.
Best regards,
Yael.
Nikol Stepan, SLSP
supported this idea
·
It would be extremely helpful if Alma supported translatable labels at the representation level.
I would like to extend this request with a closely related need:
At the moment, all digital representations are displayed in Primo VE under the same generic label “Digital Versions”. This makes no distinction between a full digital resource and supplementary materials (usage type = auxiliary) such as tables of contents, covers, or reviews. For users, this can be misleading, since they expect complete content when clicking on it.
Although a free-text label can be added directly in the representation details (for example “Rezension”, see image), this label is static and cannot be translated. In multilingual environments this is not perfectly usable, as the same text appears for all languages.