3 results found

1. Separate new and deleted portfolios behaviors of "Activate new portfolios associated with service automatically"

   "Activate new portfolios associated with service automatically?" has just 2 options (Yes and No), and it doesn't just control what happens when new portfolios are added to the collection; it also controls what happens when portfolios are deleted from the collection. I think there are probably additional use cases besides these as well.

   If "Activate new portfolios associated with service automatically?" is set to "Yes":
   
   New portfolios added to CZ collection are automatically activated in IZ
   Portfolios deleted from CZ collection are totally deleted from IZ

   If "Activate new portfolios associated with service automatically?" is set to "No":
   New portfolios added to CZ collection are not automatically activated in IZ
   Portfolios deleted from CZ collection become local and inactive in IZ and get a special status on the CZ updates task list, giving us a chance to check and either re-activate or activate in a different collection (say, if the portfolio moved to a different provider).

   We find these 2 options aren't granular enough for an important use case: There are many cases where we subscribe to a package that consists of all the titles offered by the publisher. We have perpetual access to the content published during the years we subscribe, and when the publisher issues a new title, it automatically joins our package. After entering our perpetual access data into our portfolios in these collections, we'd like to make sure they're not deleted by any CZ processes (as they're perpetual, so we want them to stay in our IZs!). However, we still want to make sure that when the provider adds a new title to the CZ collection, it is automatically added to our IZ.

   So, we want the "Yes" behavior for new portfolios but the "No" behavior for deleted portfolios, but there's no way to do that in Alma at present. An improved setup would have separate settings for new portfolios and deleted portfolios that each library could control, as shown in the attached mockup.

   As you can see, I have mocked up a new field "Delete portfolios removed from service automatically?" with the options "No, make local and inactive," and "Yes, delete completely." With this improvement, "Activate new portfolios with service automatically?" would just control the behavior of new portfolios, and the new "Delete portfolios removed from service automatically?" field would control the behavior of deleted portfolios.

   I shared this suggestion with colleagues in the CZMG, and I received support for the perpetual access use case as well as a suggestion of another use case: if a library has attached CZ portfolios to local records, they may wish to be able to control the additions and deletions behaviors separately so they are able to more closely control the portfolios attached to the local records.

   "Activate new portfolios associated with service automatically?" has just 2 options (Yes and No), and it doesn't just control what happens when new portfolios are added to the collection; it also controls what happens when portfolios are deleted from the collection. I think there are probably additional use cases besides these as well.

   If "Activate new portfolios associated with service automatically?" is set to "Yes":
   
   New portfolios added to CZ collection are automatically activated in IZ
   Portfolios deleted from CZ collection are totally deleted from IZ

   If "Activate new portfolios associated with service automatically?" is set to "No":
   New portfolios… more

   •  

   191 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   Planned  ·  AdminLiza Voloshin (Product Owner, Alma ERM, Ex Libris) responded

   Dear community,

   
   

   This idea is planned to be included in the February 2025 Alma release.

   
   

   Thank you once again for bringing our attention to this need.

2. Alma overlap analysis tool to include different identifiers in one comparison

   We would find it useful if the overlap analysis tool compare a list that includes different identifiers. i.e. ISSN, EISSN, ISBN, EISBN, TITLE in one comparison.
   Currently it only allows you to compare overlap within just one identifier. This is very important with collections from vendors that include different kinds of material.
   Being able to conduct this kind of overlap analysis is important for us in terms of making purchasing decisions and we feel that including this kind of feature in the overlap analysis tool would make this a more efficient process within Alma.

   203 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   Planned  ·  AdminLiza Voloshin (Product Owner, Alma ERM, Ex Libris) responded

   Dear community,

   We began working on this idea,

   Our solution will allow selecting up to 3 matching identifiers to be used in the comparison (in order). This will apply to both Collection Overlap Analysis and Look Up Titles. This is expected in Q3 2025.

3. Alma Metadata Editor needs a "delete portfolio" option.

   When am in the MD Editor, looking at a record for an e-resource, I can "View Inventory" to display the portfolios. From that half of the screen, I can view or edit the portfolios. Within that view or edit, I can click on the "Linking" tab and "Test access". If I find that the link has expired and the portfolio needs to be deleted, I want to be able to delete it at this point. But I have to return to the bib. record, release it, exit the editor, click back as many times as it takes to return to the search results display, then click on the "More actions" ellipses, and "Delete" before I can finally delete that portfolio. If there is more than one portfolio, I might assume that they are displayed in the reverse order of the way they appear within the MD Editor, but I verify that--which requires several more clicks. It takes 23 Alma steps to open, view, backtrack, and finally delete an old portfolio.

   When am in the MD Editor, looking at a record for an e-resource, I can "View Inventory" to display the portfolios. From that half of the screen, I can view or edit the portfolios. Within that view or edit, I can click on the "Linking" tab and "Test access". If I find that the link has expired and the portfolio needs to be deleted, I want to be able to delete it at this point. But I have to return to the bib. record, release it, exit the editor, click back as many times as it takes to return to… more

   111 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   Planned  ·  AdminLiza Voloshin (Product Owner, Alma ERM, Ex Libris) responded

   Dear community,

   This Idea is currently being handled by our development team, the delete option for portfolio will be similar to what exists for item in the MDE. As always, we take privileges into account, specifically in this case, only users with role "Electronic Inventory Operator - Extended" can delete portfolios, others will not see the new option. We're expecting this to be released by Q3 2025.