AdminLiza Voloshin
(Product Owner, Alma Resource Management, Ex Libris)
My feedback
5 results found
-
157 votes
An error occurred while saving the comment -
15 votes
An error occurred while saving the comment Hey Sandra, thanks for sharing this idea!
Just to make sure I’m on the same page—are you suggesting adding this functionality to the Community Zone Updates Task List as a 'row action' (under the 3 dots icon, on each report)?Also, could you share a few examples of how you envision using this feature? For instance:
* What kind of report would trigger the need?
* Who would you typically need to contact?
* What information would you need to pass along?Best, Liza
-
82 votes
An error occurred while saving the comment Hi all,
Thank you for submitting this idea, it does make a lot of sense!
I wonder if you mean the facet would check whether the collection was activated from the CZ or is its service Available?Best,
Liza and the Alma Product Team -
104 votes
An error occurred while saving the comment Thanks Gill for the extra information!
While the perpetual dates are not currently reflected in Primo, there is an option in Alma to view the perpetual access dates (if the access type defined on the resource is 'perpetual' or 'current and perpetual') - in this case you should see both sets of dates in the e-portfolio search (see the screenshot attached), are there other places in Alma where you would want to see those dates?An error occurred while saving the comment Dear community,
thank you for this idea. In order for us to better understand the request, could you share a specific example of a portfolio - what is defined on the portfolio, what are the currently displayed dates and what would you like to see instead.Thank you,
Liza -
22 votesAdminLiza Voloshin
(Product Owner, Alma Resource Management, Ex Libris)
shared this idea
·
Currently, when collections are linked to the Community Zone (CZ), they can be configured as either auto-delete or non auto-delete. This setting determines the handling of activated portfolios that are subsequently deleted from the CZ:
* In auto-delete collections, portfolios removed from the CZ are automatically deleted from the Institution Zone (IZ).
* In non auto-delete collections, portfolios removed from the CZ are localized, deactivated, and retained in the IZ.
We propose an enhancement to the non auto-delete behavior:
Introduce an additional configuration option that allows localized portfolios to remain active in the IZ even after they have been deleted from the CZ. This would provide institutions with greater flexibility in managing CZ-linked e-resources and ensure continued access to portfolios that may still be relevant locally, despite their removal from the CZ.
As before, deletions from the CZ will be reported in the CZUTL.