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

    访问服务

    链接程序(目标解析器)

    参考Alma和SFX下的文档,其中提供用于启用全文链接的链接参数的详细内容。

    显示条件规则

    可译的

    Alma链接解析器(和Primo查看)支持决定电子资源库对终端用户显示的条件的规则。在共享区知识库中定义显示条件规则,且包含例如传入OpenURL包含文章级别元数据元素的要求。条件规则对于报纸电子资源库和例如CCC Get It Now的电子资源库可用。

    在激活或编辑电子资源库之后,您可以查看显示的条件信息和规则。请注意,不能编辑或本地创建显示条件规则。要查看该信息,在电子服务编辑器页面选择链接选项卡;在可用性规则旁,选择服务显示条件规则链接(报纸电子资源库)或服务过滤条件规则链接(CCC Get It Now电子资源库)。

    Service_Display_Condition_Rules_Link_02.png

    服务显示条件规则链接

    Electronic service editor - Service filter condition rules.png

    服务过滤条件规则链接

    这打开服务显示条件规则页面(报纸电子资源库)或服务过滤条件规则链接(CCC Get It Now电子资源库)。

    Service display condition rule.png

    报纸电子资源库的服务显示条件规则

    Service filter condition rules.png

    CCC Get It Now电子资源库的服务过滤条件规则页面

    默认情况下,在规则名称列的规则之间使用OR逻辑。这意味着当满足这些例子中的任意规则时,使用Alma链接解析器或Primo获取时显示报纸电子资源库或CCC Get It Now电子资源库。如果所有规则都不满足,则Alma链接解析器或Primo查看不显示这些电子资源库。

    要查看每条规则的详情,在规则名称栏选项规则编号链接。有关这些规则的示例见下文。

    Rule_Details_Example_for_a_Newspaper_Electronic_Collection_02.png

    报纸电子资源库的规则详情示例

    Rule_Details_Example_for_a_CCC_Get_It_Now_Electronic_Collection_02.png

    CCC Get It Now 电子资源库的规则详情示例

    为电子资源库和资源库列表配置动态URL

    可译的
    要处理电子资源,您必须具有以下角色:
    • 电子馆藏操作员
    • 电子馆藏操作员扩展(删除操作所需)
    • 仓储经理
    除了为本地电子资源库和资源库列表管理静态链接,您可以为本地电子资源库和资源库列表创建复杂的动态URL,并动态嵌入OpenURL元数据信息。此外,您还可以使用动态URL来覆盖共享区知识库提供的链接。
    电子服务编辑器和电子资源库列表编辑器页面使您能够分别定义用于为服务或资源库列表选择链接URL的条件列表。
    Dynamic_URL_Linking_Information_Conditions_Example_NewUI_06_TC.png
    动态URL链接信息条件示例
    使用动态URL时,每个条件都必须从一个IF语句开始,用于检查ContextObject和OpenURL参数的存在。如果对于从列表顶部开始的条件存在所有参数,则该条件的指定URL用于链接。否则,将检查下一个条件。要抓取内容(如果所有其他检查失败,用于匹配),使用IF () <url>
    例如:
    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
    如果在上述示例中满足第一个条件,则生成的动态URL可能如下所示:
    http://www.publisher.com/1364-0321/2010/2
    除了rft.year,您还可以使用rft.monthrft.dayrft.date属性。
    测试动态URL语法可以验证您的条件语法。
    有关为电子资源库配置动态URL的详细信息,见电子资源库的动态URL视频(2:33分钟)。

    有关更多信息,见URL模板的常用OpenURL属性

    URL功能

    此外,动态URL可以包括以下功能来操纵指定参数中返回的值:
    • SUBSTR(字符串,起始位置,长度) - 根据字符串的起始位置和长度,返回指定字符串的子字符串。如果{rft.date}包含2010-08-01,并且从字符串开头指定前四个字符,如下所示:
      http://www.publisher.com/{rft.issn}/SUBSTR({rft.date},0,4)
      Alma使用下列URL:
      http://www.publisher.com/1824-6321/2010
    • REPLACE(字符串,检索,替换) - 根据检索和替换文本替换指定字符串中的文本。如果{rft.isbn}包含破折号(例如,978-1-285-13563-2),并且未指定替换文本,如下所示:
      IF (rtf.isbn)
      http://www.publisher.com/REPLACE({rft.isbn},-,"")
      Alma使用下列URL:
      http://www.publisher.com/9781285135632

    要替换特殊字符,请使用替换字符串的编码值。

    例如:

    REPLACE({rft.isbn},%3F,"")

    而不是

    REPLACE({rft.isbn},?,"")

    • URLENCODE(字符串) - 在指定的字符串中编码特殊字符。如果{rft.atitle}包含题名The Grapes of Wrath,并且请求编码,如下所示:
      http://www.publisher.com/URLENCODE({rft.atitle})
      Alma使用下列URL:
      http://www.publisher.com/The%20Grapes%20of%20Wrath
    电子资源库激活后可以发布至Primo。例外的是数据库类型的电子资源库,一旦它们被URL和未屏蔽的相关书目记录定义后就可以被发布。
    您可以将资源库列表定义为独立实体或电子资源库的一部分。 添加本地电子资源库中提供了添加电子资源库及其相关资源库列表的步骤。在管理本地资源库列表中提供了添加独立于添加电子资源库的资源库列表的过程。

    解析器代理

    可译的
    为了设置网络挂接定义文档, 你必须是:
    • 通用系统管理员
    要使校外用户能够访问不同供应商站点的全文服务,您必须定义代理服务器,用于对这些用户进行身份验证。

    Alma链接解析器响应传入的OpenURL,并通过自动在解析的URL中包含其他代理信息将其更改为电子链接。一些机构使用单个代理服务器,在这种情况下应定义一个代理配置文件如果机构使用多个代理服务器,则应为每个代理服务器定义代理配置文件。然后,您必须为每个电子资源库、服务或资源库列表定义相关代理。

    通过网络区分发电子资源的访问到成员时,代理必须要在机构区而不是网络区中管理。机构区代理会覆盖网络区资源库中定义的任何代理。

    见以下其他代理信息:

    代理关系

    下表介绍电子资源库、服务和资源库列表的代理启用设置之间的关系。资源库列表从其所连接的服务级别继承启用代理的设置。因此,仅在您希望与服务级别设置不同时设置资源库列表级别的代理启用设置(这种情况下,您需要将服务级别的所选代理字段留空)。启用的电子资源库代理设置不会由资源库列表继承。
    代理关系
    代理启用电子资源库级别 服务级别启用的代理 资源库列表级别启用的代理 启用的代理设置结果
    N N N 重定向到资源
    N N Y 重定向到代理登录
    N Y N 重定向到代理登录
    资源库列表继承服务设置
    N Y Y
    电子资源库不继承服务或资源库列表的代理设置。如果在服务级别选择代理配置文件,资源库列表继承服务级别的代理设置。要设置资源库列表级别的代理,将服务级别设置的所选代理字段留空。
    Y N N 重定向到资源
    电子资源库代理不会由服务或资源库列表级别继承
    Y N Y 重定向到代理登录
    Y Y N 重定向到代理登录
    资源库列表继承服务设置
    Y Y Y 重定向到代理登录
    • 要对资源库列表应用‘组设置’代理,代理需要在电子服务的‘组设置’选项卡中应用。
    • 要对电子资源库应用‘组设置’代理,代理需要在电子资源库编辑器的‘组设置’选项卡中应用。

    配置代理

    要配置解析器代理类型的集成配置文件:
    1. 在集成配置文件列表页面(配置菜单 > 通用 > 外部系统 > 集成配置文件),点击添加集成文件。显示集成配置文件向导的第一页。

    2. 集成类型选择解析器代理

    3. 输入要定义的配置文件的名称(代码),并可选择输入描述。

    4. 如果要将要定义的配置文件设置为默认代理定义配置文件,选择默认。(如果您以前将另一个配置文件定义为默认配置文件,在该配置文件中选择默认之前,清除其他配置文件中的默认选项)。如果代理设置为默认,并且操作(见下文)设置为始终,则此代理用于解析任何资源,即使资源没有设置ProxyEnabled=Yes

    5. 选择下一步。显示向导第二页。

      Resolver_Proxy_Integration_Profile_2.png

      解析器代理集成配置文件 – 步骤 2(代理定义)
    6. 选择要为该配置文件配置的代理服务器类型。

      没有选项可以输入多个IP地址。“代理IP”字段应保存代理服务器IP地址而不是允许的IP范围。以防OpenUrl请求来自该IP地址,代理不会添加到目标URL,这会防止循环。

      以下选项可用:

      • Biblio-Pam - 该服务器代理使用以下URL结构:

        结构的<Biblio-PAM URL>部分为来自Biblio-PAM的供应商提供的URL。

        <shortened target URL>为不含有http://https://的目标URL。

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

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

      • EZProxy - 该选项使用以下URL结构,其中$@为目标URL的占位符:
        • https://www.ezproxy.unibo.it/login?
        有关更多信息,见EZProxy URL数据库
      • HAN - 该选项使用以下URL结构:
        • http://<HAN server>/hanapi/?hash=<HASH>
        Proxy url参数输入http://<HAN server>部分。
        URL结构剩余的部分由Alma组建,并与在Proxy url参数中输入的部分结合。
        对于HAN代理服务器类型,您需要输入Salt参数。 Salt参数为可以含有任意字母数字值的自由文本字段。输入的值必须与您的HAN账户中的HAN代理服务器配置中的salt值匹配。在您的HAN账户中创建HAN salt值时,复制到Alma中的Salt值。
      • LIBProxy

      • OpenAthens Redirector - 该选项使用以下URL结构:
        • https://<OpenAthens Redirector URL>?url=<encoded target URL>
        结构的<OpenAthens Redirector URL>部分为来自OpenAthens的供应商提供的URL。
        Proxy url参数输入https://go.openathens.net/redirector/<your domain>
        URL的?url=部分由Alma添加。
        <encoded target URL>为编码表中的目标URL。
        请注意,即使Redirector不是代理服务器,可以使用Alma代理服务器配置。
      • WAM
        请注意,您应该忽略代理URL开头的0-
      • RemoteXS
        使用RemoteXS代理的机构能够配置Alma的链接解析器以与该代理无缝集成。
    7. 输入由供应商提供的代理URL(包括http://或https://))和代理IP地址。

    8. 使用代理选择以下值:

      • 始终 – 代理用于任何解析。

        如果选择此代理作为默认值,它将用于任何解析,即使资源(服务、资源库或资源库列表)设置为EnableProxy=No

        如果此代理未被选择为默认值,则用于设置为EnableProxy=Yes且选择了此代理的资源。

        该设置覆盖网络区的设置。
      • 从不 – 即使为特定资源启用并选择了此代理,也不会用于解析。

      • 选择性 – 此代理用于设置为EnableProxy=Yes且选择了此代理(这相当于为非默认代理选择始终)的资源。

        即使选择此代理作为默认值,也必须明确添加到资源。

    9. 选择保存。配置文件已保存。

    可译的
    Translatable

     

    Configuring General Electronic Services

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

    • General System Administrator

    • Fulfillment Administrator

    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 the View It, Get It, and How to Get It sections on the record's full display page. Services that allow users to access or purchase the materials are considered delivery-related and will appear in the View It, Get It, and How to Get It sections on the record's full display page.

    To have these services appear in Leganto, see Enabling General Electronic Services in Leganto.

    AlmaP_GES_Example_newUI.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 add a general electronic service:

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

    1. Open the General Electronic Services Configuration page (Configuration Menu > Fulfillment > Discovery Interface Display Logic > General Electronic Services).

      GES_NewUI.png

      General Electronic Services List (Alma-Primo)
      • The Item Level column is hidden by default; you can add it to the table by selecting the Manage Column Display icon above the table.

      • The Is this a Document Delivery/ILL Service column is available only with Primo VE and Alma-Summon environments.

    2. Select Add Service. The Add Service dialog box opens.

      Alma Summon/Primo VE Add Service dialog box

      Add Service Dialog Box

      Unless otherwise noted, all fields are supported in the following environments: Alma-Primo, Primo VE, and Alma-Summon.

    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 How To GetIt.

      • Is this a Document Delivery/ILL service – Select Yes to indicate that this service is delivery-related and provides access to the resource. Select No to indicate that this service is not delivery-related and will appear under the Links section.

        This field is not available with Alma-Primo environments.

      • Display Location – Specify the section on a record's full display to which you want to display the GES link. The following table lists the available options per customer environment:

        The Display Location is only displayed if Is this a Document Delivery/ILL service is selected Yes.
        The Display Location is not displayed if Is this a Document Delivery/ILL service is selected No.
        Alma-Primo Primo VE and Alma-Summon
        • Getit
        • Viewit
        • Getit & Viewit
        • None – Services appear under the Links section in the record's full display.
        • Getit & How to Getit
        • Viewit & How to Getit
        • Getit, viewitand How to Getit
        • None – Services appear under the Links section in the record's full display.

        The How to Get It section displays only when a record has no inventory. Typically, the How to Get It section is used for resource sharing and relevant ILL service links.

        • For Primo VE and Alma-Summon only, this field appears only when the Is this a Document Delivery/ILL Service field is set to Yes.

        • 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 – 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.

        • This option displays only when the value of the Display Location field includes GetIt.
        • 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.

        • storage_location_id

        • item_call_number 

      • 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 value 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 following table describes general categories by which the OpenURL attributes returned from Alma’s link resolver are grouped.

    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.
    Any attributes returned by the link resolver, that do not belong to any of the 4 categories above, are unused; they should not be selected when creating an input parameter for a Service Availability Rule. For additional information about OpenURL attribute categories see the related knowledge article.
    The following are commonly returned attributes that can be used to create service availability rules. Some of these attributes are taken from the MARC 21 fields of the relevant records. For these attributes, the MARC 21 sources appear in the MARC 21 Fields column. Attributes that are not taken from MARC 21 fields are retrieved from various other sources, including CDI records, Primo, OpenURL, and other external sources.
    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 030 a 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
    • document
    • dissertation
    • journal
    • patent
    • audio
    • series
    • score
    • video
    • videorecording
    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 physical; 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.lccn addata/lccn 010 a,z Library of Congress control number
    rft.mms_id     MMS ID of the item
    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 Services

    When the General Electronic Service is added as an item-level service, you can configure the URL template to include 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
    Storage Location ID storage_location_id
    Item Call Number item_call_number

    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}.

    Allow any Field from the Bibliographic Record to be Used when Defining a General Electronic Service

    The "General Electronic Service Bib Fields Enrichment" configuration screen (Configuration > Fulfillment > Discovery Interface Display Logic) enables institutions to define which field will be extracted from the record's metadata and be available for use when defining an "Availability Rule" or enhancing the "URL template" field upon definition of a "General Electronic Service" (Configuration > Fulfillment > Discovery Interface Display Logic > General Electronic Services).

    Below is an example workflow:

    1. Access the new configuration screen and add a new row to point to the specific bibliographic field (020_a in the example).

    Define the Bib field.

    Define the Bib Field

    2. You can find the newly defined bibliographic field in the input parameters section of a rule.

    Define GES Rule.

    Define GES Rule

    3. You can also utilize the newly defined field in the URL Template field of the general electronic service.

    Add New Name to URL Template.

    Add New Name to URL Template

    4. Below is an example of how this will appear to patrons in the Discovery (Primo) system, as well as how the actual URL will be constructed.

    GES in Search Results.

    Constructed URL

    When adding a row to the "General Electronic Service Bib Fields Enrichment" configuration screen, you need to define the Record format, Bibliographic field and subfield. The defined value within the "Field Name in General Electronic Service" will be the one that appears when defining the General Electronic Rule/URL template.

     

    1. When 2 bibliographic records are matched, the logic will only apply on the "Selected" bibliographic record.

    2. In case the URL template field starts with a parameter place holder with no text or URL before it (and regardless of what comes after it), no decoding will be done
        to the first parameter's information.
     

    3. For Network Zone members, General Electronic Services that use values from the "General Electronic Service Bib Fields Enrichment" page, it is recommended to 
        use the same names as in the network zone. This is in order to display the General Electronic Service for institution or network zone resources. 

    For more information, see General Electronic Services.

    Sharing General Electronic Services in the Community Zone 

    To share and copy shared General Electronic Services, you must have one of the following roles:

    • Fulfillment Administrator
    • General System Administrator

    Institutions spend many hours creating general electronic services. In order for these institutions to save time and effort, librarians can contribute their general electronic services to the Community Zone and copy and use the general electronic services that other institutions contributed to the Community Zone. Once the general electronic service has been copied to the institution, the institution can make changes to it in order to customize it for its needs. 

    When a general electronic service is contributed, all its related rules are contributed as well.

    Contributed general electronic services appear in the Community tab on the General Electronic Services page (Alma Configuration > Fulfillment > Discovery Interface Display Logic > General Electronic Services). Copied general electronic services appear in the Institution tab. 

    The general electronic services set by the network institution also appear in the Institution tab. To distribute the general electronic service to consortia members, the Distribute Fulfillment Network Configuration job is used (see Configuring Fulfillment Information in the Network Zone). This is since these general electronic services are managed by the network institution and therefore, cannot be edited or contributed by the member institution. 

    To contribute general electronic services to the Community Zone:
    1. From the row actions, select Contribute for a general electronic service on the Institution tab of the General Electronic Services page (Alma Configuration > Fulfillment > Discovery Interface Display Logic > General Electronic Services).

      General electronic services page.jpg

      A confirmation message appears.

      confirm message for sharing GES.jpg

    2. You can optionally change the Service Code and Service Name.
    3. It is recommended that you change the Description to include detailed information for institutions that will copy the GES. 
    4. You can optionally enter or change the name and email address for the Contact person.
    5. Select Confirm. The service appears in the Community tab and can be copied by any institution.

    In case the general electronic service has been already contributed by the institution to the CZ, you may also edit and re-contribute an edited general electronic service. The latest general electronic service overwrites the previous general electronic service. This action has no effect on local copies of the general electronic services used by other institutions. 

    To view contributed general electronic services and/or copy a contributed services:
    1. Open the Community tab on the General Electronic Services page (Alma Configuration > Fulfillment > Discovery Interface Display Logic > General Electronic Services).

      To view more information about the general electronic services, from the row actions, select View. The profile details appear.

    2. Select Copy in the row actions list of the general electronic service. The general electronic service is copied to your institution and the new general electronic service is opened for editing. The general electronic service is copied and Its status is Inactive by default.
    3. Edit the general electronic service details to match your requirements.
    4. When you are done, select Save.
    5. Select the Institution tab to view the general electronic service that you copied.
    To remove (unshare) a general electronic service you contributed from the Community Zone:
    • Select Delete in the row actions list of the general electronic service and select Confirm in the confirmation dialog box.

      The general electronic service is no longer available to other institutions. However, it is not deleted; you can continue using it in the Institution tab. Also, if another institution already copied this general electronic service, the deletion of your general electronic service has no effect on their local copy.

    Configuring the Order of General Electronic Services

    To configure the order of general electronic services, you must have one of the following roles:
    • General System Administrator
    • Fulfillment Administrator

    With the General Electronic Services Order page, you can configure the order in which general electronic services appear in Primo. Like other services, you can also assign services to appear in the first or last group in the list.

    You can only configure the order of general electronic services at the institution level. Select the required institution from the Configuring filter on the Fulfillment Configuration page.

    General electronic services page.jpg

    General Electronic Services Order Page

    This page does not have a Save button. Every selection made here is saved in Alma automatically. 

    To configure the display order of general electronic services:
    1. Open the General Electronic Services Order page (Configuration Menu > Fulfillment > Discovery Interface Display Logic > General Electronic Services Order). 

    2. Select Add to top or Add to last services to configure the order of services at the top and bottom of the list of results, respectively.
      PVE_DefineOrderForService.png

    3. In the Service type field, select General Electronic Service.

    4. In the Service name field, select Service.

    5. In the Service value field, select a service value.

    6. Depending on which list you are defining, select either Add to topAdd to last services. The service appears in the list that you are defining.

    7. For each list, select the arrows in the Move Up and Move Down columns to order the services.

    可译的

    消息自定义 

    当没有全文服务对OpenURL请求可用时,电子服务页面显示一条消息。管理员可以自定义消息的措辞。

    该配置适用于Alma-Primo环境,不适用于Primo VE。

    要自定义‘无全文’消息的措辞:

    1. 打开发现界面标签代码表(配置菜单>发现界面显示逻辑>标签)。
    2. 代码列中找到c.uresolver.emptyList
    3. 选择自定义。此行的描述列将出现,供您输入自定义的消息文本。
    4. 当没有全文可用时,输入要显示在电子服务页面上的文本。

      如果您希望没有全文可用时不显示任何消息,请将此选项留空。

    5. 选择保存
    可译的

    故障排除 - 使用OpenURL链接解析器调试工具

    您可以使用调试工具来分析OpenURL链接解析器提供的上下文服务。
    该工具使您可以获取以下信息:
    • 确定服务计算:
      • 查看基于OpenURL解析器,扩充和相关服务计算的上下文对象。
      • 了解上下文服务对象的生成方式:
        • 什么是潜在的服务?
        • 根据相关服务的计算增加了哪些服务?
        • 哪些服务根据常规电子服务和显示逻辑的覆盖范围或规则进行过滤?
    • 确定链接解析率以及OpenURL的生成方式:
      • 使用哪个目标解析器?
      • 是否使用代理?
      • 它是资源库列表级别的静态URL吗?
      • 有直接链接吗?
      • 查看生成的targetURL。
    • 在提供的调试内容中查看原始OpenURL。
    • 使用在匹配前处理的DOI完善来自CrossRef的数据(上下文对象)。

    • 有关调试引文的uRosolver(OpenURL)链接的信息,见调试引文uResolver链接

    要调试OpenURL:
    1. 在仓储中检索要测试访问权限的电子题名或资源库列表。

      对于Primo VE环境,您也可以使用Primo VE检索和显示完整的电子记录。跳转到Primo VE部分的步骤ii

    2. 根据您的Primo环境类型,执行以下步骤:

      • Alma-Primo

        1. 根据结果类型,点击列表中的单册的查看(电子题名)或测试访问(电子资源库列表)。您还可以从资源库列表清单页面和电子服务编辑器页面的资源库列表选项卡测试访问。

          Alma-Primo_ViewIT.png

        2. 在查看选项卡中,点击在新窗口显示
          Primo_DisplayInNewWindow.png

        3. 右键点击电子服务页面上的框架,然后选择查看页面来源或框架源的选项。每个浏览器的选项有所不同。

          Select_View_Page_Source_Option_NewUI_02.png

          选择查看页面源选项
        4. 找到来源视图顶部的DEBUG部分。选择并复制URL。

          HighlightCopyDebug_URL.png

        5. 打开新的浏览器页面或选项卡,粘贴从地址栏复制的调试URL,然后按回车键查看XML调试器输出。

      • Primo VE
        要调试,您需要启用显示CTO按钮,这在常规情况下隐藏。选择该按钮显示文本对象(CTO),提供结果的更多信息,帮助您处理OpenURL链接解析器提供的文本服务中的问题。

        1. 对于结果列表中的记录,点击在发现系统显示打开完整显示。

          PVE_DisplayInDiscovery.png

        2. 要启用显示CTO按钮,添加以下参数到记录的完整显示URL的末尾然后按回车&displayCTO=true

          例如:

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

          PVE_DisplayCTO_Button.png

        3. 点击显示CTO显示XML调试器输出。

    3. 滚动浏览XML以分析/调试检索结果问题。

    XML输出

    XML输出含有两个元素:

    • <context object>元素 - 含有OpenURL对象的元数据信息。该元素是所有元数据信息的容易,例如ISSN、题名、出版日期等。该元数据由Alma作为OpenURL分析的一部分而收集。
    • <context services>元素 - 含有关于服务类型、解析、代理、目标URL等的信息。Alma计算与OpenURL相关的这些服务。该服务也含有target_url。

    这是XML调试器输出的示例:

    <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>

            Note: to get the <target_url> result in Primo VE, it's not sufficient to use         showCTO=true.您必须打开CTO,找到“传入URL”并添加debug=true&svc_dat=CTO到其中(要使目标URL显示,需要debug=true)。 

          <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>

    分析/调试检索结果问题

    调试器提供关于处理OpenURL、服务计算的信息,也提供用于链接题名而创建的target_url。

    通过<context services>元素,可以看到Alma计算的与该OpenURL相关的所有服务。这通过以下方式有所帮助:

    • target_url密钥显示由Alma生成的链接。这可以帮助您查看Alma创建的URL是否有问题,或者供应商侧是否有问题。该链接含有可以帮助您调试部分问题的信息。
    • 您也可以更好地了解链接器服务页面。例如,如果希望显示特定服务,但是没有显示,检查以下内容:
      • 覆盖范围信息。服务可能不符合覆盖范围信息。例如,您可能希望看到卷1第1期,但是图书馆值采购了卷2。因此,Alma过滤掉了该服务。
      • ISBN/ISSN编号。链接可能需要ISBN。您的引文可能有ISSN。因此,Alma的链接不显示。
      • 显示逻辑规则。服务也有可能由于定义的显示逻辑规则而过滤掉。

    请注意,记录从结果中显示过滤出来的地方,XML输出包含过滤器(true或false)和过滤原因的密钥ID。例如,如果过滤器原因参数包含日期过滤器,并且OpenURL输入指定了year=2010的数据参数,则可能表示该记录已被过滤,因为该范围超出了指定的日期范围。

    链接解析器使用分析报告

    有关Alma分析中可用于创建链接解析器使用分析报告的字段,见链接解析器使用。有关Alma分析的通用信息,见分析

    Alma链接解析器特殊服务

    开放获取

    用户可以对Unpaywall Open Access文章启用链接解析服务:
    • 要启用该服务,设置 enable_open_access_services_from_unpaywall_api客户参数为true(见配置其他设置(读者服务)中的enable_open_access_services_from_unpaywall_api)。
    • 开发获取信息提交的位置可以在在线服务顺序配置(配置菜单 > 读者服务 > 发现界面显示逻辑 > 在线服务顺序)中配置。有关更多信息,见配置在线服务的顺序。开发获取信息的默认位置在末端。
    • 可以配置开放获取规则指定哪些显示或隐藏。见配置显示逻辑规则
    • 也可以配置开放获取的直接链接。见配置直接链接
    • 对于免费的开放获取文章的检索结果,请注意,Alma只在从发现系统(Primo VE)打开记录的完整视图时检查免费全文访问。如果文章或资源的唯一可用全文资源免费,则不会显示在检索结果中(除非应用了包含没有通过馆际互借的在线全文结果过滤器)。
    • 此外,如果在Unpaywall API响应中没有PDF响应,不会显示Unpaywall Service。
    • Unpaywall服务根据在API请求中发送的电子邮件限制呼叫。如果没有定义机构电子邮件,创建机构特定的通用无效电子邮件并包含在API中。转至配置 > 通用 > 添加图书馆或编辑图书馆信息 > 联系信息
    • 添加指示用于认证CDI链接中使用的OA链接没有代理。Alma认证由CDI返回的链接中没有对OA链接使用代理。这在客户设置了代理但是不想对OA链接使用时特别有用。

      要认证未使用代理,添加OA指示。指示应用于以下由CDI返回的链接:
      • linktorsc(常规‘记录中的链接’链接)
      • linktorsradditional(所有链接)
      • linktopdf(快速链接)
      • linktohtml(快速链接)
    CDI对linktorsc /linktorsradditional部分中的每个OA链接提供以下信息:
    <links>
    <linktorsradditional>$$U<link>$$G<Provider>$$H<OA></linktorsradditional>
    <linktorsradditional>$$U<link>$$G<Provider>$$H<OA></linktorsradditional>
    <linktorscr>$$U<link>$$G<Provider>$$H<OA></linktorscr>
    </links>
    对OA链接,$$H含有字符串"free_for_read"指示如果未检测到OA链接,$$H留空或不存在。如果链接包含"free_for_read"指示,这会在决定是否前置代理URL时纳入考虑范围。
    例如:
    <linktorscr>$$Uhttps://www.doaj.org/ABC/123.pdf$$EPDF$$P1$$GDOAJ$$Hfree_for_read</linktorscr>
    <linktorscradditional>$$Uhttps://www.doaj.org/ABC/123.pdf$$EPDF$$P1$$GDOAJ$$Hfree_for_read</linktorscradditional>
    <linktorsrcadditional>$$Uhttp://api.digitalnz.org/records/43...n_$$GDigitalNZ$$Hfree_to_read</linktorsrcadditional>
    <linktohtml>$$Uhttps://www.proquest.com/docview/18...P50$$Gproquest$$Hfree_for_read</linktohtml>
    <linktopdf>$$Uhttps://www.sciencedirect.com/scien...hub$$GElsevier$$Hfree_for_read</linktopdf>

    链接解析器 - 相关记录的服务

    配置电子服务的相关记录

    该部分仅对Primo适用。有关如何在Primo VE和中配置相关记录的信息,见配置Primo VE的相关记录服务

    相关记录指向OpenURL链接解析器,当用户在搜索结果中接收某个记录时,还应返回相关记录。特定MARC字段,称为链接条目(例如MARC字段76X-78X),允许记录链接到相关书目记录以及对用户区分它们的关系。对于用于链接条目的MARC字段的完整列表,见修改相关电子服务的显示标签。有关纸本资源的更多信息,见配置纸本馆藏的相关记录
    对于电子服务,相关记录的配置是有用的,原因如下:
    • 用户寻求的文章只能在相关版本的期刊上提供。
    • OpenURL中的元数据可以用于一个发布,但实际上,另一个名字的相关期刊才是是终端用户寻求的。
    • 供应商可能在馆藏中列出之前的或更新的版本,导致共享区不一致。例如,期刊Civil Engineering Systems现在名为Civil Engineering and Environmental Systems
    下例中,查看显示已发现记录和相关记录的可用服务:
    ViewIt_Img1.png
    相关记录如查看中所示
    密切关系表明,这两条记录在搜索结果中应该被认为是相同的。如果OpenURL要求的记录与另一个记录有密切关系(MARC 773和774),则相关记录的电子服务包含在查看中,但并不指明这些服务是相关记录。对于用户来说,似乎这些服务用于在OpenURL中发送的记录。由于关系类型非常接近,可以认为是等价的;就用户而言,不需要区分。其他类型的关系被认为较远,并列在查看的相关标题服务部分。

    要在查看中配置与相关标题相同的部分中配置关联关系,见启用Primo中相关记录显示中的显示密切相关的记录服务选项。

     如果有773$g过滤器且相应单册字段字段为空,单册满足过滤条件。

    修改相关电子服务的显示标签

    发现界面标签代码表(配置 > 读者服务 > 发现界面显示逻辑 > 标签)使您可以自定义和翻译查看中的以下标签:
    • 题名 - 在查看中相关记录列表上方显示的标签:
    • 关系 - 在查看和获取中显示每个相关条目的标签。要修改标签,见下表中的相关关系。
    ViewIt_Img2.png
    相关记录如查看中所示
    对于上述示例,您可以通过修改发现显示标签代码表中的以下代码的描述字段自定义题名和关系的标签:
    发现界面标签代码表
    代码 描述
    c.uresolver.ServicesForRelatedTitles 适用于相关题名的服务
    c.uresolver.viewit.related_type_list.PRECEDES 先于

    下表显示了在查看中为每种类型的关系出现的书目记录中定义的MARC字段和出厂标签之间的相关性。有关修改标签的信息,见配置发现界面中的服务标签

    Primo详情部分显示的标签和信息由Primo中定义的规范化规则确定。

    相关记录类型
    关联/类型 MARC字段 UNIMARC字段 在Primo的位置
    主系列条目(远程) 760 410 查看:c.uresolver.viewit.related_type_list.MAIN_SERIES = Main Series
    指示符 0#  
    $w, $x $1且从001开始
    子系列条目(远程) 762 411 查看:c.uresolver.viewit.related_type_list.SUBSERIES = Subseries
    指示符 0#  
    $w, $x $1且从001开始
    原始语言条目(远程) 765 454 查看:c.uresolver.viewit.related_type_list.ORIGINAL_LANGUAGE = Original Language
    指示符 0#  
    $w, $x, $z $1且从001开始
    翻译条目(远程) 767 453 查看:c.uresolver.viewit.related_type_list.TRANSLATION = Translation
    指示符 0#  
    $w, $x, $z $1且从001开始
    补充条目(远程) 770 421 查看:c.uresolver.viewit.related_type_list.SUPPLEMENT = Supplement
    指示符 0#  
    $w, $x, $z $1且从001开始
    补充父条目(远程) 772 422 查看:c.uresolver.viewit.related_type_list.SUPPLEMENT_PARENT = Supplement Parent
    指示符 00  
    $w, $x, $z $1且从001开始
    馆藏单册条目(关闭) 773 461

    查看获取:c.uresolver.viewit.related_type_list.PART_OF = Part Of

    详情:显示/是部分(在Primo规范化规则中定义)

    对于Primo VE,获取不在题名后显示关系类型,密切关联的单册总会显示在相关题名位置部分中。

    指示符 0#  
    $w, $x, $z $1且从001开始
    组成单位条目(关闭) 774 462-464

    查看获取:c.uresolver.viewit.related_type_list.CONTAINS = Contains

    对于Primo VE,获取不在题名后显示关系类型,密切关联的单册总会显示在相关题名位置部分中。

    指示符 0#  
    $w 462 $1且从001开始
    463 $1且从001开始
    464 $1且从001开始
    $x  
    $z  
    其他版本条目(远程) 775 451 查看:c.uresolver.viewit.related_type_list.OTHER_EDITION = Other Edition
    指示符 0#  
    $w, $x, $z $1且从001开始
    其他纸本表单条目(远程) 776 452 查看:c.uresolver.viewit.related_type_list.ADDITIONAL_FORM = Additional form
    指示符 0#  
    $w, $x, $z $1且从001开始
    有条目的发行(远程) 777 423 查看:c.uresolver.viewit.related_type_list.ISSUED_WITH = Issued With
    指示符 0#  
    $x $1且从001开始
    $w  
    上一条目(远程) 780 430
    431 
    432 
    433 
    434 
    435 
    436 
    437
    查看:c.uresolver.viewit.related_type_list.PRECEDES = Precedes

    详情:显示/关系 - 相关题名:较早的题名(在Primo规范化规则中定义)

    指示符 00, 01, 02, 03, 04, 05, 06, 07  
    $w, $x, $z $1且从001开始
    下一条目 (远程) 785 440 
    441 
    442 
    443 
    444 
    445 
    446 
    447
    查看:c.uresolver.viewit.related_type_list.SUCCEEDS = Succeeds

    详情:显示/关系 - 相关题名:之后的题名(在Primo规范化规则中定义)

    指示符 00, 01, 02, 03, 04, 05, 06, 07, 08  
    $w, $x, $z $1且从001开始
    数据源条目 786

    $w, $x, $z

      查看:c.uresolver.viewit.related_type_list.CONTAINS = Contains
    其他关系条目(远程) 787 412
    413
    424
    425
    455
    456
    470
    481
    482
    488
    查看:c.uresolver.viewit.related_type_list.OTHER_RELATIONSHIP = Other Relationship
    指示符 0#  
    $w, $x, $z $1且从001开始
    添加条目个人名称的连续出版物 800

    $w, $x

      查看:c.uresolver.viewit.related_type_list.CONTAINS = Contains
    详情:显示/关联 – 连续出版物:(在Primo规范化规则中定义)
    添加条目团体名称的连续出版物 810

    $w, $x

      查看:c.uresolver.viewit.related_type_list.CONTAINS = Contains
    详情:显示/关联 – 连续出版物:(在Primo规范化规则中定义)
    添加会议名称的连续出版物 811

    $w, $x

      查看:c.uresolver.viewit.related_type_list.CONTAINS = Contains
    详情:显示/关联 – 连续出版物:(在Primo规范化规则中定义)
    添加条目同一题名的连续出版物 830

    $w, $x

      查看:c.uresolver.viewit.related_type_list.CONTAINS = Contains
    详情:显示/关联 – 连续出版物:(在Primo规范化规则中定义)
    有效的ISBN,ISSN或其他标准号码(远程) 020 $a, $e 010 $a 查看: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
    取消/无效的ISBN,ISSN或其他标准号码(远程) 020 $z 010 $z 查看: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
    链接ISSN(远程) 022 $l 011 $f 查看:c.uresolver.viewit.related_type_list.LINKS_TO = Links To
    有关配置相关记录的更多信息,请见配置电子服务的相关记录

    在Primo中启用显示相关记录

    要配置相关记录,您必须具有以下角色之一:
    • 通用系统管理员
    • 读者服务管理员
    相关记录服务配置页面使您能够配置出现在Primo/Primo VE的查看和获取中的相关题名的电子服务。
    要启用相关记录服务:
    1. 打开相关记录服务配置页面(配置菜单 > 读者服务 > 发现界面显示逻辑 > 相关记录)。

      Related_Record_Services_Configuration_04.png
      相关记录服务配置页面
    2. 对于电子馆藏,参考下表配置相关记录在查看中的显示方式。有关更多信息,见配置电子服务的相关记录修改相关电子服务的显示标签

      相关记录服务配置选项 - 查看部分
      参数 描述

      启用相关记录服务

      如果想要在查看中显示记录的相关题名,选择。如果启用,剩余的字段会使您配置限制或修改特定类型记录的相关题名显示。

      如果全文可获取,则显示相关服务

      如果有全文可用,显示相关记录的服务。如果OpenURL中的原始记录有全文服务,则不会显示相关记录的服务。

      显示连续出版物的相关服务

      显示连续出版物的相关服务(具有期刊资料类型)。

      显示专著的相关服务

      包含专著(具有图书材料类型)的相关服务。

      复制电子资源库服务

      为远程相关服务使用复制电子资源库服务。如果相关记录与相同的电子资源库相关联,则Primo仅显示一个服务。

      为相关服务启用直接链接

      打开直链功能。

      禁用数字记录的相关记录服务

      禁用数字记录的相关记录服务。

      显示密切相关记录服务

      紧密相关的服务(在书目记录中定义为MARC 773或774字段)应如何显示:

      • 作为原有服务的一部分 – 紧密相关的服务放置在查看的常规服务列表中,没有指示这些是相关题名的服务。

      • 从初始记录服务分离 – 密切相关的服务放置在查看的相关题名服务部分。

    3. 对于纸本馆藏,参考下表配置相关记录在获取中的显示方式。有关更多信息,见配置纸本馆藏的相关记录

      相关记录服务配置选项 - 获取部分
      参数 描述

      启用相关记录服务

      如果想要在获取中显示记录的相关题名,选择。如果启用,剩余的字段会使您配置限制或修改特定类型记录的相关题名显示。

      显示连续出版物的相关馆藏

      选择该选项显示连续出版物的相关馆藏记录。

      显示专著的相关馆藏

      选择该选项显示专著的相关馆藏记录。

      请注意,对于专著,在读者提交读者服务题名层级的请求时,会考虑显示在获取中的相关馆藏。如果禁用了专著的相关记录显示,读者服务题名层级请求不会考虑未显示的馆藏相关记录。

      显示密切相关记录馆藏

      选择以下选项指示想要如何在获取中显示密切相关记录(通过书目记录的MARC 773或774字段定义):

      • 作为原有馆藏的一部分 – 紧密相关的记录放置在获取的初始馆藏列表中,没有指示这些是相关馆藏,包括题名和相关类型。

      • 从初始记录馆藏分离 – 密切相关的记录放置在查看的相关题名服务部分。有关更多信息,见上表中的c.uresolver.getit2.display_related_holding_separately_from_original_record

      对于Primo VE,不管如何设置,相关记录会分开显示。

    4. 选择保存

    • Was this article helpful?