Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Access to Services

    Translatable

    Linking Program (Target Parser)

    Refer to the following document (SFX Target and Alma E-Collection Configuration Guide) that provides specific linking parameters which are required to enable full text linking.

    Display Condition Rules

    Translatable

    The Alma Link Resolver (and Primo View It) supports rules that determine the conditions in which an electronic collection is presented to an end user. Display condition rules are defined in the Community Zone knowledge base and include, for example, a requirement that the incoming OpenURL includes article-level metadata elements. Condition rules are available for newspaper electronic collections and electronic collections like CCC Get It Now.

    After you activate or edit the electronic collection, you can view the display condition information and rules. Note that display condition rules cannot be edited or locally created. To view this information, select the Linking tab on the Electronic Service Editor page; and next to Availability rules, select the Service display condition rules link (for newspaper electronic collections) or the Service filter condition rules link (for the CCC Get It Now electronic collection).

    Service_Display_Condition_Rules_Link_02.png

    Service Display Condition Rules Link

    Electronic service editor - Service filter condition rules.png

    Service Filter Condition Rules Link

    This opens the Service Display Condition Rules page (for newspaper electronic collections) or the Service Filter Condition Rules page (for the CCC Get It Now electronic collection).

    Service display condition rule.png

    Service Display Condition Rules for Newspaper Electronic Collections

    Service filter condition rules.png

    Service Filter Condition Rules for CCC Get It Now Electronic Collections

    By default, there is OR logic applied between the rules identified in the Rule Name column. This means that when any of the rules in these examples are met, the newspaper electronic collection or the CCC Get It Now electronic collection appear when using the Alma Link Resolver or Primo View It. If none of the rules are met the newspaper electronic collection or the CCC Get It Now electronic collection does not appear in Alma Link Resolver or Primo View It.

    To view the details of each rule, select the rule number link in the Rule Name column. See below for examples of these rules.

    Rule_Details_Example_for_a_Newspaper_Electronic_Collection_02.png

    Rule Details Example for a Newspaper Electronic Collection

    Rule_Details_Example_for_a_CCC_Get_It_Now_Electronic_Collection_02.png

    Rule Details Example for a CCC Get It Now Electronic Collection

    Configuring Dynamic URLs for Electronic Collections and Portfolios

    Translatable
    To work with electronic resources, you must have the following roles:
    • Electronic Inventory Operator
    • Electronic Inventory Operator Extended (required for delete operations)
    • Repository Manager
    Instead of managing static links for local electronic collections and portfolios, you can create sophisticated dynamic URLs for local electronic collections and portfolios and embed OpenURL metadata information dynamically. In addition, you can use dynamic URLs to override linking provided by the community knowledge base.
    The Electronic Service Editor and Electronic Portfolio Editor pages enable you to define a list of conditions that are used to select a linking URL for the service or portfolio, respectively.
    Dynamic_URL_Linking_Information_Conditions_Example_NewUI_06_TC.png
    Dynamic URL Linking Information Conditions Example
    When using dynamic URLs, each condition must start with an IF statement that checks for the existence of ContextObject and OpenURL parameters. If all parameters exist for a condition starting at the top of the list, the specified URL for that condition is used for linking. Otherwise, the next condition will be checked, and so forth. To catch any case (use this to match if all other checks fail), use IF () <url>.
    For example:
    IF (rft.issn, rft.year, rft.volume)
    http://www.publisher.com/{rft.issn}/{rft.year}/{rft.volume}
    IF (rft.issn, rft.year)
    http://www.publisher.com/{rft.issn}/{rft.year}
    IF (rft.issn) http://www.publisher.com/{rft.issn}
    IF ()
    http://www.publisher.com
    If the first condition is met in the above example, the resulting dynamic URL may look something like the following:
    http://www.publisher.com/1364-0321/2010/2
    In addition to rft.year, you can also use rft.month, rft.day, and rft.date attributes.
    Test dynamic URL syntax enables you to verify the syntax of your conditions.
    For more information about configuring dynamic URLs for electronic collections, see the Dynamic URLs For Electronic Collections video (2:33 mins).

    See Commonly Used OpenURL Attributes for the URL Template for more information.

    URL Functions

    In addition, the dynamic URL may include any of the following functions to manipulate the values returned in the specified parameters:
    • SUBSTR (string, from, length) - Return a substring of the specified string, based on the starting position and length of the string. If {rft.date} contains 2010-08-01, and the first four characters from the beginning of the string are specified, as follows:
      http://www.publisher.com/{rft.issn}/SUBSTR({rft.date},0,4)
      Alma uses the following URL:
      http://www.publisher.com/1824-6321/2010
    • REPLACE (string, search, replace) - Replace text in the specified string, based on search and replacement text. If {rft.isbn} contains dashes (for example, 978-1-285-13563-2) and no replacement text is specified, as follows:
      IF (rtf.isbn)
      http://www.publisher.com/REPLACE({rft.isbn},-,"")
      Alma uses the following URL:
      http://www.publisher.com/9781285135632
    • URLENCODE (string) - Encode special characters in the specified string. If {rft.atitle} contains the title The Grapes of Wrath, and encoding is requested, as follows:
      http://www.publisher.com/URLENCODE({rft.atitle})
      Alma uses the following URL:
      http://www.publisher.com/The%20Grapes%20of%20Wrath
    Electronic collections are available (to be published to Primo) after they have been activated. The exception to this is database type electronic collections, which are available to be published as soon as they are defined by a URL and an associated unsuppressed bibliographic record.
    You can define portfolios as standalone entities or as part of an electronic collection. The procedure for adding electronic collections and their associated portfolios is provided in Adding a Local Electronic Collection. The procedure for adding a portfolio independent of adding an electronic collection is provided in Managing Local Portfolios.

    Resolver Proxies

    Translatable
    To configure a resolver proxy profile, you must have the following role:
    • General System Administrator
    To enable off-campus users to access full text services at different vendor sites, you must define a proxy server, which is used to authenticate these users.

    The Alma Link Resolver responds to an incoming OpenURL and changes it to an electronic link by automatically including additional proxy information in the resolved URL. Some institutions use a single proxy server, in which case one proxy profile should be defined. If an institution uses several proxy servers, a proxy profile should be defined for each proxy server. You must then define the relevant proxy for each electronic collection, service, or portfolio.

    When distributing access to electronic resources through the Network Zone to members, proxies must be managed in the Institution Zone rather than the Network Zone. The Institution Zone proxy will override any proxy defined in a Network Zone collection.

    See the following for additional proxy information:

    Proxy Relationships

    The following table presents the relationships between the proxy-enabled setting for electronic collections, services, and portfolios. Portfolios inherit the proxy-enabled setting from the service-level setting to which they are attached. As a result, set a portfolio-level proxy-enabled setting only when you want it to be different from the service-level setting (in which case, leave the Proxy selected field on the service level blank). The electronic collection proxy-enabled settings are not inherited by portfolios.
    Proxy Relationships
    Proxy Enabled for Electronic Collection Level Proxy Enabled for Service Level Proxy Enabled for Portfolio Level Proxy Enabled Setting Results
    N N N Redirected to resource
    N N Y Redirected to proxy login
    N Y N Redirected to proxy login
    Portfolio inherits service setting
    N Y Y
    The electronic collection does not inherit proxy settings from the service or portfolios. If a proxy profile is selected on the service level, portfolios inherit the proxy setting from the service level. To set the proxy for the portfolio level, leave the Proxy selected field of the service-level setting blank.
    Y N N Redirected to the resource
    The Electronic Collection proxy is not inherited by the service or portfolio level
    Y N Y Redirected to proxy login
    Y Y N Redirected to proxy login
    Portfolio inherits the service setting
    Y Y Y Redirected to proxy login

    Configuring a Proxy

    To configure a resolver proxy definition type of integration profile:
    1. On the Integration Profile List page (Configuration Menu > General > External Systems > Integration Profiles), select Add Integration Profile. The first page of the integration profile wizard appears.

    2. Select Resolver Proxy for Integration Type.

    3. Enter a name (Code) for the profile you are defining and, optionally, enter a description.

    4. Select Default if you want the profile you are defining to be the default proxy definition profile. (If you previously defined another profile as the default profile, clear the Default selection in the other profile before selecting Default in this profile). If the proxy is set as the default, and Actions (see below) is set to Always, then this proxy is used for resolving any resource, even resources that do not have ProxyEnabled=Yes.

    5. Select Next. The second page of the wizard appears.

      Resolver_Proxy_Integration_Profile_2.png

      Resolver Proxy Integration Profile – Step 2 (Proxy Definitions)
    6. Select the type of proxy server that you want to configure for this profile.

      There is no option to enter multiple IP addresses. The "Proxy IP" field should hold the proxy server IP address and not some allowed IP range. In case the OpenUrl request will come from this IP address, the proxy will not be added to the target Url, and this is to avoid looping. 

      The following options are available:

      • Biblio-Pam – This server proxy uses the following URL structure:

        The <Biblio-PAM URL> portion of the structure is the vendor-provided URL from Biblio-PAM.

        The <shortened target URL> is the target URL without the http:// or https://.

        • https://<Biblio-PAM URL>/http/<shortened target URL>

        • https://<Biblio-PAM URL>/https/<shortened target URL>

      • EZProxy – This option uses the following URL structure where $@ is the placeholder for the target URL:
        • https://www.ezproxy.unibo.it/login?
        See EZProxy URL Database for more information.
      • HAN – This option uses the following URL structure:
        • http://<HAN server>/hanapi/?hash=<HASH>
        Enter the http://<HAN server> portion for the Proxy url parameter.
        The remainder of the URL structure is constructed by Alma and appended to the portion of the URL that you entered in the Proxy url parameter.
        For the HAN proxy server type, you need to enter a Salt parameter. The Salt parameter is a free text field that may contain any alpha-numeric value. The value that you enter must identically match the salt value in the HAN proxy server configuration in your HAN account. When you create the HAN salt value in your HAN account, copy it to the Salt parameter in Alma.
      • LIBProxy

      • OpenAthens - This option uses the following URL structure:

        "http://" + {base_url}+ "." + {PROXY_URL} + {URL_PARAMETERS};

        For example:

        Target_url = www.google.com/help=true&test=false

        Proxy_url = proxy.com

        Resulting URL: http://www.google.com.proxy.com/help=true&test=false

      • OpenAthens Redirector – This option uses the following URL structure:
        • https://<OpenAthens Redirector URL>?url=<encoded target URL>
        The <OpenAthens Redirector URL> portion of the structure is the vendor-provided URL from OpenAthens.
        Enter https://go.openathens.net/redirector/<your domain> for the Proxy url parameter.
        The ?url= portion of the URL is added by Alma.
        The <encoded target URL> is the target URL in its encoded form.
        Note that even though Redirector is not a proxy server, the Alma proxy server configuration can be used.
      • WAM
        Note that you should omit the 0- at the beginning of your proxy URL.
    7. Enter the proxy URL as provided by the vendor (including http:// or https://) and the proxy IP address.

    8. Select one of the following values for Use Proxy:

      • Always – The proxy is used for any resolving.

        If this proxy is selected as default, it is used for any resolving, even for resources (services, collections, or portfolios) with EnableProxy=No.

        If this proxy is not selected as default, it is used for resources where EnableProxy=Yes and this proxy is selected.

        This configuration overrides the configuration in the Network Zone.
      • Never – This proxy is never used for resolving, even if it is enabled and selected for a particular resource.

      • Selective – This proxy is used for resources where EnableProxy=Yes and this proxy is selected (this is equivalent to selecting Always for a non-default proxy).

        Even if this proxy is selected as the default, it must be added to the resource explicitly.

    9. Select Save. The profile is saved.

    Translatable

    General Electric Services

    Adding a General Electronic Service

     

    Translatable

    Return to menu

    To configure general electronic services, you must have one of the following roles:

    • General System Administrator

    • Fulfillment Administrator

    This section applies only to Primo. For information on how to configure general electronic services in Primo VE, see Configuring General Electronic Services for Primo VE

    In addition to services found in your own collection (such as full text, requests, and so forth), Alma enables you to define general HTTP services (such as searches in ProQuest dissertations and Amazon.com, Ask a Librarian, and so forth) to present to patrons in Primo. To have these services appear in Leganto, see Enabling General Electronic Services in Leganto.

    AlmaP_GES_Example.png

    Electronic Service Example (Primo View It)

    In order to create a general electronic service, you must be familiar with the syntax of the service’s URL, which includes any parameters that are required to query or access specific information from the service. The service’s URL along with OpenURL context object attributes returned from Alma’s link resolver are used to define the URL template, which Alma uses to create the service link that appears in View It and/or Get It.

    In addition, you can configure the following display settings for general electronic services:

    You can also share your general electronic services in the Community Zone, and use general electronic services defined by other institutions. See Sharing General Electronic Services in the Community Zone

    To configure general electronic services:

    It is recommended to use ExLibris's Unpaywall service in View It and not an externally used customer Unpaywall GES. This is because the open access in ExLibris's Unpaywall service is 100% available. 

    1. Open the General Electronic Services Configuration page (Configuration Menu > Fulfillment > Discovery Interface Display Logic > General Electronic Services). In addition to the columns that are visible on the General Electronic Services list, the Item Level column may be added to the view in the view configuration.

      GES_NewUI.png

      General Electronic Services List
    2. Select Add Service. The Add Service dialog box opens.

      AlmaPrimo_AddService.png

      Add Service Dialog Box
    3. Enter the following service information:

      • Service Code – The internal code for the service.

      • Service Name – The internal name used for the service.

      • Service Description – The description of the service.

      • Public Name – The label for the link that displays in View It and/or Get It.

      • Public Note – The note or description of the service that displays below the link in View It and/or Get It.

      • Display Location – Specify the areas within a record's full display that you want to display the GES link. The following options are valid in Primo: None, Getit, Viewit, and Getit & Viewit.

        The display of general electronic services is based on the service's availability rules that are defined with the Service Availability Rules tab, which appears while editing a general electronic service. For more details, see step 5. See Configuring Display Logic Rules if you want to hide the general electronic service based on additional criteria (such as the existence of another type of service or the type of user).
      • URL Template – The URL where the patron is redirected when the external service link is selected. The external service link is comprised of the base URL of the service, and any parameters that are required to query or access specific information from the service. It is formatted according to the syntax of the URL of the service. For more information, see  URL Template.

      • Item Level - This option displays only when Display Location is set Getit. Select Yes to show the link next to each item that matches the input rules. Select No to show the link at the holding level.

        To prevent potential performance issues, Item-level General Electronic Services cannot be used for the If Exists portion of Display Logic Rules.

        For more information, see Item Level General Electronic Service.

    1. Select Add and Close. The new service appears on the General Electronic Service page with the following row actions: Remove and Edit.

    2. Edit the new row to configure additional service details.

      The Service Details page appears.

      AlmaPrimo_ServiceDetails_ProQuest.png

      Service Details Page (Service Details Tab)
    3. To display this service to signed-in users only, select No in the Enable without login field.

    4. To hide this service based on the availability of the physical resource in the institutional repository, select one of the following options for Disable Service:

      When a guest user or a user without a configured campus performs any of the campus-level disabling activities, Alma disables/hides the service based on a self-ownership check done at the institution level.

      • Never – The service is never disabled.

      • When resource is owned by the campus – The service is disabled when physical items for the resource are owned by the campus.

      • When resource is owned by the campus and available – The service is disabled when physical items for the resource are owned by the campus and are available (that is, they are not involved in a process).

      • When resource is owned by the institution – The service is disabled when there are physical items for the resource that are owned by the institution.

      • When resource is owned by the institution and available – The service is disabled when there are physical items for the resource that are owned by the institution, are in place, and are in an open location. Note that if a physical location is set to Unavailable (see Adding a Physical Location) and this option is selected, the service is enabled. You may want to use this option when items in a certain location (such as a reading room) cannot be requested. Setting this location to Unavailable will enable the display of the service.

    5. Select the Service Availability Rules tab.

      The Service Availability Rules tab displays the rules that the system uses to determine whether a service should be hidden from the user. Each service has a default rule that is applied when none of the other rules apply. The Default general electronic service rule hides the service by default (IsDisplay=False). You can edit the default rule and add rules as needed.

      GES_ServiceAvailabilityRules_NewUI.png

      Service Availability Rules Tab
    6. Add rules regarding the OpenURL context object attributes (which may be returned by Alma’s link resolver during the user’s search) to ensure that Alma has the necessary information to display the service.

      • The available attributes are standard OpenURL attributes. For more information, see Commonly Used OpenURL Attributes for the URL Template.

      • The following item level attributes may be used when item level services are configured:

        • material_type

        • item_policy - values are populated from the institution's Item Policy table. See Configuring Item Policies.

        • process_type

        • base_status - values are Item not in place and Item in place.

      • Adding parameters within a rule will cause the parameters to have an AND relationship with each other, meaning that all values must be true before the rule is considered true. For OR conditions, where only one of values must be true, parameters should be entered separately in a new rule.

      • If multiple rules evaluate to true, the output parameter will be applied based on the first rule that is true.

      1. To add a new rule, select Add Rule. The Edit Rule page opens.

        AddGES_Rule_NewUI.png

        Edit Rule Page
      2. In the Edit Rule section, enter the rule name (required) and description (optional).

      3. In the Input Parameters section, select Add Parameter. The Add Parameter dialog box opens.

        GES_AddParameter_NewUI.png

        Edit Rule Page
      4. Enter the following fields:

        • Name – The name of the attribute in the OpenURL context object. For more information about these attributes, see Commonly Used OpenURL Attributes for the URL Template.

        • Operator – The comparison operator to use with this context object attribute.

        • Value – An accepted value for this parameter. To match multiple values, create a separate rule for each value. Note that not all operators require a value.

      5. Select Add Parameter. The parameter is added to the input parameter list.

      6. In the Output Parameters section, set IsDisplay to true.

      7. Select Save. The Service Availability Rules page displays the new rule.

    7. Select Save. The General Electronic Services page displays the new service.

    In a collaborative network, you can create general electronic services in the Network Zone and then distribute them to member institutions. The member institutions have view permission to the distributed records but are not able to edit or delete them. When the Network Zone general electronic service has been distributed, the local list will show either the distributed records only or both the distributed records and the previous local general electronic service records, depending on the configuration in the customer parameter, network_ges_distribution_members_behavior.

    General Electronic Services New UI.png

    General Electronic Services List for a Member Institution

    For more information, see Configuring Fulfillment Information in the Network Zone.

    URL Template

    The URL substitutes OpenURL fields that are enclosed in brackets ( "{" and "}") with the relevant values. For example, the referring URL’s ISBN is substituted into a URL containing: ...&isbn={rft.isbn}&...

    For example, the URL for an Amazon search for a specific ISBN:

    http://www.amazon.com/s/ref=nb_sb_ss_c_0_12?url=search-alias%3Dstripbooks&field-keywords={rft.isbn}

    When connecting to a resource sharing broker, ensure that this field contains an attribute corresponding to the broker in use. For example, when using the OCLC broker:

    http://xxx.worldcat.org/oclc/{rft.oclcnum}

    ILLiad - Books/Book Items (based on your institution’s base URL). For example:

    http://libill.XXX.edu/illiad/illiad.dll?Action=10&Form=30&rft.genre={rft.genre}&rft.title={rft.btitle}&rft.stitle={rft.stitle}&rft.atitle={rft.atitle}&rft.date={rft.pubdate}&rft.month={rft.month}&rft.volume={rft.volume}&rft.issue={rft.issue}&rft.number={rft.number}&rft.epage={rft.epage}&rft.spage={rft.spage}&rft.edition={rft.edition}&rft.isbn={rft.isbn}&rft.eisbn={rft.eisbn}&rft.au={rft.aulast},{rft.aufirst}&rft.auinit={rft.auinit}&rft.pub={rft.pub}&rft.publisher={rft.publisher}&rft.place={rft.place}&rft.doi={rft.doi}&rfe_dat={rft.oclcnum}&rfr_id={rfr_id}

    ILLiad - Articles/Journals (based on your institution’s base URL). For example:

    http://libill.XXX.edu/illiad/illiad.dll?Action=10&Form=30&rft.genre={rft.genre}&rft.title={rft.title}&rft.stitle={rft.stitle}&rft.atitle={rft.atitle}&rft.jtitle={rft.jtitle}&rft.au={rft.au}&rft.date={rft.year}&rft.month={rft.month}&rft.volume={rft.volume}&rft.issue={rft.issue}&rft.number={rft.number}&rft.spage={rft.spage}&rft.epage={rft.epage}&rft.edition={rft.edition}&rft.issn={rft.issn}&rft.eissn={rft.eissn}&rft.aulast={rft.aulast}&rft.aufirst={rft.aufirst}&rft.auinit={rft.auinit}&rft.pub={rft.pub}&rft.pubdate={rft.pubdate}&rft.pubyear={rft.pubyear}&rft.publisher={rft.publisher}&rft.place={rft.place}&rft.doi={rft.doi}&rfe_dat={rft.oclcnum}&rfr_id={rfr_id}

    ProQuest - Dissertation Service. For example:

    http://gateway.proquest.com/openurl?res_dat=xri%3Apqm&title={rft.btitle}&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adissertation&url_ver=Z39.88-2004&genre=dissertation

    The following values can be specified in the URL Template parameter between the curly brackets used for normalizing the ISBN, ISSN, eISBN, or eISSN:

    • rft.normalized_isbn

      This normalization removes the text after digits and the hyphen (-) and converts ISBN 10 to ISBN 13

    • rft.normalized_issn

      This normalization removes the text after digits and changes text to lower case.

    • rft.normalized_Eisbn

      This normalization removes the text after digits and the hyphen (-) and converts ISBN 10 to ISBN 13.

    • rft.normalized_Eissn

      This normalization removes the text after digits and changes text to lower case.

    For more information regarding OpenURL, refer to the following:

    Commonly Used OpenURL Attributes for the URL Template

    The OpenURL attributes returned from Alma’s link resolver are grouped by the following general categories:

    OpenURL Attribute Categories
    Category Prefix Description
    Requester req. Information about the requesting entity, that is, the patron. Not used when creating service availability rules for general electronic services.
    ReferringEntity rfe. Information about the referring entity, i.e. Primo. Not used when creating service availability rules for general electronic services.
    Referent rft. Information about the requested item.
    ServiceType svc. Whether a particular format of the Referent is available: "yes" or "no". For example, whether the requested target is available as an abstract or as full text. Multiple service types may be available.
    Other various Other returned values are unused, unless noted below.
    The following are commonly returned attributes that can be used to create service availability rules:
    Commonly Returned OpenURL Attributes from Alma’s Link Resolver
    Attribute PNX Mapping MARC 21 Fields Description
    req_id     The PDS handle (see Identify Patrons to Provide Relevant Services)
    rft.advisor     Advisor, for a dissertation
    rft.applcc     Application country code in ISO two-character format, for a patent. The country in which the patent application was main.
    rft.appldate     Date of application, for a patent
    rft.applyear     Year of application, for a patent
    rft.artnum addata/artnum   Article number. Assigned by the publisher. A URL may be the only usable ID for an online article.
    rft.assignee     Assignee, for a patent: "Smith, John J.", "IBM"
    rft.atitle addata/atitle   Article or chapter title
    rft.au addata/au 100 or 110 or 111 One author's full name: "Smith, Fred James Jr."
    rft.aucorp addata/aucorp   Organization or corporation that created document: "Mellon Foundation"
    rft.aufirst     First author's given name: "Fred James" May have spaces and punctuation.
    rft.auinit addata/auinit   First author's first and middle initials
    rft.auinit1 addata/auinit1   First author's first initial
    rft.auinitm addata/auinitm   First author's middle initial
    rft.aulast addata/aulast   First author's last name: "Smith" May have spaces and punctuation.
    rft.ausuffix addata/ausuffix   First author's name suffix: "Jr." etc.
    rft.bici addata/bici   Book Item and Component Identifier (BICI code)
    rft.btitle addata/btitle For the LDR positions, see Fields that Identify the Bibliographic Material Type. Book title, if the LDR material_type = BK. See rft.jtitle.
    rft.cc     Publication country code, in ISO two-character format: "US". See co.
    rft.chron     Enumeration or chronology not in standard format: "1st quarter". Where possible, use date. See ssn and quarter.
    rft.co     Publication country: "United States". See cc.
    rft.coden addata/coden   CODEN (alphanumeric code)
    rft.date addata/date   Publication date. For a patent, this is the date that the patent was issued. Format is YYYY, YYYY-MM, or YYYY-MM-DD.
    rft.day     Publication day
    rft.dcContributor     Dublin Core contributor: person, organization, or service
    rft.dcCreator     Dublin Core creator: person, organization, or service
    rft.dcDescription     Dublin Core description: abstract, table of contents, graphical representation, or free text
    rft.dcFormat     Dublin Core format: File format, physical medium, or dimensions, such as MIME type
    rft.dcIdentifier     Dublin Core identifier: Unambiguous resource identifier
    rft.dcLanguage     Dublin Core language: Resource language
    rft.dcPublisher     Dublin Core publisher: person, organization, or service
    rft.dcRelation     Dublin Core relation: A related resource
    rft.dcRights     Dublin Core rights: Rights information
    rft.dcSource     Dublin Core source: A related resource from which this resource was taken
    rft.dcSubject     Dublin Core subject: keywords and classification codes
    rft.dcTitle     Dublin Core title: Resource title
    rft.dcType     Dublin Core type: nature and genre, such as described by DCMITYPE. For format, see dcFormat.
    rft.degree     Degree issued, for a dissertation
    rft.doi addata/doi   DOI (digital object identifier) field
    rft.edition display/edition 250 a Book edition, typically a phrase, with or without numbers: "First edition", "4th ed.".
    rft.eisbn addata/eisbn 020 a if there is no 020 e and the record is not physical; otherwise 020 e International Standard Book Number for electronic version. May be multiple ISBN, separated by commas. May contain a hyphen. May or may not be distinct from rft.isbn.
    rft.eissn addata/eissn 022 a if there is no 022 e and the record is not physical; otherwise 022 e International Standard Serial Number for electronic version. May be multiple ISSN, separated by commas. May contain a hyphen. May or may not be distinct from rft.issn.
    rft.epage addata/epage   End page of article/chapter within volume/issue.
    rft.format addata/format   MIME type of the format
    rft.genre addata/genre   One of:
    • article: document published in a journal
    • book: complete in a single part, often identified by an ISBN
    • bookitem: section of a book, usually with a title or number
    • conference: record of a conference (one or more conference papers)
    • issue: single issue
    • preprint: paper or report published in print or electronically prior to publication in journal or serial
    • proceeding: conference presentation published in a journal or serial publication
    • report: report or technical report published by an organization, agency, or governmental body
    • unknown
    rft.inst     Issuing institution, for a dissertation
    rft.inventor     Inventor’s full name: "Smith, John J.". For a patent.
    rft.invfirst     Inventor’s given names: "John J.". For a patent.
    rft.invlast     Inventor’s last name: "Smith". For a patent.
    rft.isbn addata/isbn 020 a if there is an 020 e; otherwise 776 z if the record is not physical or 020 a if there is no 020 e and the record is physical International Standard Book Number. Nine digits plus a check digit. May contain hyphens.
    rft.issn addata/issn 022 a if there is no 022 e and the record is phpysical; otherwise 022 a if there is an 022 e or 776 x if the record is not physical International Standard Serial Number. May contain a hyphen. ISSN for a book may be associated with the series.
    rft.issue addata/issue   Journal issue: "Spring 1998". Typically numeric.
    rft.jtitle addata/jtitle For the LDR positions, see Fields that Identify the Bibliographic Material Type. Full journal title, if the LDR material_type = CR. See rft.btitle. For example, "Journal of the American Medical Association". For short title, use stitle.
    rft.kind     Patent kind code, for a patent: "AU A1". Kind codes are meaningful within the country of origin.
    rft.month     Publication month
    rft.number     Application number, for a patent
    rft.object_type   For the LDR positions, see Fields that Identify the Bibliographic Material Type. The LDR material_type. The default is BOOK.
    rft.oclcnum addata/oclcid 035 a,z OCLC control number or journal level OCLC number. May be multiple OCLC control numbers, separated by commas.
    rft.pages addata/pages   Start and end pages of article/chapter within volume/issue: "53-58". Can also contain pages not in sequence, e.g. "12-6,64-67". See spage and epage.
    rft.part addata/part   Either a subdivision of, or in place of, volume. Examples: "B", "Supplement".
    rft.place addata/cop 260 a or 264 a Publication place: "New York".
    rft.prioritydate     Priority date, for a patent
    rft.pub addata/pub 502 a,c or 260 b or 264 b Publisher name: "Harper and Row".
    rft.pubdate   260 c or 260 g or 264 c or 362 a or 008(date1) Publication date, for a patent
    rft.publisher   502 a,c or 260 b or 264 b Publisher name
    rft.pubyear     Year of publication
    rft.quarter addata/quarter   Chronology: "1", "2", "3", or "4". For non-standard chronology, use chron.
    rft.series addata/seriestitle   Title of the series that contains this book. There may also be an ISSN associated with the series.
    rft.sici addata/sici   Serial Item and Contribution Identifier (SICI code)
    rft.spage addata/spage   Start page of article/chapter within volume/issue
    rft.ssn addata/ssn   Season: "winter", "spring", "summer", or "fall". For non-standard season, use chron.
    rft.stitle addata/stitle 245 a Short journal title: "J Am Med Assn". For full title, use jtitle.
    rft.title   245 a,b Book title (deprecated: use btitle), journal title (deprecated: use jtitle), dissertation title, patent title
    rft.tpages     Total pages: "392". Typically only for monographs (books and printed reports). May not be numeric: "F96".
    rft.volume addata/volume   Journal volume: "124". Typically numeric, but may be roman numerals, etc.
    svc.abstract     Abstract
    svc.any     Any format
    svc.citation     Citation
    svc.fulltext     Full text
    svc.holdings     Holdings information. This field is not used to hide services based on whether the record has holdings. If it is included in the OpenURL, it will be saved in the Context Object for use in the GES.
    svc.ill     Interlibrary loan

     

    Item-Level General Electronic Service

    When the General Electronic Service is added as an item level service, the URL template may be configured to make use of the following Holdings and item level information:

    Holdings/Item Element Name of Placeholder
    Current Library (Code) library
    Current Location (Code) location
    Current Call Number call_number
    Barcode barcode
    Material Type (Code) material_type
    Current Item Policy (Code) item_policy
    MMS ID mms_id
    Process Type (Code) process_type
    Item description description

    In addition, it is possible to add fields from the Holdings record to the URL template. The placeholder syntax is HOL_{field}_{indicators}_{subfields}. The use of indicators is optional. For example:

    • HOL_506_ab - Alma will extract subfields a and subfield b from 506 field. Each subfield will be delimited from the next one with a space. The indicators are not taken into account.

    • HOL_506_12_df - Alma will extract subfields d and subfield f from 506 field only when indicators 1 and 2 exists. Each subfield will be delimited from the next one with a space.

    • HOL_506_1#_g - In this scenario, Alma will extract subfields g from 506 field only when the first indicator value is 1 with no dependency on the second indicator.

    A sample URL template may be : <baseURL>?LIB={library}&BARCODE={barcode}&FIELD1={HOL_506_ab}.

    Message Customization 

    When there are no full text services available for the OpenURL request, the Electronic Services page displays a message. An administrator can customize the wording of the message. 

    This configuration is applicable to Alma-Primo environments and does not apply to Primo VE.

    To customize the wording for the 'no full text' message:

    1. Open the Discovery Interface Labels code table (Configuration Menu > Fulfillment > Discovery Interface Display Logic > Labels).
    2. Locate the row with c.uresolver.emptyList in the Code column.
    3. Select Customize. The Description column cell in that row opens for you to enter your customized message text.
    4. Enter the text you want to appear on the Electronic Services page when no full text is available.

      If you prefer that no message be displayed when no full text is available, leave this option blank.

    5. Select Save.
    Translatable

    Troubleshooting

    Using the OpenURL Link Resolver Debugger Tool

    You can use a debugger tool to troubleshoot the context services that are offered by the OpenURL Link Resolver. The tool enables you to enter an OpenURL input message and receive an XML debugger response from the OpenURL Link Resolver. From the XML response, you can:
    • Determine the service calculation:
      • View the context object that was calculated based on the OpenURL parsing, augmentation, and related service.
      • Understand how the context services object was generated:
      • What were the potential services?
      • Which services were added based on the calculation of related services?
      • Which services were filtered out based on coverage or rules for general electronic services and display logic?
    • Determine the link resolution and how the OpenURL was generated:
      • Which target parser was used?
      • Was a proxy used?
      • Was it a static URL on the portfolio level?
      • Is there a direct link?
      • View the generated targetURL.
    • View the original OpenURL in the debugging content provided.
    • Enriching the data (context object) from CrossRef using the DOI is handled before matching.
    • For information about debugging a citation's uResolver (OpenURL) link, see the knowledge article Debugging Citation uResolver Links.
    To run the debug tool:
    1. Search the repository for the electronic title or portfolio that you want to test access.

      For Primo VE environments, you can also use Primo VE to search for and display the electronic record's full display. Skip to step ii in the Primo VE section.

    2. Depending on your type of Primo environment, perform the following steps:

      • Alma-Primo:

        1. Depending on the type of results, select View It (electronic titles) or Test Access (electronic portfolios) for an item in the results list. You can also test access from the Portfolios List page and the Portfolios tab on the Electronic Service Editor page.

          Alma-Primo_ViewIT.png

          Display View It Tab
        2. In the View It tab, select Display in a new window.

          Primo_DisplayInNewWindow.png

          View It Tab
        3. Right-click the Electronic Services page and select the option to view the page or frame source. The options are somewhat different for each browser.

          Select_View_Page_Source_Option_NewUI_02.png

          Select View Page Source Option
        4. Locate the DEBUG section at the top of the source view and copy the URL.

          HighlightCopyDebug_URL.png

          Highlight and Copy the DEBUG URL
        5. Open a new browser page or tab, paste the debug URL that you copied in the previous step into the address bar of the new page or tab, and press enter to view the XML debugger output.

      • Primo VE:
        To debug, you will enable the Display CTO button, which is hidden in regular use. Selecting this button displays the Context Object (CTO) that provides you with additional information about the result, to help you troubleshoot the context services that are offered by the OpenURL Link Resolver. 

        1. For a record in the results list, select Display in Discovery to open its full display.

          PVE_DisplayInDiscovery.png

          View Full Display Page in Primo VE
        2. To enable the Display CTO button, add the following parameter to the end of the record's full display URL and then press enter: &displayCTO=true.
          CTO is the Context Object that provides you with additional information about the result, to help you troubleshoot the context services that are offered by the OpenURL Link Resolver. 

          For example:

          https://<Alma instance>/discovery/fulldisplay?docid=alma9926095600521&context=U&vid=PRIMO_OAP_INST:Alma&lang=en&displayCTO=true

          PVE_DisplayCTO_Button.png

          Display CTO Button Enabled on Full Display Page
        3. Select Display CTO to display the XML debugger output.

    3. Scroll through the XML to analyze/debug your search result issues. After the <context object> element is the <context services> element that contains information regarding service type, parsing, proxy, the target URL, and so forth.

      Notice that in cases where records were filtered out from displaying in the results, the XML output contains key IDs for Filter (true or false) and Filter reason. For example, if Filter reason contains Date Filter and the OpenURL input specified a data parameter of year=2010, this may indicate that the record was filtered because it was outside of the specified date range.

      <uresolver_content xmlns="http://com/exlibris/urm/uresolver/xmlbeans/u" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <context_object>
          <keys>
            <key id="rft.stitle">Test</key>
            <key id="rft.pub">Springer</key>
            <key id="rft.place">Berlin :</key>
            <key id="licenseEnable">true</key>
            <key id="sfx.sid">primo.exlibrisgroup.com</key>
            <key id="rft.jtitle">Test</key>
            <key id="available_services">viewit</key>
            <key id="available_services">getit</key>
            <key id="rft.genre">journal</key>
            <key id="Incoming_URL">http%3A%2F%2Fdocedu-na01.alma.exlibrisgroup.com%2Fview%2Furesolver%2FTRAINING_1_INST%2Fopenurl%3Fdebug%3Dtrue%26svc_dat%3DCTO%26debug%3Dtrue%26debug%3Dtrue%26%26u.ignore_date_coverage%3Dtrue%26rft.mms_id%3D9926095600521%26rfr_id%3Dinfo%3Asid%2Fprimo.exlibrisgroup.com%26svc_dat%3Dviewit%26u.ignore_af_filter%3Dtrue%26internalAccess%3Dtrue%26isInNewWindow%3Dtrue</key>
            <key id="institution">521</key>
            <key id="internalAccess">true</key>
            <key id="rft.oclcnum">62155677</key>
            <key id="u.ignore_af_filter">true</key>
            <key id="req.id" xsi:nil="true"/>
            <key id="rft.mms_id">9926095600521</key>
            <key id="user_ip" xsi:nil="true"/>
            <key id="debug">true</key>
            <key id="inventory_id">519285510000521</key>
            <key id="rfr_id">info:sid/primo.exlibrisgroup.com</key>
            <key id="rft.inventory_id">519285510000521</key>
            <key id="publication_place">Berlin :</key>
            <key id="rft.object_type">JOURNAL</key>
            <key id="isInNewWindow">true</key>
            <key id="rft.publisher">Springer</key>
            <key id="ctx_id">1325448060000521</key>
            <key id="rft.pubdate">Began with: Vol. 1, no. 1 (Dec. 1992).</key>
            <key id="full_text_indicator">true</key>
            <key id="u.ignore_date_coverage">true</key>
            <key id="rft.title">Test</key>
            <key id="rft.lccn">2009252997</key>
            <key id="customer">510</key>
            <key id="rfr.rfr">primo.exlibrisgroup.com</key>
            <key id="rft.eissn">1863-8260</key>
            <key id="rft.eissn">1133-0686</key>
          </keys>
        </context_object>
        <context_services>
          <context_service service_type="getFullTxt" context_service_id="1325447980000521">
            <keys>
              <key id="package_name">ProQuest New Platform</key>
              <key id="package_public_name">ProQuest Pharma Collection New Platform</key>
              <key id="package_display_name">ProQuest Pharma Collection New Platform</key>
              <key id="package_internal_name">PROQUEST_PHARMA_COLLECTION_NEW_PLATFORM</key>
              <key id="interface_name">ProQuest New Platform</key>
              <key id="package_pid">619246910000521</key>
              <key id="service_type_description">Full text available via</key>
              <key id="character_set">iso-8859-1</key>
              <key id="Is_free">0</key>
              <key id="portfolio_PID">5310098520000521</key>
              <key id="cz_link_id">532670000001098994</key>
              <key id="electronic_material_type">JOURNAL</key>
              <key id="Availability">Available from 1997&lt;br> Most recent 1 year(s) not available&lt;br></key>
              <key id="static_url">true</key>
              <key id="parser_program">PROQUEST::open</key>
              <key id="parse_parameters">url=http://gateway.proquest.com/openurl &amp; clientid= &amp; url2=http://search.proquest.com&amp;jkey=1486339</key>
              <key id="Authentication_note"/>
              <key id="public_note"/>
              <key id="proxy_enabled">false</key>
              <key id="proxy_selected">DEFAULT</key>
              <key id="related_title">@TITLE (@RelationType)</key>
              <key id="is_related_service">false</key>
              <key id="is_closly_related">false</key>
              <key id="license_exist">false</key>
              <key id="crossref_enabled">no</key>
            </keys>
            <resolution_url>https://docedu-na01.alma.exlibrisgro...customerId=510</resolution_url>
            <target_url>http://gateway.proquest.com/openurl?...%2Fsid%3Aprimo</target_url>
            <is_error>false</is_error>
            <error_code>null</error_code>
          </context_service>
        </context_services>
        <performance_counters>
          <performance_counter name="TOTAL" duration="0.0"/>
          <performance_counter name="MMS_LOOKUP" duration="0.0"/>
          <performance_counter name="ENRICH" duration="0.0"/>
          <performance_counter name="PARSE" duration="0.0"/>
          <performance_counter name="GET_SERVICES" duration="0.01"/>
          <performance_counter name="FILTER" duration="0.003"/>
          <performance_counter name="SAVE" duration="0.005"/>
          <performance_counter name="GET_ZERO_TITLE_SERVICES" duration="0.0"/>
          <performance_counter name="FETCH_SERVICE_THRESHOLD_RULES" duration="0.0"/>
          <performance_counter name="CREATE_ZERO_TITLE_SERVICES" duration="0.0"/>
          <performance_counter name="SAVE_ZERO_TITLE_SERVICES" duration="0.0"/>
          <performance_counter name="GET_SINGLE_SERVICE" duration="0.0"/>
          <performance_counter name="EXECUTE_TARGET_PARSER" duration="0.0"/>
          <performance_counter name="GET_URESOLVER_CONTENT" duration="0.0"/>
          <performance_counter name="UPDATE_SELECTED" duration="0.0"/>
        </performance_counters>
      </uresolver_content>
      Example XML Debugger Output

    Link Resolver Usage

    Translatable
    The fields of the Link Resolver Usage subject area can be used to create reports that provide both specific details of link resolver usage as well as a broad perspective of how the Alma link resolver is used. This provides libraries with a useful means of determining proper electronic collection development.
    This subject area supplements the Usage Data subject area, which includes data from vendors, while the Link Resolver Usage subject area takes data directly from the Alma link resolver.
    Using the Link Resolver Usage area, the Design Analytics you can create reports/dashboards for the Link Resolver Usage area and are able to answer the following types of business questions:
    • How many times did users select View It in all sources over a specified period of time?
    • How many times did users select View It in a specific source?
    • How many times did users select View It and no results were produced?
    • How many times did users select View It for a particular source that resulted in no full text?
    • How many times did users select View It for the most frequently requested full?text journals from a particular source?
    Star_Diagram_LR_Usage.png
    Star Diagram – Link Resolver Usage

    Field Descriptions

    The following lists the fields available in Link Resolver Usage.
    Field_Descriptions_LR_Usage.png
    Link Resolver Usage – Field Descriptions

    OpenURL Context Measures

    The OpenURL Context Measures table is a fact table that stores all measures relating to the OpenURL Context. All fields are taken from the CONTEXT_OBJECT table. The primary key is CONTEXT_OBJECT_ID.
    OpenURL Context Measures
    Field Description Additional Information
    Number of Requests The number of times an OpenURL request was sent to the Alma Link resolver.  
    Number of Clicked Requests Indicates if at least one of the services was selected Values are 1 and 0. Each time a request is selected, 1 is added to the total sum.
    Number of Requests Without Services The number of incoming OpenURLs that do not result in any services  
    Number of Services (total) The total number of services offered per incoming OpenURL request The number of services offered per incoming open URL request both from:
    • the “View It” tab within Primo
    • the electronic services page after clicking from another source
    Number of Electronic Services The number of electronic services that appear when a user selects View it The number of electronic services that appear when a user selects View it.
    Number of Digital Services The number of digital representations that appear when a user selects View it In order for this field to have data, you must select the Include Representation services in link resolver statistics check box (Configuration > Fulfillment > Discovery Interface Display Logic > Other Settings).
    Number of Clicked Services (total) The total number of services selected  
    Number of Electronic Clicked Services The number of electronic services a user selects from the View it menu  
    Number of Digital Clicked Services The number of digital representations a user selects from the View it menu. In order for this field to have data, you must select the Include Representation services in link resolver statistics check box (Configuration > Fulfillment > Discovery Interface Display Logic > Other Settings).
    % Clicks from Requests The percentage of incoming OpenURL requests that were selected % Clicks from Requests = (Number of selected requests / Number of Requests) * 100
    % Requests Without Services from Requests The percentage of incoming OpenURL requests that do not have services % Requests Without Services from Requests = (Number of requests without services / Number of requests) * 100

    OpenURL Context Details

    The OpenURL Context details table is a dimension table that stores the details of the OpenURL context object. The primary key is CONTEXT_OBJECT_ID. The context object is the part of the OpenURL that contains the metadata information that identifies the resource to which the OpenURL links.
    OpenURL Context Details
    Field Description Additional Information
    Title The title of the OpenURL Context  
    Author The Author of the OpenURL Context  
    ISSN The ISSN of the OpenURL Context  
    ISBN The ISBN of the OpenURL Context  
    Material Type The Material Type of the OpenURL Context  
    Network Inventory Group
    The network inventory group This field allows you to filter and display link resolver usage by library or campus. This is relevant for institutions using the inventory network groups.
    Request ID The Request ID of the OpenURL Context  
    Article Title The Article Title of the OpenURL Context  
    EISSN The EISSN of the OpenURL Context  
    Source The Source of the OpenURL Context The database/index that generates an OpenURL to the link resolver in order to obtain context-sensitive services for an electronic resource citation/reference.
    Normalized Source The normalized name of the source.  
    Open URL The OpenURL  
    Source Type The Source Type
    This field allows libraries to easily gather data about from where users are coming when using the Alma Link Resolver.
    The following are the possible values for the Source Type field:
    • Alma - the link was selected from within Alma staff user interface
    • Primo and Primo Central - the link was selected from Primo or Primo Central
    • The source - when the link is selected from another source, such as Web of Science, Ebsco, Pubmed, Google Scholar, and all other external sources, the name of the source is used as the source type.

    The Source Field

    The Source field indicates is the database/index that generates an OpenURL to the link resolver in order to obtain context-sensitive services for an electronic resource citation/reference. It appears in the OpenURL after the dash—for example, after &rfr_id=info:sid/primo.exlibrisgroup.com-. It also appears in the Primo PNX record.
    By comparing the Source with other parameters such as Number of Clicked Requests, you can analyze trends in the use of electronic resources.
    The following are some guidelines that indicate how the source is determined: 
    • If a patron selects on a title in Primo that is in Alma, the source is the source ID of the system.
    • If the source has a colon in it, either the user was a staff member testing the link within Alma, or the user received access to an article from within a database by being referred back to the uresolver to see if the user has a subscription that covers it.
    • If the source has an underscore or consists of letters such as wj (Wiley journals), the user received access to the article from a PCI record in Primo.
    The source google does not have a colon and means Google Scholar.
    The following is an example of an OpenURL with the source in bold:
    http://ap01.alma.exlibrisgroup.com/view/uresolver/64OTAGO_INST/openurl?debug=true&ctx_enc=info:ofi/enc:UTF-8&ctx_id=10_1&ctx_tim=2019-09-09T14%3A46%3A59IST&ctx_ver=Z39.88-2004&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&url_ver=Z39.88-2004&rfr_id=info:sid/primo.exlibrisgroup.com-proquest&req_id=&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Mandatory%20death%20penalty%20unjustified%20where%20no%20death%20or%20wounding%E2%80%94ICCPR%20Art%206(2)%20(Zambia)&rft.jtitle=Commonwealth%20Law%20Bulletin&rft.btitle=&rft.aulast=&rft.auinit=&rft.auinit1=&rft.auinitm=&rft.ausuffix=&rft.au=&rft.aucorp=&rft.date=1996-07-01&rft.volume=22&rft.issue=3&rft.part=&rft.quarter=&rft.ssn=&rft.spage=1114&rft.epage=&rft.pages=&rft.artnum=&rft.issn=0305-0718&rft.eissn=&rft.isbn=&rft.sici=&rft.coden=&rft_id=info:doi/&rft.object_id=&rft.eisbn=&rft.edition=&rft.pub=Commonwealth%20Secretariat.&rft.place=London&rft.series=&rft.stitle=&rft.bici=&rft_id=info:bibcode/&rft_id=info:hdl/&rft_id=info:lccn/&rft_id=info:oclcnum/&rft_id=info:pmid/&rft_id=info:eric/((addata/eric%7D%7D&rft_dat=%3Cproquest%3E1791678607%3C/proquest%3E%3Curl%3Ehttps://search.proquest.com/docview/1791678607/%3C/url%3E,language=eng,view=DUNEDIN&svc_dat=viewit&rft_pqid=1791678607&rft_galeid=&rft_cupid=&rft_eruid=&rft_nurid=&rft_ingid=

    Request Date

    The Request Date table is a dimension table that stores the details about the date of the request. The primary key of the table is DATE_KEY.
    Request Date
    Field Description Additional Information
    Request Date The date of the request.  
    Request Start of Week The date of the first business day of the week  
    Request Week Number The number of the week of the year  
    Request Month Key The month key of the request (for example: 1, 2, 3). This field is recommended if you want to sort by month.
    Request Month The month of the request. For example: January, February).
    Request Full Month The month and the year of the request. For example: January 2014.
    Request Quarter The quarter of the request. For example: Q1, Q2.
    Request Year The year of the request. For example: 2014.
    Request Fiscal Month Key The fiscal month key of the request (for example: 1, 2, 3). This field is recommended if you want to sort by the fiscal month.
    Request Fiscal Year The fiscal year of the request.  
    Request Date Filter Used to filter report results by date.  
    Request Date Stores the Hierarchy column that allows the user to drill down from the year to the month to the specific request date. Using this column, a user may view the accumulative measures in each level of the hierarchy.

    Bibliographic Details

    The Bibliographic Details table is a dimension table that stores the bibliographic details of the physical item. The primary key of the table is MMS_ID.
    The field descriptions can be found in the Bibliographic Details shared dimension.
    Bibliographic Details
    Field Source in Alma (for Internal Reference)

    Mapping from

    MARC21

    Mapping from UNIMARC

    Mapping from

    Dublin Core

    Title Taken from display.title in the display section of the operational record

    245 a,b

    249 a,b,c,v

    200 a,c,d,e,h,i dc:title
    Title (Filing) The title with common words such as "The" and "An" removed to help with sorting the title.
    For a video describing the use of this field, see Sort Analytics Reports by Filing Title - Ignoring "The", "A", and "An".

    240

    245

    200 a,e

    500

    Not relevant for Dublin Core
    Title (Normalized) The normalized Title. This field is useful when you want to use the normalized title from one subject area to compare with a report with fields from a different subject area. This field is built in the following manner:
    Alma does the following to the 245 field (except subfields c,h,6 and 8) in the following order:
    1. Removes non filing text.
    2. Removes <<>> and anything between them.
    3. Removes these characters: []|,.;:"
    4. Changes these characters to a space: !@#$%^&*()_+-={}\<>?/~'
    5. Changes characters to lowercase.
    6. Packs spaces (replace all sequences of more than one space with a single space).

    245 a,b

    249 a,b,c,v

    200 a,c,d,e,h,i dc:title
    Title Author Combined and Normalized 100 characters of the normalized title and the first four letters of the author in lowercase letters, with spaces removed See Author and Title Fields See Author and Title Fields See Author and Title Fields
    Title (Complete) The information from MARC field 245, subfields $p, $n, $s, $k, $f, $g. 245 a,n,p,h,b,c,f,g,k,s 200 a-i Currently empty, planned to come from dc:alternative
    Author Taken from display.author in the display section of the operational record 100,110,111 700,701,710,711 Currently empty, planned to come from dc:creator, dcterms:creators
    Author (Contributor) An additional Author field

    711 a,c-e,i,j,n,q,u and its 880

    700 a-e,j,q,u and its 880

    710 a-e,i,n,u and its 880

    700 a-d,f,p

    701 a-d,f,p 

    710 a-h,p

    711 a-h,p

    720 a,f"

    721 a,f

    702 a-d,f,g 

    712 a-h,p

    722 a,f

    Currently empty, planned to come from dc:contributor, dcterms:contributor
    Bibliographic Source of Acquisition Note The name of the people or organization that is the source of the material (from MARC field 541 $a) 541 a   Not relevant for Dublin Core
    Bibliographic Acquisition Accession Number Note The identification code assigned to materials acquired in a single and separate transfer of custody (from MARC field 541 $e). 541 e   Not relevant for Dublin Core
    ISBN Taken from search.isbn in the search section of the operational record MARC 020 a,z MARC 776 z 010 a dcterms:identifier dcterms:ISBN
    ISBN Valid The valid ISBN value MARC 020 a   Not relevant for Dublin Core
    ISSN Taken from the MMS Display Table in the search section of the operational record 022 l,a 776 x (for non-physical records) 011 a f dcterms:identifier dcterms:ISSN
    ISSN Valid The valid ISSN value MARC 022 a   Not relevant for Dublin Core
    Original Cataloging Agency The MARC code or the name of the organization that created the original record 040 a 081 b Not relevant for Dublin Core
    Publisher Taken from display.publisher_const_b in the display section of the operational record

    260 b

    264 b

    210 c

    214 c

    dcterms:publisher, dc:publisher
    Publication Date Taken from display.date_of_publication in the display section of the operational record
    The publication date is determined as follows:
    • the bibliographic details publication date comes from 264 subfield c
    • if there is no 264 subfield c, then the publication date comes from 260 subfield c
    • if there is no 264 subfield c and also no 260 subfield c, then the publication date comes from 008 pos. 7-10
    The publication date is determined as follows:
    • the bibliographic details publication date comes from 210 subfield d
    • If there is no 210 subfield d, then the publication date comes from field 214 subfield d.
    • if both fields do not exist, then the publication date comes from field 100 subfield a pos. 9-12 
    dc:date
    Publication Place Taken from display.place_of_pu blication in the display section of the operational record 260 a 264 a 210 a 214 a Not relevant for Dublin Core (use Place Code)
    Place Code Taken from display.place_code in the display section of the operational record 008 pos. 15-17   Currently empty, planned to come from dcterms:spatial
    Place of Publication - Country The country of publication For a list of country codes, see:

    MARC Code List for Countries

    For a list of country codes, see:

    List of ISO 3166 Country Codes

    Not relevant for Dublin Core (use Place Code)

    If the value of this field in the bibliographic record does not exist in the official list of place codes, the value for this field in Alma Analytics will be "No place, unknown, or undetermined". If there are multiple place codes in this field, only the first value is displayed.

    Place of Publication - State The state of publication For a list of country codes, see:

    MARC Code List for Countries

    For a list of country codes, see:

    List of ISO 3166 Country Codes

    Not relevant for Dublin Core (use Place Code)

    If the value of this field in the bibliographic record does not exist in the official list of place codes, the value for this field in Alma Analytics will be "No place, unknown, or undetermined". If there are multiple place codes in this field, only the first value is displayed.

    Place of Publication - City The city of publication For a list of country codes, see:

    MARC Code List for Countries

    For a list of country codes, see:

    List of ISO 3166 Country Codes

    Not relevant for Dublin Core (use Place Code)

    If the value of this field in the bibliographic record does not exist in the official list of place codes, the value for this field in Alma Analytics will be "No place, unknown, or undetermined". If there are multiple place codes in this field, only the first value is displayed.

    Material Type See the table, Fields that Identify the Bibliographic Material Type, in the Material Types in Search Results section for a description of material type. MARC control LDR Material Type   Planned to be empty.  Currently comes from dc:type
    Material Type Code Code of the material type described above (in Material Type). MARC control LDR Material Type   Not relevant for Dublin Core
    Begin Publication Date Taken from display.begin_pub_date in the search section of the operation 008 pos. 07-10 100.Date1 Not relevant for Dublin Core
    End Publication Date Taken from display.end_pub_date in the search section of the operation 008 pos. 11-14 100.Date2 Not relevant for Dublin Core
    Category of Material Taken from display. category_of_material in the display section of the operational record Position 0 of the 007 field  200 b dc:type
    Bibliographic Level Taken from display.bib_level in the display section of the operational record Position 7 of the LDR field of the bibliographic record Position 7 of the LDR field of the bibliographic record Not relevant for Dublin Core
    Bibliographic ID Taken from display.bib_id in the display section in the operational record 010 excluding numeric subfields 020 a dcterms:identifier dcterms:ISBN, dcterms:identifier dcterms:ISSN
    Network Number Taken from search. other_system_number in the search section of the operational record 035 a z 053 a z dc:identifier , dcterms:identifier
    OCLC Control Number (019) The OCLC control number

    019 a

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on 
      Not relevant for Dublin Core
    OCLC Control Number (035a) The OCLC control number

    035 a

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on
    035 a Not relevant for Dublin Core
    OCLC Control Number (035a+z) The OCLC control number

    035a+z

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on
    035a+z Not relevant for Dublin Core
    OCLC Control Number (035z) The OCLC control number

    035 z

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on
    035 z Not relevant for Dublin Core
    BIB 008 MARC The contents of the MARC 008 bibliographic field 008   Not relevant for Dublin Core
    BIB LDR MARC The contents of the MARC LDR bibliographic field LDR   Not relevant for Dublin Core
    Open Access Indicates if the article is open access Based on 506 f 506 2   Not relevant for Dublin Core
    Edition Taken from display.complete_edition in the display section of the operational record MARC 250 subfields a,b 205 a,b,f,g dcterms:isVersionOf
    Form of Item The form of the item MARC 008 pos. 29 (Maps and Visual Material) or 23 (other material configurations)   dc:format
    Government Publication The government publication type MARC 008 pos. 28   Not relevant for Dublin Core
    Language Code Taken from display.language in the display section in the operational record 008 pos. 35-37 101 a Currently comes from dc:language.  Planned to come from dc:language and dcterms:language
    Language Of Cataloging The language in which the cataloging was done 040 b 100 a,22-24 Not relevant for Dublin Core
    Series Taken from display.series_small in the display section in the operational record

    800 t

    810 t

    811 t

    830 a,n,p,v

    410 a,h,i,o,t,x Currently empty.  Planned to come from dcterms:isPartOf
    Subjects Taken from display.subjects in the display section of the operational record 65X, 69X,630,689 600 a,b 602 603-8 610 616 617 dc:subject dcterms:LCSH,MESH,DDC,UDC,LCC
    Type of Date Taken from display. type_of_date in the search section of the operational record 008 pos. 6 100 pos 8 Not relevant for Dublin Core
    Uniform Title Taken from display.uniform_title in the display section of the operational record 240 130 500 Not relevant for Dublin Core
    Uniform Resource Identifier The uniform resource identifier 856 u 856 u dc:identifier (dcterms:URI) ,dcterms:identifier (dcterms:URI)
    Uniform Resource Identifier Exists Indicates if 856 subfield u contains data      
    Resource Type Constructed based on existing bibliographic fields such as the LDR and 008. For more information, see The Resource Type Field.     dc:type
    DC License   Relevant only for Dublin Core Relevant only for Dublin Core Field does not yet exist.  It will be populated by  dcterms:license
    DC Rights   Relevant only for Dublin Core Relevant only for Dublin Core Field does not yet exist.  It will be populated by dc:rights and dcterms:rights
    The following table describes other fields in the shared dimension (taken from Alma and not MARC):
    Administrative Bibliographic Details
    Field Source in Alma (for Internal Reference)
    Collection Name The name of the collection.  This is a title level collection as defined at 'Resources > Manage Inventory > Manage Collections'.
    Collection ID The ID of the collection.  This is a title level collection as defined at 'Resources > Manage Inventory > Manage Collections'.
    Active Course Code The code of an active course.
    Active Course Name The name of an active course.
    MMS ID Stores the MMS ID of the item. This is the MMS ID of the portfolios associated with the electronic collection. It is not the MMS ID of the electronic collection or of the MMS ID of the descriptive bibliographic record added in the Additional tab of the electronic collection editor. If there are no portfolios, the value of this field is empty.
    LC Classification Top Line Stores the combined LC code and classification numbers until the first period which is followed by a letter. If there are no periods then the entire string is taken until there is a space. The length is limited to 50 characters.
    For example:
    • if the LC Classification is | a HB3821.I8 |b R3 then the LC Classification Top Line will be HB3821
    • if the LC Classification is | a DF506.5 |b .G27 then the LC Classification Top Line will be DF506.5
    • if the LC Classification is | a N 7353 |b .K513 1965 then the LC Classification Top Line will be N
    • if the LC Classification is | a NOT YET ORDERED then the LC Classification Top Line will be NOT
    The LC Classification Top Line will contain one value. For MARC21, if the bibliographic record has:
    • both 090 and 050 then the LC Classification Top Line will come from 090
    • 050 and not 090 then the LC Classification Top Line will come from 050
    • 090 and not 050 then the LC Classification Top Line will come from 090

    Regarding Dublin Core:

    Currently empty. Planned to come from:
    (dcterms:LCSH),
    dcterms:subject (determs:LCSH),
    dc:subject (dcterms:LCC),
    dcterms:subject (determs:LCC)

    Dewey Classification Stores the Dewey Classification
    Dewey Classification Top Line

    Stores the first 3 digits of the Dewey Classification

    Regarding Dublin Core:

    Currently empty.  Planned to come from dc:subject (dcterms:DDC),
    dcterms:subject (determs:DDC)  

    Chinese Classifications Stores the Chinese Classification
    Local Param 1-10 This field allows you to enrich the bibliographic and holdings information exported to Analytics with additional information from MARC fields in Alma."
    In order to make use of this field, you must contact Ex Libris Support and supply them with a three-digit MARC field code (for example, 901). (The field does not need to include a 9.)
    The fields can be number and code fields but not control fields. Therefore, the field must be greater than or equal to 010, because 00X are Control Fields and 01X-09X are Numbers and Code Fields.
    Following configuration of this field by Ex Libris Support, its value will be available in analytics.
    Subfields can be maintained in the Analytics fields identified for Local Param. When this capability is implemented, fields/subfields appear in Alma Analytics with the Alma subfield delimiter (either $$ or ‡) used to delineate the subfield content. Contact Support to enable this feature. Note that reindexing is required to fully implement this capability.
    Note that the local param fields are not related to the MARC type of the record. For example, if field 913 is defined to be in local param 1 then field 913 will always be in local param 1. This is the case if the record is of the type KORMARC, CNMARC, UNIMARC, MARC21, and so forth. It is not possible to have different sets of Local Param 1-10 for different types of MARC.
    Link ID The link ID. For more information concerning this field and the next two, see Understanding the fields Link ID Linked to CZ and Linked to NZ in the Bibliographic Details folder.
    Linked to CZ Indicates if the record is linked to the Community Zone
    Linked to NZ Indicates if the record is linked to the Network Zone
    Creator Stores the name of the user that created the record
    Creation Date Stores the creation date
    Managed by Provider Indicates if the electronic resource is managed by the provider
    Modified By Stores the user name that modified the record
    Modification Date Stores the modification date
    Peer Reviewed Indicates if the article was peer reviewed
    Provider Name The name of the provider
    Record Format The format of the bibliographic record. Examples:
    • MARC 21
    • DC
    • KORMARC
    • CNMARC
    • UNIMARC
    Suppressed from Discovery Indicates whether the record is suppressed from external discovery systems
    Bibliographic Lifecycle The Lifecycle of the item. Possible values are Deleted and In Repository. This allows you to filter reports by In Repository/Deleted items.
    Network ID This field is used by institutions implementing a Network Zone. It is the same as the MMS ID of the bibliographic record in the Network Zone and can be used to create reports that show the MMS ID in the member institution (using the existing MMS ID), as well as the corresponding MMS ID in the Network Zone.
    ISSN (Normalized) The normalized ISSN.
    ISBN (Normalized)
    The normalized ISBN.
    Brief Level The level of the brief record
    Originating System The system where the bibliographic record originated
    Originating System ID The ID of the system where the bibliographic record originated
    Originating System Version The version of the originating system

    LC Classifications

    Using this dimension, the user may drill down from Group1 to Group4. In each level, the user may see measures accumulated to the relevant group and see the number of items grouped by classification.
    The field descriptions can be found in the LC Classifications shared dimension.
    LC Classifications
    Field Description Additional information
    Start Range Stores the start range of the group such as PS501  
    End Range Stores the end range of the group such as PS689  
    Classification Code Stores the letters in the beginning of the range such as PS
    • In the Fulfillment subject area, if there is more than one classification code, the last one appears.
    • The Classification Code comes from the bibliographic record, except for in the Physical Items subject area where it comes from the holdings record.
    Start Range Number Stores the numbers that come after the letter in the start range  
    End Range Number Stores the numbers that come after the letter in the end range  
    Group1 Stores the name of the first level  
    Group2 Stores the name of the second level  
    Group3 Stores the name of the third level  
    Group4 Stores the name of the fourth level  
    Group5 Stores the name of the fifth level  
    Classifications Stores the Hierarchy column that allows the user to drill down from the first level of the classification to the fourth level. Using this column provides the user with the option to view the accumulative measures. Note that the fifth level is not included in this field.  

    Dewey Classifications

    Books can be classified with Dewey Classifications.
    In Dewey Classifications, topics are ordered in a hierarchy that is indicated by a three digit number. The highest level of the hierarchy is indicated by a number with one significant digit followed by two zeros, such as 600. The second level in the hierarchy is indicated by a number with two significant digits followed by one zero, such as 630. The third level in the hierarchy is indicated by a number with three significant digits such as 636.
    The field descriptions can be found in the Dewey Classifications shared dimension.
    Dewey Classifications
    Field Description Additional information
    Dewey Number Holds the first 3 digits of the Dewey Classification.
    The Dewey Number comes from the bibliographic record, except for in the Physical Items subject area where it comes from the holdings record.
    Group1 Stores the name of the first level.  
    Group2 Stores the name of the second level.  
    Group3 Stores the name of the third level.  
    Dewey Classifications Stores the Hierarchy column that allows the user to drill down from the first level of the Dewey Classification to the third level. Using this column provides the user with the option to view the accumulative measures (loans or returns) in each level of the hierarchy.  

    Other Classifications

    The Other Classifications table is a dimension table that contains fields for classification systems other than LC and Dewey.
    Other Classifications
    Field Description Additional Information
    Chinese Classifications
    Classification Code The Chinese Classification code with which to find a match to the Chinese Classification code from the bibliographic record.  
    Group 1-7 (Chinese) Stores the Chinese Classification Code, which comes from the bibliographic record.  
    Group 1-7 (English) Stores the name of the levels of classification  
    Chinese Classifications (Taiwan)
    Classification Code The Chinese Classification code with which to find a match to the Chinese Classification code from the bibliographic record.  
    Group 1-3 (Chinese-Taiwan) Stores the Chinese Classification Code, which comes from the bibliographic record.  
    Group 1-3 (English) Stores the name of the levels of classification  

    Institution

    The shared Institution dimension allows the Network Zone to view reports according to institution. It is available in every subject area. It contains the following fields:
    Institution
    Field Description Additional information
    Institution Code The code of the institution.  
    Institution Name The name of the institution.  
    Institution Timezone The timezone of the institution  
    Data Available As Of When the data became available to analytics  
    Data Updated As Of When the data was taken from Alma  
    If an analytics report is run from the Network Zone in a collaborative network implementing a Network Zone, all member institutions are included in the report for Institution Code and Institution Name.
    If an analytics report is run from an institution that is not part of a collaborative network implementing a Network Zone, only the single institution from which the report is run is included in the report for Institution Code and Institution Name.
    Reports involving data across a collaborative network implementing a Network Zone may take longer to run than reports within one institution.

    Shared Dimensions with Other Subject Areas

    For information concerning shared dimensions with other subject areas, see Shared Dimensions.

    Alma Link Resolver Special Services

    Open Access

    Users can enable a link resolver service for Unpaywall Open Access articles. To enable the service, set the enable_open_access_services_from_unpaywall_api customer parameter to true (see enable_open_access_services_from_unpaywall_api in Configuring Other Settings (Fulfillment).
    Where the open access information is placed can be configured in the Online Services Order configuration (Configuration Menu > Fulfillment > Discovery Interface Display Logic > Online Services Order). See the section Configuring the Order of Online Services for more information. The default placement of the open access information is at the end.
    Open access rules can be configured to specify what appears or is hidden based on open access. See Configuring Display Logic Rules for more information.
    Direct linking for open access can also be configured. See Configuring Direct Linking for more information.
    Regarding search results for Unpaywall Open Access articles, note that Alma only checks for Unpaywall full-text access when opening the full view of a record from discovery (Primo VE). If the only available full-text source for an article or resource is through Unpaywall, it will not appear in search results unless the Include results with no online full-text to request through Inter-Library Loan filter is applied.

    Additionally, if there is no response for a PDF in the Unpaywall API Response, no Unpaywall Service will be displayed.

    Link Resolver - Services for Related Records

    Configuring Related Records for Electronic Services

    This section applies only to Primo. For information on how to configure related records in Primo VE, see Configuring Related Record Services for Primo VE

    Related records indicate to the OpenURL link resolver that, when a user receives a certain record in the search results, another record should also be returned as related. Certain MARC fields, called linking entries (such as MARC fields 76X-78X), allow records to link to related bibliographic records and to differentiate their relationships to users. For a full list of MARC fields that are used as linking entries, see Modifying the Display Labels for Related Electronic Services. For additional information regarding physical resources, see Configuring Related Records for Physical Inventory.
    For electronic services, the configuration of related records are useful for the following reasons:
    • Articles sought by users may be available only in related versions of the journal.
    • Metadata in the OpenURL can be for one publication, but in fact, a related journal by another name is what the end user sought.
    • Vendors may list previous or newer versions in their holdings causing inconsistencies in the Community Zone. For example, the journal Civil Engineering Systems is now named Civil Engineering and Environmental Systems.
    In the following example, View It displays the available services for the discovered record and the host record:
    Related Records as Shown in View It
    A close relation indicates that the two records should be considered identically useful in the search results. If the record requested in the OpenURL has close relations (MARC 773 and 774) with another record, electronic services for the related record are included in View It, with no indication that these services are for the related record. To the user, it seems as if these services are for the record sent in the OpenURL. Since the relation type is very close, it can be considered equivalent; and as far as the user is concerned, no distinction needs to be made. Other types of relations are considered remote and are listed under the Services for Related Titles section in View It.

    To configure close relations to appear in the same section as the related titles in View It, see the Display closely related record services option in Enabling the Display of Related Records in Primo.

    Modifying the Display Labels for Related Electronic Services

    The DISCOVERY_INTERFACE_LABELS code table page enables you to modify the following labels in View It:
    • Title – The following code defines the label that displays above the list of related records in View It:
      c.uresolver.ServicesForRelatedTitles
    • Relationship – The label that appears for each related entry in View It and Get It. To modify a label, see the relevant relationship in the table below.
    Related Records as Shown in View It
    See the illustrations below for examples of entries in the Discovery Interface Labels table (DISCOVERY_INTERFACE_LABELS).
    Discovery Interface Labels Table - Services for Related Titles
    Discovery Interface Labels Table - Additional Form
    The following table presents the correlation between the MARC fields defined in the bibliographic record and the out-of-the-box labels that appear for each type of relation in View It. For information on modifying labels, see Configuring Service Labels in the Discovery Interface.

    The labels and information that appear in the Primo's Details section is determined by the normalization rules that are defined in Primo.

    Related Record Types
    Relation/Type MARC Field UNIMARC Field Location in Primo
    Main series entry (remote) 760 410 View It: c.uresolver.viewit.related_type_list.MAIN_SERIES = Main Series
    Indicators 0#  
    $w, $x $1 and starts with 001
    Subseries entry (remote) 762 411 View It: c.uresolver.viewit.related_type_list.SUBSERIES = Subseries
    Indicators 0#  
    $w, $x $1 and starts with 001
    Original language entry (remote) 765 454 View It: c.uresolver.viewit.related_type_list.ORIGINAL_LANGUAGE = Original Language
    Indicators 0#  
    $w, $x, $z $1 and starts with 001
    Translation entry (remote) 767 453 View It: c.uresolver.viewit.related_type_list.TRANSLATION = Translation
    Indicators 0#  
    $w, $x, $z $1 and starts with 001
    Supplement entry (remote) 770 421 View It: c.uresolver.viewit.related_type_list.SUPPLEMENT = Supplement
    Indicators 0#  
    $w, $x, $z $1 and starts with 001
    Supplement parent entry (remote) 772 422 View It: c.uresolver.viewit.related_type_list.SUPPLEMENT_PARENT = Supplement Parent
    Indicators 00  
    $w, $x, $z $1 and starts with 001
    Host item entry (close) 773 461

    View It and Get It: c.uresolver.viewit.related_type_list.PART_OF = Part Of

    Details: Display/Is Part Of (defined in Primo normalization rules

    For Primo VE, Get It does not display the type of relation after the title, and closely related items will always appear under the Locations for Related Titles section.

    Indicators 0#  
    $w, $x, $z $1 and starts with 001
    Constituent unit entry (close) 774 462-464

    View It and Get It: c.uresolver.viewit.related_type_list.CONTAINS = Contains

    For Primo VE, Get It does not display the type of relation after the title, and closely related items will always appear under the Locations for Related Titles section.

    Indicators 0#  
    $w 462 $1 and starts with 001
    463 $1 and starts with 001 
    464 $1 and starts with 001
    $x  
    $z  
    Other edition entry (remote) 775 451 View It: c.uresolver.viewit.related_type_list.OTHER_EDITION = Other Edition
    Indicators 0#  
    $w, $x, $z $1 and starts with 001
    Additional physical form entry (remote) 776 452 View It: c.uresolver.viewit.related_type_list.ADDITIONAL_FORM = Additional form
    Indicators 0#  
    $w, $x, $z $1 and starts with 001
    Issued with entry (remote) 777 423 View It: c.uresolver.viewit.related_type_list.ISSUED_WITH = Issued With
    Indicators 0#  
    $x $1 and starts with 001
    $w  
    Preceding entry (remote) 780 430
    431 
    432 
    433 
    434 
    435 
    436 
    437
    View It: c.uresolver.viewit.related_type_list.PRECEDES = Precedes

    Details: Display/Relation – Related Titles: Earlier Title (defined in Primo normalization rules)

    Indicators 00, 01, 02, 03, 04, 05, 06, 07  
    $w, $x, $z $1 and starts with 001
    Succeeding entry (remote) 785 440 
    441 
    442 
    443 
    444 
    445 
    446 
    447
    View It: c.uresolver.viewit.related_type_list.SUCCEEDS = Succeeds

    Details: Display/Relation – Related Titles : Later Title (defined in Primo normalization rules)

    Indicators 00, 01, 02, 03, 04, 05, 06, 07, 08  
    $w, $x, $z $1 and starts with 001
    Data source entry 786

    $w, $x, $z

      View It: c.uresolver.viewit.related_type_list.CONTAINS = Contains
    Other relationship entry (remote) 787 412
    413
    424
    425
    455
    456
    470
    481
    482
    488
    View It: c.uresolver.viewit.related_type_list.OTHER_RELATIONSHIP = Other Relationship
    Indicators 0#  
    $w, $x, $z $1 and starts with 001
    Series added entry-personal name 800

    $w, $x

      View It: c.uresolver.viewit.related_type_list.CONTAINS = Contains
    Details: Display/Relation – Series: (defined in Primo normalization rules)
    Series added entry-corporate name 810

    $w, $x

      View It: c.uresolver.viewit.related_type_list.CONTAINS = Contains
    Details: Display/Relation – Series: (defined in Primo normalization rules)
    Series added entry-meeting name 811

    $w, $x

      View It: c.uresolver.viewit.related_type_list.CONTAINS = Contains
    Details: Display/Relation – Series: (defined in Primo normalization rules)
    Series added entry-uniform title 830

    $w, $x

      View It: c.uresolver.viewit.related_type_list.CONTAINS = Contains
    Details: Display/Relation – Series: (defined in Primo normalization rules)
    Valid ISBN, ISSN, or other standard number (remote) 020 $a, $e 010 $a View It: c.uresolver.viewit.related_type_list.REPLACED_BY = Replaced By
    022 $a, $e 011 $a
    024 $a 013 $a, 014 $a, 015 $a, 016 $a, 017 $a, 072 $a, 073 $a
    Cancelled/invalid ISBN, ISSN, or other standard number (remote) 020 $z 010 $z View It: c.uresolver.viewit.related_type_list.REPLACES = Replaces
    022 $y, $z 011 $g, 011 $y, 011 $z
    024 $z 013 $z, 014 $z, 015 $z, 01 $z, 017 $z, 072 $z, 073 $z
    Linking ISSN (remote) 022 $l 011 $f View It: c.uresolver.viewit.related_type_list.LINKS_TO = Links To
    For more information about configuring related records, see Discovery Interface Display Logic for Related Records.

    Enabling the Display of Related Records in Primo

    To configure related records, you must have one of the following roles:
    • General System Administrator
    • Fulfillment Administrator
    The Related Record Services Configuration page enables you to configure the electronic services and physical inventory for related titles that appear in the Primo.
    To enable related record services:
    1. Open the Related Record Services Configuration page (Configuration Menu > Fulfillment > Discovery Interface Display Logic > Related Records).

      Related_Record_Services_Configuration_04.png
      Related Record Services Configuration Page
    2. For electronic inventory, refer to the following table to configure how related records display in View It. For more information, see Configuring Related Records for Electronic Services and Modifying the Display Labels for Related Electronic Services.

      Related Record Services Configuration Options – View It Section
      Parameter Description

      Enable related record services

      Select Yes if you want to display a record's related titles in View It. If enabled, the remaining fields allow you to restrict or modify the display of related titles for specific types of records.

      Display related services if full text is available

      Display services for related records if full text is available. Services for related records are not shown if there is a full-text service for the original record in the OpenURL.

      Display related services for serials

      Display related services for serials (which have a Journal material type).

      Display related services for monographs

      Include related services for monographs (which have a Book material type).

      Deduplicate electronic collection services

      Use deduplication of electronic collection services for remote related services. This causes Primo to display only one service if related records are associated with the same electronic collection.

      Enable direct link for related services

      Turn on the direct-linking feature.

      Disable Related Record Services for Digital

      Disable the display of related records for digital records.

      Display closely related record services

      How closely related services (which are defined with MARC 773 or 774 fields in the bibliographic record) should appear in View It:

      • As part of the original services – Closely related services are placed in the list of regular services in View It with no indication that these services are for related titles.

      • Separately from the original record services – Closely related services are placed under the Services for Related Titles section in View It.

    3. For physical inventory, refer to the following table to configure how related records display in Get It. For additional information, see Configuring Related Records for Physical Inventory.

      Related Record Services Configuration Options – Get It Section
      Parameter Description

      Enable related record services

      Select Yes if you want to display a record's related titles in Get It. If enabled, the remaining fields allow you to restrict or modify the display of related titles for specific types of records.

      Display related holdings for serials

      Select this option to display the related holdings records for serials.

      Display related holdings for monographs

      Select this option to display the related holdings records for monographs.

      Note that for monographs, related inventory appearing in Get It is considered when fulfilling title-level requests placed by the patron. If you disable the display of related records for monographs, the related records’ inventory that isn’t displayed is not considered when fulfilling title-level requests.

      Display closely related records holdings

      Select one of the following options to indicate how you want the closely related records (which are defined with MARC 773 or 774 fields in the bibliographic record) to appear in Get It:

      • As part of the original holdings – Closely related records are placed in the list with the original holdings in Get It with an indication that these are related holdings, including title and relation type.

      • Separately from the original record holdings – Closely related records are placed under the Locations for Related Titles section in Get It. See c.uresolver.getit2.display_related_holding_separately_from_original_record in the table above for more information.

      For Primo VE, related records are displayed separately, regardless of this setting.

    4. Select Save.