[Wactclc-alma] Follow-up from Monday's meeting at Bellevue College

[Guidry, Wade]

Yes, this is pretty much the answer.

Activating in Alma

Activating collections (or individual portfolios) in Alma indicates that you have access to the collection and/or portfolio.

Activating collections/portfolios in Alma also allows the collections/portfolios to be searched *at the title level* in Primo.

Activating in Primo

Activating collections in the Primo PCI allows those collections to also  be full-text searchable in Primo (where article level metadata exists), and will provide article level search results for those journal titles you own. And also for journal titles you don’t own or have access to, if the user selects “expand my search results”.

Ebsco

Because Ebsco does not share its article-level metadata with Ex Libris, there is no way to activate Ebco collections directly within the PCI. So, two options exist:

Using the Ebsco API as a search scope in Primo

This option is problematic, in that it results in a somewhat “uncontrolled” search, where search terms are sent from Primo to Ebsco, and Ebsco sends back search results, that are not really well-curated or formatted for use in Primo.

The Ebsco API is, however, one workaround you can use with Primo. I don’t recommend using it, as it doesn’t provide a strong user experience. But SPSCC, for example, is using the Ebsco API, and is happy with it so far.

Using “alternative coverage” in the PCI for Ebsco

Another way to provide article level search results in Primo is to use the “alternative coverage” technique. In this method, you activate “ebsco equivalent” collections in the PCI. That is, collections that closely mimic, alone or in combination, the holdings of an Ebsco collection.

When those equivalent collections are activated, and users search Primo, Primo matches the article level results from the equivalent collections in the PCI with your actual Ebsco holdings as reflected in Alma, and directs users to the associated content in Ebsco.

This method is not without issues. Particularly where the range of holdings in the equivalent collection may not match what is actually available in Ebsco.

But, with alternative coverage, at least all data being searched is curated and formatted for Primo use. And is also local to Primo and Ex Libris.

The ExL document describing the appropriate alternate coverages for various Ebsco collections, and also a bit of overview about using alternate coverages, can be found at:

https://knowledge.exlibrisgroup.com/@api/deki/files/45896/Primo_Central_Index_Collection_List_%E2%80%93_Alternative_Coverage_%5BSept_2016%5D.pdf



From: Wactclc-alma [mailto:wactclc-alma-bounces at lists.ctc.edu] On Behalf Of Nicole Longpre
Sent: Wednesday, November 9, 2016 1:25 PM
To: WACTCLC Alma Discussion <wactclc-alma at lists.ctc.edu>
Subject: Re: [Wactclc-alma] Follow-up from Monday's meeting at Bellevue College

Hi Dale,

Obviously I am not Wade, but I had asked a similar question to your question 1 to Justine just before go live and here is her response:
If a record (portfolio) exists in the CZ, can we simply activate it in Alma without activating the relevant collection in PCI?



Yes, you can.



The 2 primary reasons to activate in the PCI are:



1. You want to enable full-text article searching in Primo



If journal package is only activated in Alma, then only the bib record metadata is searchable in Primo.



But, if you activate in the PCI as well, any article full-text info that Ex Libris has available in the PCI for those journals will be searchable by patrons as well.



This is particularly powerful for journal packages, and is a great patron service. Ebook content in Primo won't be full-text searchable, even if you enable those collections in the PCI.



(there's also a subtlety here about searching Primo with the "expand my search" feature, which some of you may have enabled)



2. You want a collection searchable in Primo (via 'expand my results), but don't want to activate or manage the collection in Alma, either because you don't own it, or some other reason.


From: Wactclc-alma [mailto:wactclc-alma-bounces at lists.ctc.edu] On Behalf Of Dale Burke
Sent: Wednesday, November 09, 2016 9:24 AM
To: WACTCLC Alma Discussion <wactclc-alma at lists.ctc.edu<mailto:wactclc-alma at lists.ctc.edu>>
Subject: [Wactclc-alma] Follow-up from Monday's meeting at Bellevue College

Hello all,

First, I want to say that the meeting was very beneficial. It was great to meet Wade in person, and I was impressed with some of Wade's explanations of a couple of topics.

I am hoping that Wade could reiterate a couple of the comments he made during our meeting at Bellevue.  This would be helpful for me and for anyone who was not able to attend the meeting.

Could you re-explain the following in easy to understand terms:

1)  Activating an electronic collection in Alma vs Primo PCI activation.  Subtle differences that we need to understand more fully.  Is there a "best practice" for making sure your coverage is what you expect.

2)  How to get the best coverage for EBSCO articles in Primo.  There was a discussion about EBSCO at the article level vs. some other means.  There was also talk about how to use alternative coverage for EBSCO articles.  I would like to see this explained in more detail.

I would also encourage others who attended to post any follow-up "Aha" moments or questions from the meeting.

Dale Burke
Technical Services Librarian
[https://lh4.googleusercontent.com/5X_QEwm_g--tzfcAatV2-GBhPyBlyI9MgjAJucyeAYGdBFiZAKd2MCXvR4GlG8mYdi6czhygyClHcQAO0SMNFeoQj1v1otf4ZhHAuO8Hy5XMBGCD7vhvTHFrzt34IdtmHnA8MwPp]
20000 68th Ave. W
Lynnwood, WA  98036
425-640-1526
dburke at email.edcc.edu<mailto:dburke at email.edcc.edu>
[https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20161109/aeb646f3/attachment.html>