[Wactclc-alma] Vendor Interfaces and Primo links

[Daniel Moore]

These are awesome notes Kirsti, many thanks for sharing them!

-Dan

On Tue, Nov 5, 2019 at 1:26 PM Thomas, Kirsti <
Kirsti.Thomas at seattlecolleges.edu> wrote:

> When Primo displays an electronic title in the Full Record View, it
> follows some rules about what to display as the text for the URL link:
>
>
>
>    1. If the title is part of an electronic collection, Primo displays
>    the public name of the electronic collection
>    2. If the title is *not* part of an electronic collection, Primo
>    displays the name of whatever Vendor Interface is associated with the
>    portfolio record
>    3. If the title is *not* part of an electronic collection *and*
>    there’s *no* Vendor Interface associated with the portfolio record,
>    Primo displays the phrase: v*iew full text*
>
>
>
> Here’s an example of Situation (3):
>
>
>
> We have a bib record for a streaming video in Alma.  For whatever reason,
> one of the two existing portfolio records isn’t associated with any
> electronic collection and doesn’t have an Interface Name associated with it
> either.
>
>
>
>
>
>
>
> Here's a side-by-side comparison of the portfolios in the Title Display
> screen and the Portfolio List screen:
>
> The portfolio record that’s *not* associated with an electronic collection
> is a Kanopy video that belongs to South Seattle.  If you look for this
> streaming video in South Seattle’s Primo, you get a hypertext link that
> says *view full text*. That’s the default phrase that appears when
> there’s no electronic collection and no Interface Name associated with the
> portfolio record.
>
>
>
> Here's how that looks in Primo:
>
>
>
>
>
> This default phrase isn’t very helpful, especially if you’ve got a lot of
> portfolio records that were created from 856 fields in your bib records as
> part of the P2E process during migration.  Like this:
>
>
>
>
>
>
>
> It goes on like that for another 59 lines!
>
>
>
>
>
> You can manually create an Interface Name to show up as the hypertext link
> for your standalone e-titles.
>
>
>
> For example, we have a standalone subscription to Puget Sound Business
> Journal online that we buy directly from Puget Sound Business Journal.  In
> our Alma vendor record, I created a very simple Interface record.  All it
> has is an Interface Name, a Description, and a Note:
>
>
>
> Interface Name: *Puget Sound Business Journal Portal*
>
> Interface Description: *Customized portal created by Bizjournals.com to
> allow remote access for end users*
>
> Note: *Customized portal for Seattle Colleges (50 concurrent users)*
>
> Status: *Active*
>
>
>
>
>
>
>
>
>
> Then, in the portfolio record for *Puget Sound Business Journal*, under
> the *General* tab, I selected * Puget Sound Business Journal Portal* as
> the Interface Name.
>
>
>
>
>
>
>
>
>
>
>
> Here’s how this looks in Primo:
>
>
>
>
>
>
>
> The *Available from…* statement comes from the* Coverage* tab of the
> portfolio record. I manually entered the coverage information when I
> created the portfolio record in Alma.
>
>
>
>
>
> We’ve got a few OCLC bib records in our system that have links to public
> domain ebooks or Open Access e-journals.  Even though we don’t buy these
> titles from anyone, I set up a special vendor record in Alma just so I
> could create Interface records so that *something* other than * view full
> text *would show up in Primo.
>
>
>
> Here are a few screenshots of the Vendor Details:
>
>
>
>
>
>
>
>
>
>
>
> Here’s an example from Alma of a record that uses these interfaces:
>
>
>
>
>
>
>
>
>
>
>
>
>
> Here’s the same record in Primo:
>
>
>
>
>
>
>
> I only worked this out last week, so we have a lot of standalone e-titles
> that still have to be cleaned up.
>
>
>
> It will be ok!
>
>
>
> Kirsti S. Thomas
>
> Library Technical Service Manager
>
> Seattle Colleges
>
> kirsti.thomas at seattlecolleges.edu
>
>
>


-- 
Regards,

Dan Moore
Systems and Collections Librarian
Edmonds Community College Library
dan.moore at edcc.edu / daniel.moore at email.edcc.edu
(425) 640-1526
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 19953 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0026.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 21844 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0027.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 16448 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0028.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 21624 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0029.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 9046 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0030.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 23308 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0031.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 29207 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0032.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 13639 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0033.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.jpg
Type: image/jpeg
Size: 30767 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0034.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 27135 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0035.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.jpg
Type: image/jpeg
Size: 10847 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0036.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.jpg
Type: image/jpeg
Size: 23314 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0037.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.jpg
Type: image/jpeg
Size: 18268 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191105/2e09b7c7/attachment-0038.jpg>