Alma Link Resolver Workflow
The following flow chart depicts the high level logical steps for the Alma Link Resolver from the point of OpenURL requests to the delivery of services.
Receive Open URL
Alma Link Resolver supports ANSI/NISO Z39.88-2004 (R2010) the OpenURL Framework for Context-Sensitive Services. For more information, see ANSI/NISO publications.
Build Context Object
Once the OpenURL is received, Alma Link Resolver does the following:
- Extracts the OpenURL metadata by parsing the metadata element available in the OpenURL
- Additional metadata elements are augmented from additional sources based on ID, for example: Pubmed, DOI.
Note: The Link Resolver finds matching services based on the metadata from additional sources based on ID. Wrong metadata, such as on a DOI, can impact the availability of services from these sources, since if the metadata is incorrect, then incorrect matching services will be found.
For information on augmentation, see Alma Resolver Augmentation.
- All metadata from the OpenURL and from augmentation processes are saved in a Context Object.
Match Bibliographic Record/s
Based on the metadata elements stored in the Context Object, Alma's Link Resolver attempts to match all bibliographic records in the catalog, based on the following logic:
- Identifiers EISSN,ISSN, EISBN, ISBN, LCCN, CODEN, OCLC unique number. When a Bibliographic record is found, the search stops.
Note: Alma Link Resolver supports incoming CDI OpenURLs with multiple ISBNs and EISBNs. Alma will use these ISBNs and EISBNs to match bibliographic records and will return all relevant electronic services.
- The identifiers are prioritized according to the genre (article/journal/issue genres give a higher priority to EISSN/ISSN; other genres give a higher priority to EISBN/ISBN). When genre is not present, priority is given to EISBN/ISBN over EISSN/ISSN. See Using Standard Identifiers for more information.
- If no match is found on the identifiers, a search is performed by "title" and "author" unless the genre is Journal, Article, or Issue (in which case no further search is performed).
- If a match is found, the search stops.
- If there was no search by identifier (no identifier as part of the Context Object), a search is performed by "title" only. When searching by title only, the genre plays a role in determining the material type to be retrieved. If the genre is Book, BookItem, Report, or Document, the material type to be retrieved is monograph. If the genre is Issue, Journal or Article, the material type to be retrieved is serial.
The functionality to combine the EISSN and ISSN searches is controlled by the parameter: temp_enable_identifier_combined_search which is set to true by default. This functionality opens URLs generated for items that have EISSN and ISSN and matches them on EISSN.
When set to false, the combined search functionality is turned OFF.
This parameter is for use by Ex Libris. To edit the settings, contact Ex Libris support.
When the Link Resolver searches for an ISSN, it performs an All Titles repository search using the ISSN index, searching for all titles that are not suppressed AND where ISSN equals the value sent in EISSN or ISSN of the OpenURL, according to the rules described on this page. For the subfields of the ISSN field that are considered by the Link Resolver, see the Mapping of MARC21 fields table below.
- The Alma Link Resolver searches for a match by EISSN first. If a match by EISSN is found, the search is stopped and an additional search for ISSN is not performed.
- Important! If a match by EISSN is found, but it is filtered out from View It (for example, the dates are not covered) and the search stops as described above, an additional search for ISSN is not performed.
|Fields that are mapped to Author||Fields that are mapped to Title||Fields that are mapped to ISBN/EISBN||Fields that are mapped to ISSN/EISSN|
|100 $$ a-d,j,q,u
110 $$ a-e,g,n,u
111 $$ a,c-e,g,n,q,u
700 $$ a-d,g,j,q,u
880 $$ a-d,g,j,q,u
710 $$ a-e,g,i,n,u
880 $$ a-e,g,i,n,u
711 $$ a,c-e,g,i,j,n,q,u
|245 $$ a,b,k,n,p
and their 880 fields and subfields
|700 all subfields excluding numeric subfields
701 all subfields excluding numeric subfields
710 all subfields excluding numeric subfields
711 all subfields excluding numeric subfields
|200 $$a,e,h,I||010 $a||011 $$a,f|
For internal reference: Author and Title are respectively creator_contributor and extended_title from the search section of the Operational Record.
Build Context Service
Alma's Link Resolver will calculate all relevant services for the matched Bibliographic record(s). Service is considered relevant based on Availability:
- Bibliographic record is not suppressed
- Portfolio is active
- For Journals: coverage, embargo conditions are passed
- Electronic service is active
Alma's Link Resolver will add additional services in the following cases:
- Services for Related Bibliographic Records (configurable)
- For an institution that manages distributed electronic services, Alma's Link Resolver will calculate availability based on "Available For" group setting.
For more information, see Link Resolver for Institutions Using Distributed Electronic Resources.
- In the context of consortia that manages electronic services centrally in the Network Zone:
- Alma's Link Resolver will consult the Network Zone to check if there are any services that are available for the Context Object for the institution based on "Available For" group settings defined in the Network Zone. For more information, see Link Resolver for Consortia.
Once the Context Service is built the relevant services will be presented to the patrons.
By default all services will be sorted alphabetically by the electronic collection name.
The institution can influence the appearance of the services in the following ways:
- Define sort order
- Service Labels
- Display Logic Rules
- Configuring Direct Linking
- Displaying License Information
- Displaying Access Model
For more information, see Link Resolver Library Preferences
Once a user selects a service (or is directed to one), Alma's Link Resolver will generate the final URL using a dedicated linking program (Target Parser) that implements the service provider linking syntax.
For further information, see Access to Services