Elizabeth York
My feedback
27 results found
-
6 votes
Hello,
We will reach out to East View, and ask for the metadata for this collection.
Thanks,
Tamar Ganor
Content Product Manager
An error occurred while saving the comment Elizabeth York
shared this idea
·
-
Add an option to disable direct linking for newspapers
-
Direct%20Linking%20configuration%20screen%20with%20new%20newspapers%20option.png 36 KB -
Direct%20Linking%20configuration%20screen%20with%20journal%20option%20changed%20to%20journals%20and%20newspapers.png 33 KB -
Primo%20newspaper%20result%20showing%20different%20coverage%20ranges%20for%20different%20portfolios(1).png 64 KB
3 votesElizabeth York
shared this idea
·
-
-
126 votesElizabeth York
supported this idea
·
-
131 votes
Hello,
We are working with East View to streamline their planned platform change.
You can also track the updates in the Known Issues platform:
https://supportcenter.clarivate.com/s/known-issues/knowledge-detail?language=en_US&recordId=kA2QO00000108Ej0AI
I will post here once the migration is completed.
Kind regards,
Tamar Ganor
Content Product Manager
Elizabeth York
supported this idea
·
-
46 votesElizabeth York
supported this idea
·
-
49 votes
An error occurred while saving the comment Elizabeth York
commented
I strongly support this idea. The current behavior (restored portfolio having a people icon and looking like a CZ portfolio) is unintuitive and misleading, as the people icon makes it look like a CZ-linked portfolio, but the portfolio is really local. Correcting this by making the portfolio display a house icon would make it easier to maintain restored local portfolios in Alma. It might also increase libraries' confidence in and usage of the Manage Deleted Repository Tool.
Elizabeth York
supported this idea
·
-
18 votesElizabeth York
supported this idea
·
An error occurred while saving the comment Elizabeth York
commented
Rutgers University Libraries supports this idea, as we have publications that have moved to Inlibra too.
-
5 votes
Hello,
We will reach out to Alexander Street, and ask for the metadata for this collection.
Thanks,
Tamar Ganor
Content Product Manager
An error occurred while saving the comment Elizabeth York
commented
Hi Tamar,
I was wondering, have there been any updates on this collection? Docuseek said Alexander Street told them they had "created a discovery file with Ex Libris," so we're hoping this collection will be available soon to activate in the CZ!
Elizabeth
An error occurred while saving the comment Elizabeth York
commented
We heard from Docuseek that Alexander Street has "created a discovery file with Ex Libris." We'd like to double-check with Ex Libris to see, has Alexander Street provided this 4th edition file to Ex Libris, and what is its status in the process of being added to the CZ? Thanks for helping us understand how this is progressing!
Elizabeth York
shared this idea
·
-
62 votesElizabeth York
shared this idea
·
-
32 votes
An error occurred while saving the comment Elizabeth York
commented
I want to strongly suggest that if this were to be implemented, this would need to be an option where libraries could select to either create portfolios before or after the normalization process.
There is a very good reason for portfolios to be created before the normalization process--when we import bibliographic records for electronic resources, we want their portfolio links to be created or updated, but we do not want to create 856 fields in our bib records. So, we have a norm rule to remove 856 fields from bib records, and this rule goes into effect nicely after portfolio creation/update. In Alma, access to e-resources is provided via portfolio links, not 856 fields. The portfolio link is what should be maintained and updated to provide consistent access, and Alma gives us great tools to manage our portfolios in batches in our electronic collections. We don't want to be creating 856 fields on our bib records, which would unnecessarily duplicate our portfolio links and be hard to maintain--we want to maintain our links to e-resources in our portfolios alone!
So, I ask Ex Libris, if you implement this, please do not make this a global change so that norm rules are applied before portfolio creation for all customers. If you do implement this, please allow customers to choose whether norm rules should be applied before or after portfolio creation.
-
42 votesElizabeth York
supported this idea
·
An error occurred while saving the comment Elizabeth York
commented
I voted for this request, but I'd like to note that many libraries do not use Cloud Apps due to security concerns or technical limitations of the apps, so as part of implementing this idea, I suggest the option to update electronic-collection level linking parameters should also be built into the Change Electronic Collection Information job in Alma.
For context, I'd like to share the link to the November 2024 release notes that made it so customer linking parameters are configured at the electronic collection level for CDI database collections: Possibility to Define Linking Parser Parameters for Database Collections in Collection Level to be Used by CDI Direct Linking: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411
-
108 votesElizabeth York
supported this idea
·
An error occurred while saving the comment Elizabeth York
commented
In response to the Anonymous comment on what should be done if multiple licenses apply to a book (i.e. a book is both owned and in an EBA)--following the precedent of the ProQuest Ebook Central autoholdings integration, there should be a series of checkboxes in the portfolio, one for each access model (owned, subscribed, in DDA, etc). If a book is in multiple categories, multiple checkboxes should be checked.
-
9 votesElizabeth York
shared this idea
·
-
37 votesElizabeth York
shared this idea
·
-
196 votesElizabeth York
supported this idea
·
An error occurred while saving the comment Elizabeth York
commented
I support this idea, as it would help address the confusing cases where a resource is available OA on one platform, but it is behind a paywall on another platform. The portfolio-level indication would accurately show whether that specific portfolio is available openly or not.
This idea would also help address cases where some (but not all) of a journal coverage range is OA. The bibliographic record OA indicator is not granular enough, as it does not show which parts of the journal are OA. A portfolio-level indicator could show whether that specific portfolio and its coverage ranges are OA or not.
-
66 votes
An error occurred while saving the comment Elizabeth York
commented
This is a good idea! Here is another use case: sometimes, a provider updates their parser parameters but fails to update their service parser, so all the parsers break. As a temporary fix, we need to locally override the service parser parameters to work with the new portfolio parser parameters. At present, we have to manually edit every affected service's parser parameters. With this job, we could manually override all the affected collections' service parser parameters in bulk.
Elizabeth York
supported this idea
·
-
33 votes
Hello,
We are working with the provider to obtain MARC records to enrich JoVE collections.
Kind regards,
Tamar
Elizabeth York
supported this idea
·
-
63 votesElizabeth York
supported this idea
·
Elizabeth York
shared this idea
·
-
7 votesElizabeth York
shared this idea
·
-
40 votes
An error occurred while saving the comment Elizabeth York
commented
I'd like to note that it is possible to make many linking parser parameters changes for multiple collections at the same time using the Change Electronic Collection Information Job, including setting the parser and parser parameters. That being said, the example given in the Idea Exchange Request, swapping out the ProQuest ClientID is not one of them (probably because the job only includes fields common to all collections, and different services require different IDs). I'm not sure if Ex Libris could make it possible to batch edit the ID fields that are not common to all collections/services. If they were to implement such a feature, I would hope they would add it to the Change Electronic Collection Information Job too.
.png){kind=link}
I just wanted to add, I heard from East View Support today, "East View's Online team has provided product information, title lists, and URLs to link resolvers (Ex Libris, OCLC, and EBSCO). This product will be added to their knowledgebase platforms on their internal schedules." We'll look forward to seeing this collection in the CZ soon!