Yes that helps - we call it "suppressed".

Your post inspired me to research changing from our "old-style" III link resolver to OCLC KB.  So far, fun with pubget...

Cindy

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Jenn Riley
Sent: Monday, July 14, 2014 3:05 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] non-kb based openurl from ILS

Oops, sorry for being oblique! Right now we have records for ebooks and ejournals in Aleph completely hidden from users ('shadowed' as we call it here), so they're not retrieved in searches. We did this because we knew the links in them werent going to work once we shut off SFX. If we had OpenURL working in Aleph going through the OCLC KB we'd unshadow these records and make them available to users again.

This all assumes the records can get into Aleph in the first place which is a separate issue, for which our approach and painful decisions are too complicated to get into here. :-)

Does that help?

Jenn




On 2014-07-14 2:50 PM, "Harper, Cynthia" <[log in to unmask]> wrote:

>Sorry if this is too basic, but I'm not sure what you mean by "shadowing"
>records in Aleph - does that mean you'd just have brief records in 
>Aleph which are loaded from an OCLC kb export? But that sounds like 
>your second option, adding a linkout...  I just don't know the "shadowing"
>terminology.
>
>Cindy Harper
>[log in to unmask]
>
>-----Original Message-----
>From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of 
>Jenn Riley
>Sent: Monday, July 14, 2014 1:54 PM
>To: [log in to unmask]
>Subject: [CODE4LIB] non-kb based openurl from ILS
>
>Hi everyone,
>
>We use Aleph for our back end ILS and WorldCat Local as our discovery 
>layer. We'd previously maintained both the OCLC KB and the SFX KB, but 
>under the principle of not maintaining data in two places we've retired 
>SFX. We started out just shadowing records for e-books and e-journals 
>in Aleph, but are now wondering what it would look like to continue to 
>have those records available in Aleph and find a way to have them link out.
>The URLs in these (currently shadowed) records go to SFX, and trying to 
>redirect or batch update those looks like a no-go based on the 
>difficulty of matching up the SFX and OCLC KB data. So we'd have to 
>hide those URLs and find another way to get the user from the Aleph 
>search result to the electronic version of that item.
>
>In this scenario we're considering a 'find full text' button in Aleph 
>that sends an OpenURL request through to the OCLC link resolver. It's 
>basically old-skool OpenURL as before KBs existed. Or how OpenURL works 
>from an A&I database.
>
>We think it's possible to do this in Aleph piggybacking on how the SFX 
>requests were constructed and sent, but would like to talk with others 
>who have done this or something similar through Aleph, if there are any.
>Anyone have any experience with this? Or words of advice?
>
>Jenn
>
>-----------------------------------
>Jenn Riley
>Associate Dean, Digital Initiatives | Vice Doyenne, Initiatives 
>numériques
>
>McGill University Library | Bibliothèque Université McGill
>3459 McTavish Street | 3459, rue McTavish Montreal, QC, Canada H3A 0C9 
>| Montréal (QC) Canada  H3A 0C9
>
>(514) 398-3642
>[log in to unmask]