...
...
...
...
...
...
...
...
...
...
Page Properties | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
This relates to the management of electronic resources for each CSU IZ using Model 1 (the local acquisition, licensing and e-resource management by the individual libraries. The openURL, proxy, and Discovery Interface Display Logic are driving forces behind display and access of electronic resources. It is essential to have recommendations and best practices that allow us to customize and maximize the system for the benefit of staff and library users.
...
- Alma's UResolver complies with 0.1 and 1.0 OpenURL (Sept 2016). The goal of the Alma Link Resolver is to provide patrons access to electronic resources that they have identified using OpenURL-compliant discovery tools such as Google Scholar, PubMed, Primo, etc.
Each CSU is responsible for contacting vendors or updating admin modules with the Alma link resolver and icon prior to going live. Note: This Ex Libris document explains the process of running a report in SFX to create a vendor list to send the new services page URL when moving from SFX to Alma.
- The CO will put in place temporary redirects from SFX to the Alma link resolver as campuses go live, so if you don't update all of your vendors by go-live, your users won't get stuck.
- The link resolver icon is the equivalent of the SFX openURL icon. Note: Here is the URL for the link resolver icon.
- The Link Resolver Base URL consists of the following parameters: http://<primo_fe_server_url:port>/openurl/<primo_institution_code>/<primo_services_page_view_code. Note: We do not use a "port" in our URL syntax. To get your base URL, go to the Primo Back Office and navigate to Primo Home>Ongoing Configuration Wizards>Institution Wizard. Copy and paste the Services Page URL. This same URL is also available in Alma by navigating to General Config menu > General Config > Other settings > Primo service page url
- The Alma resolver augmentation function is a component of the Alma Link Resolver process that enhances OpenURL metadata with DOI, OAI, and PubMed information. We recommend that you implement this, a one time only task. Look under General Configuration > Integration Profiles > Add Integration Profile. Note: Ask Jessica at CO for CrossRef details.
- Alma supports the ability to check the validity of the full-text URL before presenting it to the end user through the View It services menu. This functionality is only available for EBSCOhost – The EBSCO Link Resolver Plugin. In an NZ environment, the Link Resolver Plugin integration profile must be created for the network institution and for all the member institutions. We recommend that you agree to let Jessica implement this plugin for you.
- If you need to provide an openURL when submitting support cases, this Ex Libris document (How to Extract OpenURL) explains how to extract an openURL from Primo, Alma and Google Scholar.
...
Have you done the following tasks:
Set Up CRM Contacts
- Support cases can be opened from within Alma by clicking the Send to Ex Libris link found in the menu options below an electronic collection or electronic portfolio search result in the CZ or IZ. To take advantage of this feature, you should configure CRM contacts (Administration > General Configuration > Configuration Menu > General Configuration > CRM Contacts).
...
Typical troubleshooting issues include:
What to do with fulltext linking problems? Ex Libris has a document that provides you with specifics for How to report Full Text Linking and Availability Problems.
Have a clear e-resource metadata issue? You may want to report specific metadata issues to Ex Libris. For example, if you see an incorrect issn/isbn in the Alma Community Zone, you see titles that are missing (or are no longer available) in a full text collection, or the coverage for a title is incorrect, you can report these issues directly to Sales Support.
Set Up Google Scholar
- To publish electronic holdings to Google Scholar, you must configure the Publish electronic records to Google Scholar publishing profile and run it weekly to make sure that holdings information is accurate. The document "Publishing electronic Holdings to Google Scholar" provides further details for setting up this profile.
Set Up Institutional Electronic Holdings File
- The publishing profile allows you to configure the settings used to generate the electronic holdings file that Primo Central uses to update the status indicators. This process should be run weekly to make sure that the holdings information is accurate. The document Publishing Electronic Holdings to Primo Central provides further details about this profile.
Back Up Files
- Have a back up file or spreadsheet identifying vendor linking parameters (L/P) details. The L/P (found in the linking information tab from the Edit Service link for electronic material) should migrate correctly from SFX to Alma but if not, then you have the necessary information. You may decide to add this information to an internal note in the vendor record. The document SFX Target and Alma E-Collections Configuration Guide provides details for linking information (parser, parse params, etc) for vendors
- Spreadsheet of collections and vendors that should be in IZ
Under consideration: The Task Force would like to track IZ and NZ support cases. We would like to have some sort of case log (available on the wiki?). Possible workflows:
...
- Alma Resolver Augmentation
- What version of OpenURL protocol does Alma Support?
- How to confirm list of vendors to send services page URL when moving from SFX to Alma?
- What URL should be provided to vendors for the Alma ViewIt window link and the link resolver icon (AKA the Alma equivalent of the SFX OpenURL icon)?
- Base URL for the Services Page
- The Alma Link Resolver (video)
- Configuring the Link Resolver Plugin for checking EBSCOhost Full-Text URLs.
- Primo and Alma - The Alma Link Resolver
- Alma Link Resolver, OpenURL, GES, Citation Linker video
- How to Extract OpenURL from Primo, Alma, and other sources like Google Scholar
- Configuring the Primo Front End for Alma's Link Resolver
- Resolving Electronic Resources in the NZ
- Resolver Proxies
- Discovery Interface Display Logic
- Primo and Alma - Discovery interface display logic rules.pptx
- Discovery Interface Display Logic (Part 1)
- Discovery Interface Display Logic (Part 2)
- Discovery Interface Display Logic: Ask the Expert
- Managing Display Logic Rules When Working with a Network Zone
- Discovery Interface Display Logic for Related Records.pptx
- Defining Display Logic Rules at the Campus Level
- Patron Purchase Request and Display Logic Rule
- Modifying Display Labels
- Related records - Discovery Interface Display Logic for Related Records.pptx
- Primo and Alma - How to hide resource sharing request when there is a holding but no item
- General Electronic Services & Display Logic Rules documentation and video from Orbis Cascade Alliance
- Adding a General Electronic Service
- Why is a recently added GES not displaying?
- View It is limited for 25 Resources
- How to Report Linking Problems to Ex Libris
- Configuring CRM contacts
- Troubleshooting Toolkit (U of Minnesota paper presented at ELUNA 2016 conference)
- Publishing Electronic Holdings to Google Scholar
- Publishing Electronic Holdings to Primo Central
- SFX Target and Alma E-Collections Configuration Guide
Action log
Section | Point Person | Expected Completion Date | Last action taken | Next action required |
---|---|---|---|---|
Articulate the need for the policy (background) | Christine Holmes |
| 8/23/2016- ERM Task Force discussed the ERM policy and procedures outline and assign a policy to a task force member. Jessica assigned the policy and procedures for shared resources in Alma. | Draft for Shared Resources due September 30th. Send draft to Tech Service Working Group Leads |
Rough Draft for Shared Resource policies and procedures | Christine Holmes |
| Rough draft | |
ERM Task Force meet to discuss rough draft of policies and see if there is any feedback from the Working Group Leads |
| ERM Task Force met to discuss policies and procedures | ||
Send rough drafts of policies to Tech Services-discuss policies in Open Forum. Ask for feedback from working group. |
| Link to Drafts were sent out to the Tech Services Working Group | ERM Task Force will go over the feedback received from the ULMS IMP Team and the Tech Services Working Group. Meet with other TS Working Groups to discuss overlap of policies and procedures. ERM Task Force will meet | |
Final "live" Draft for Shared Resources is due |
| Final drafts for policies is December 9th. All policies for all task forces are due this date. | ||
ERM Task Force meet to discuss final drafts of polices and see if any feedback from the Working Group Leads |
|
Tasks to be completed
- Type your task here, using "@" to assign to a user and "//" to select a due date