TABLE OF CONTENTS

Basic Setup

A local electronic collection that contains electronic portfolios attached to the print MARC bibliographic records that correspond to HathiTrust overlap holdings.

Reasoning:

  • The matchpoint between UC and HathiTrust is the OCLC number for the print bibliographic records. 

  • ETAS is a temporary measure, so electronic bibliographic records are not feasible for matching and maintaining database integrity

Scenario A - One UC (or multiple UCs) has activated ETAS

Option 1: Ten Local Collections in the NZ - one for each campus

  • What:

    • CDL creates a local electronic collection (inactive) for each UC campus that contains an electronic portfolio for each print OCLC number present in HathiTrust that is held by that campus

    • CDL activates the e-collection for the campus and adds the campus as “available for” for the duration of ETAS activation

  • How:

Option 2: One Local Collection in each IZ

  • What:

    • Each campus creates a local electronic collection (inactive) for each UC campus that contains an electronic portfolio for each print OCLC number present in HathiTrust

    • Campus activates the e-collection for the duration of ETAS activation

  • How:

Option 3: One Local Collection in the NZ - all UC holdings

  • What:

    • This option assumes that if one UC has activated ETAS, it then has access to the holdings of all UCs in HathiTrust

    • Same as Scenario B - Option 1 (see below)

    • CDL activates the e-collection for the campus and adds the campus as “available for” for the duration of ETAS activation

  • How:

    • See Scenario B - Option 1 (see below)

Scenario B - All UCs have activated ETAS

Option 1: One Local Collection in the NZ - all UC holdings

  • What:

    • CDL creates a local electronic collection (inactive) that contains an electronic portfolio for each print OCLC number present in HathiTrust that exists in the NZ

    • CDL activates the e-collection and adds all campuses as “available for” for the duration of ETAS activation

  • How:

Mechanism for loading

OAI-PMH

This option creates an automated load of HathiTrust records and creates an electronic portfolio (in the electronic collection of choice) for any match on OCLC# and filters out any open access records using an indication rule. This method can be set to run daily/weekly/monthly and each subsequent run of the import profile will only process records with a date stamp after the last harvest. 

Create a Repository Import Profile using Import Protocol: OAI-PMH for set “hathitrust”

  • Originating System - other

  • Import Protocol - OAI

  • Source format - OAI MARC21 Bibliographic

  • Status - Active

  • OAI Base URL: https://oai.hathitrust.org/

  • Click Connect and Edit

  • Set - All works in HathiTrust

  • Leave default start date/date stamp


Normalization & Validation

    Filter out the data using [select Indication Rule that ignores 856 URLs that are Open Access (based on Attribute in 856$r)]


Indication Rule:

rule "856 has r of Open Access"

when

(not exists "856.r.*ic*" OR not exists "856.r.*op*" OR not exists "856.r.*orph*" OR not exists "856.r.*und*" OR not exists "856.r.*icus*")

then

set indication."true"

end


Match Profile

Match by Serial / Non Serial - No

Match Method - Unique OCLC Identifier Match Method

Handling - Automatic

Upon match - Do Not Import

No Match - Upon no match - Do Not Import


Set Management tags - leave default (don’t publish)


Inventory Information [Creates portfolio in local e-coll for each 856 (sometimes multiple) for any OCLC# that already exists in Alma.]


Select Electronic

Portfolio Type - Part of an electronic collection - select local electronic collection

Multiple portfolios

Extract portfolio information from field 856

Extract access URL from field Subfield u

OAI url: https://oai.hathitrust.org/?verb=ListRecords&metadataPrefix=marc21&set=hathitrust

Sets: https://oai.hathitrust.org/?verb=ListSets

https://www.hathitrust.org/member-libraries/resources-for-librarians/data-resources/oai-feed/

Hathifile

This method involves requesting an overlap file from HathiTrust for each campus that contains the OCLC# and HT bibkey for each title held by that campus, filtered to only those titles in ETAS (“deny”). This file is then loaded into the electronic collection of choice using either an Import Profile (could be automated to pick up the file via FTP) or via the Portfolio Loader (always manual). The load would create an electronic portfolio attached to an existing print bibliographic record by matching on the OCLC#

Resources:

https://www.hathitrust.org/member-libraries/resources-for-librarians/data-resources/hathifiles/

https://www.hathitrust.org/member-libraries/resources-for-librarians/data-resources/hathifiles/hathifiles-description/

Schedule for Maintenance

OAI-PMH - monthly, after first load it only processes updates

Hathifile - recommend minimally yearly. Would depend on interfacing with HathiTrust.

CDL responsibilities

  • Create electronic collection(s) depending on options

  • Configure available for groups in the event of ETAS activation

    • Includes creating a custom parser, with parser parameters for each campus so that users are prompted to log in automatically for items

Local campus responsibilities

  • Campus must update holdings with HathiTrust for up to date activation in the event of ETAS

  • Create electronic collection for local holdings, depending on options

  • Configure URLs so that users are prompted to log in automatically for items

URL authentication setup

HathiTrust Documentation: https://www.hathitrust.org/member-libraries/resources-for-librarians/improve-discovery/auto-login/

Options in Alma:

NZ - Create custom Parser in the electronic collection and add parser parameters in Group Settings 

Example: assumes bkey=url with record id ( IZ screenshot provided - NZ Parser parameters are in different location)

IZ - Create custom Parser in the electronic collection OR append authentication string to URLs at time of import and creation of the electronic portfolio