Katherine O'Brien
My feedback
32 results found
-
172 votesKatherine O'Brien
supported this idea
·
-
233 votes
An error occurred while saving the comment -
276 votes
An error occurred while saving the comment Katherine O'Brien
commented
I think the fact that the Product team asked for clarification on this Idea shows that standard purchasing workflow needs of libraries really isn't understood by Ex Libris.
We decided not to use purchase requests because it creates a local portfolio when the request is approved. We use the EBC integration profile, which only checks for existing CZ portfolios, not local ones, and so we end up with duplicate portfolios in our collection. The CZ portfolios are preferable but it is too much work to de-dupe and the integration profile is more valuable to us than the purchase request feature.
The big appeal of e-titles in Alma is the CZ. It makes no sense to have a local portfolio created without the ability to link to a CZ portfolio with minimal hassle.
Ex Libris also seems to struggle with the idea of libraries purchasing more user licenses for an existing electronic title, which fits with the confusion around this Idea also. If it's in the same collection, you don't want a new portfolio just because you purchased an extra user license.
As Vanessa said - the desire is to link the request to a portfolio from the CZ. We want to minimise the number of local portfolios in our Alma, so that we have minimal management required for portfolios. Being able to link the request to CZ portfolios would in theory also address the local/CZ portfolio duplication issues.
This would be really really useful for us.
-
241 votesKatherine O'Brien
supported this idea
·
-
59 votesKatherine O'Brien
supported this idea
·
-
105 votesKatherine O'Brien
supported this idea
·
-
16 votesKatherine O'Brien
supported this idea
·
-
67 votesKatherine O'Brien
supported this idea
·
-
27 votesKatherine O'Brien
supported this idea
·
-
55 votes
An error occurred while saving the comment Katherine O'Brien
commented
This is the only thing holding us back from implementing purchase requests (which would be very beneficial when we roll out Leganto across our institution). We are currently trying to work out a cumbersome workaround to fix the duplicate issue that occurs when our Proquest Ebook Central integration profile ignores local portfolios and brings in CZ portfolios of new ebook orders.
Katherine O'Brien
supported this idea
·
-
50 votesKatherine O'Brien
supported this idea
·
-
156 votesKatherine O'Brien
supported this idea
·
-
224 votesKatherine O'Brien
supported this idea
·
-
179 votes
Thank you for this suggestion. we are checking the option to allow view history of requests same as we provide history of loans .
An error occurred while saving the comment Katherine O'Brien
commented
This should be a basic core function. Users expect it.
Katherine O'Brien
supported this idea
·
-
770 votes
Thanks for the examples - we will review them and discuss our options.
Best,
Tamar
Katherine O'Brien
supported this idea
·
-
34 votesKatherine O'Brien
supported this idea
·
-
36 votesKatherine O'Brien
supported this idea
·
-
107 votesKatherine O'Brien
supported this idea
·
-
65 votesKatherine O'Brien
supported this idea
·
-
14 votesKatherine O'Brien
supported this idea
·
Another +1 for selecting a CZ portfolio as part of the ebook purchase request workflow
This would allow us to use purchase requests. We decided not to use purchase requests because it creates a local portfolio when the request is approved. We use the EBC integration profile, which only checks for existing CZ portfolios, not local ones, and so we end up with duplicate portfolios in our collection. The CZ portfolios are preferable but it is too much work to de-dupe and the integration profile is more valuable to us than the purchase request feature.