...
- Ebooks and electronic journals are ordered just like their print counterparts (See acq training), but don't require any item or shelf prep work. Individual title purchases may start with patron requests or the work of selectors. New requests are tracked in the Eresources group using ERIN, a workflow managing tool.
- Electronic content lives at the vendor/publisher site, and we essentially lease access to that content via licenses.
- Generally speaking we purchase Harvard-wide electronic access - authenticated use is via ip address. Off campus access goes through the proxy server, for which users must use Harvard credentials (Harvard Key). A few resources require users to create an additional user account.
- There are many different models for ebook publishing: ebooks take many forms. Integrating resource, pdf or html versions of the print book, downloadable, etc...
- Once purchased and available on the publisher site, books and journals must be activated in Alma for users to be able to find them. This happens via the CZ.
- CZ records are activated in Alma, which creates an instance of the same record in our IZ. Any updates to the CZ record from Ex Libris will be reflected in our IZ records automatically.
- Records from the CZ can be enhanced with additional subject headings, etc. in the metadata editor.
- We get standardized COUNTER reports for journal and book usage via Alma's SUSHI service. These reports inform decisions about whether to keep or cancel low use journals, or buy additional content for heavily used titles.
- Troubleshooting Problems: occasionally we lose access to eresources, sometimes because the publisher detects suspicious activity from a Harvard account, but problems can occur for any number of technical reasons. Troubleshooting electronic resources is a daily activity and can involve staff from LTS and HUIT. Access problems are usually tracked using Footprints tickets.
- Journal cancellations, end of life for ebooks: When libraries cancel journal subscriptions, we often retain access to the years that our subscription was active (not always!). In these cases, we update the coverage statement in Alma to reflect our entitlements.
Notes/Outline:
- Overview: Mapping SFX, Verde, Aleph work to Alma
Aleph workflow:
Requests and overall workflow tracked via ERIN
Descriptive and Acquisitions work
Bib record: Bring in via OCLC or create, further cataloging work passed along to catalogers when needed
add holdings
add order(s)
process invoices
Linking:
When resource live at publisher/provider site, create a urn (ERNIE), put in the Aleph holdings record
(If new resource, will need to be proxied)
And/or
SFX: activate appropriate targets, services, portfolios; configure updates
update coverage dates and linking information when needed
Verde: Record licenses, admin info for publisher sites/platforms, cost share info
Usage
UStat – SUSHI and manually downloaded COUNTER reports
Related automated tasks in metadata management
EDI
Order loader
Batch loading/updating of ebook packages
Others:
Activation in Metalib, Primo to make resources visible in library portal
Maintenance and troubleshooting
Broken links, access or authentication problems
Breaches
Other technical problems
Alma workflow:
Alma integrates work previously spread across multiple interfaces, products that didn’t talk to each other
Bibs brought in from external source (e.g., OCLC) or CZ, descriptive work/cataloging in metadata editor
SFX-like tasks such as activation and updating coverage occurs in Community Zone (CZ)
services
collections
portfolios
Local collections & portfolios may be created when necessary and linked to CZ at a later date
License & Acq work - ordering & invoicing, integration with ERIN requests
The CZ and creating local collections & portfolios when necessary
License & Acq work - ordering & invoicing, integration with ERIN requests
...
- order loader
- EDI
- 'manual' & ad hoc ordering
...
- testing access/activation at vendor site
- single title ebook/journal
- batch of ebooks
- ebook package
- other examples?
- default proxy, other proxy options (e.g., Law)
- services
- running jobs (?)
...
- finding the 'right' vendor record; vendor types in Alma(?)
- admin logins - IP ranges, etc
- usage reports - SUSHI, ad hoc
...
Basic Topics
Overview of pre-Alma workflows: Aleph, SFX, Verde, ERNIE (screenshots), ERIN
Intro to CZ – searching, interpreting records, levels (service, collection, portfolio)
Activating single Ebooks (one time orders)
Activating Journals (continuous orders)
Linking to descriptive record
Linking POLs
What if it's not in the CZ?
What displays in Hollis+ ?
Advanced Topics
Cleaning up migrated P to E records (example?)
Proxy issues: table of proxy settings & their effects at different levels (screenshot)
Updating multiple portfolios at once - loading sets of ebooks into a collection
Local collections and portfolios - e.g., linking a local portfolio to a collection
Moving from platforms of individually cataloged ebooks with static URNs to CZ Collections/Portfolios and parse parameters
Platform example: ClinicalKey? PsychiatryOnline?
Best practices? Getting all the pieces connected