Lauren Gibbs
My feedback
11 results found
-
145 votesLauren Gibbs
supported this idea
·
-
26 votes
An error occurred while saving the comment Lauren Gibbs
supported this idea
·
-
83 votes
An error occurred while saving the comment Lauren Gibbs
commented
Hello Liza,
I personally would want to have the facet show collections that are localized in our IZ whether they are activated or not. The goal would be to activate a new portfolio in a collection we already are using, so being able to filter for only localized collections would help so much. Thanks!An error occurred while saving the comment Lauren Gibbs
commented
This would save staff so much time and searching. Please implement this.
Lauren Gibbs
supported this idea
·
-
216 votes
Hi Elizabeth, Katie, and everyone,
Thanks so much for sharing this idea!
From what I understand, it includes two main parts:
- Allowing institutions to edit the list of values in various fields, with a specific example being the “Implemented Authorization Method” field.
- Adding more fields and making them reportable in Analytics, along with a request for a flexible mechanism to support this.
Regarding the second point — adding a flexible mechanism is quite a complex change and could impact the timeline.
If you can point out around three specific fields that are most important to add first, it might be easier.
Looking forward to hearing your thoughts!
Thanks again,
Tamar
Lauren Gibbs
supported this idea
·
-
68 votesLauren Gibbs
supported this idea
·
-
50 votesLauren Gibbs
supported this idea
·
-
25 votesLauren Gibbs
supported this idea
·
-
4 votesLauren Gibbs
supported this idea
·
-
43 votes
Hi Liz,
We would like to better understand the situation of "portfolio changes vendors":
- Does this mean that the interface of the portfolio was changed?
- Is it enough to report this on collection/service level, and not in portfolio level?
- What actions would you take upon such report?
Thanks,
Tamar Fuches
Alma product team
Lauren Gibbs
supported this idea
·
-
159 votesLauren Gibbs
supported this idea
·
-
47 votes
An error occurred while saving the comment Lauren Gibbs
commented
This would be very helpful for us as well. We recently needed to make all of our Springshare A-Z database list databases discoverable in Primo. Some of these are portfolios in Alma, so we had to add local collections to make them discoverable as databases. This complicates the management of these resources and duplicates our work. We had to add a ton of notes and link POLs so we could trace the local collection back to the actual portfolio that containes the cost, renewal, and access settings. Being able to designate a portfolio as a database so it is discoverable as a database would solve this issue for us.
This would also be useful for us. We have multiple vendors where the same title for the same time period in the same report has usage on multiple platforms. Since there is only one field for the Counter platform setting at the collection and portfolio level, we cannot accurately calculate cost per use for these vendors. In order to accurately account for all usage of that title for that month and report, we would need at least 3 fields for Counter platform at both the collection and portfolio level, or another way to work multiple platforms into the same cost per use report. I recently discussed this over email with Yoel Kortick and he suggested I share this via idea exchange, then I saw it was already suggested, so I am adding my thoughts here.