Under Electronic Service Editor to have the ability to remove portfolios in bulk.
In the electronic service editor you have the ability to deleted all the selected portfolios. I would like the ability to simply remove the portfolios in bulk from the collection.
Pat
shared this idea
Dana Moshkovits
responded
Clarification was provided regarding the functionality requested – which is not to delete portfolios but rather detaching portfolios from the collection and setting them as standalone portfolios.
Re-opening the idea.
-
Rhonda Reedy commented
I would like the ability to simply select all portfolios in an electronic collection and choose to deactivate them and then to delete them. Instead of one by one or by creating a set then running job to complete this action. This would be such a time saver and much easier for new staff to complete. We need to do this when cleaning up old collection such as for those that can now be set to autoload.
-
Anonymous
commented
Also appearing as NERS 2022 number 7768.
-
Diana Brooking commented
The label "Already Supported" is false and needs to be removed please.
The Service editor needs the options to "Remove Selected" and to "Remove a Set" for portfolios, in order to make them standalone. There is already a function to "Move Set of Portfolios" if they are moving from one collection to another.
It seems to me that as elsewhere in Alma, there is too much dependence on specific use cases rather than making functionality consistent. This makes for a confusing user interface and a need for continual enhancement requests. Any function for adding, removing, or moving portfolios to and from collections should offer: 1) doing it manually one by one; 2) doing it for a selected group; and 3) doing it by using an Alma set. As well as the spreadsheet functions offered through the Portfolio loader.
-
Karl Lehtonen
commented
i'd like to suggest an approach to this idea.
if we could run a job on a portfolio managed set to disassociate members of that set from their collection, rendering those portfolios standalone - so that they can then be identifiable as standalone (eg via repository search "is standalone"), or can simply be filed into an alternate collection - certainly valuable with publishers merging, demerging and moving content rights around. again, probably only applicable to local portfolios where local staff take into account applicable parser parameters or simply use static URLs. thanks for suggesting - i would very much like to see this implemented. :)