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

    Link Resolver Usage

    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?
    link_resolver_star.png
    Star Diagram – Link Resolver Usage

    Field Descriptions

    The following lists the fields available in Link Resolver Usage.
    link_resolver_descriptions.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=

    OpenURL Service Details

    The OpenURL Service Details table is a dimension table that stores the details of the OpenURL service. You can use the fields of this dimension to determine how many times a service was clicked and other information.
    These fields will be fully functional for the August release.
    OpenURL Service Details
    Field Description Additional Information
    Electronic Collection ID The electronic collection ID  
    Electronic Collection Name The electronic collection name  
    Interface Name The interface name  
    Is Clicked Service Indicates (Yes\No) if the service was clicked  
    Is Digital Service Indicates (Yes\No) if the service is a digital service   
    Is Electronic Service Indicates (Yes\No) if the service is an electronic service  
    Is Network Service Indicates (Yes\No) if the service is from the Network Zone  
    Portfolio ID The portfolio ID  
    Service Type The service type  

    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.

    Ex Libris works with content providers worldwide to enrich the metadata available in the Alma Community Zone. To enrich the journal/serial content in the CZ, we work directly with the Library of Congress CONSER feed for electronic serials, which we match against our knowledge base to enrich with all of the relevant metadata fields that they supply (for more details, see Community Zone Serial Records Enrichment). We receive weekly updates from CONSER and enrich the CZ records with all relevant metadata, including the 050 fields (when available).

     

    In the case of book content, we work with multiple providers who are willing to share their metadata with the Alma community globally (for more details, see Community Zone Monograph Records Enrichment). If you have local access to these classifications, you may want to consider working with the local extension for these records whenever an update is not available. (For more details, see Working with Local Extension Fields for Community Zone-linked Records)

    Bibliographic Details
    Field Source in Alma (for Internal Reference)

    Mapping from

    MARC21

    Mapping from UNIMARC

    Mapping from

    Dublin Core

    800 v

    810 v

    811 v

    Displayed when field 490 with first indicator '0' and v do not exist, and field 830 v does not exist.

       
    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
    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
    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
    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
    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
    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 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
    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
    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
    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
    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
    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
    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
    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
    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
    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
    Leading zeros are not displayed.

    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
    Leading zeros are not displayed.

    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
    Leading zeros are not displayed.

    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
    Leading zeros are not displayed.

    035 z

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on
    035 z 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
    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
    Place Code Taken from display.place_code in the display section of the operational record 008 pos. 15-17 102$$a Currently empty, planned to come from dcterms:spatial
    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.

    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.

    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_publication in the display section of the operational record MARC 260 a. When 260a is empty, it is taken from MARC 264a 210 a 214 a Not relevant for Dublin Core (use Place Code)
    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
    Resource Type Constructed based on existing bibliographic fields such as the LDR and 008. For more information, see The Resource Type Field.     dc:type
    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 6XX excluding 69X, 630, 689 600 a,b 602 603-8 610 616 617 dc:subject dcterms:LCSH,MESH,DDC,UDC,LCC
    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 (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
    Title (Filing) The title with common words such as "The" and "An" removed to help with sorting the title alphabetically.
    Any text between double arrows (<<>>) is removed.
    For a video describing the use of this field, see Sort Analytics Reports by Filing Title - Ignoring "The", "A", and "An".

    240 a,c,p

    245 a,c,p

    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
    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 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      
    Uniform Title Taken from display.uniform_title in the display section of the operational record 240 130 500 Not relevant for Dublin Core
    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)
    Active Course Code The code of an active course.
    Active Course Name The name of an active course.
    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.
    Brief Level The level of the brief record
    Chinese Classifications Stores the Chinese Classification
    Collection ID The ID of the collection.  This is a title level collection as defined at 'Resources > Manage Inventory > Manage Collections'.
    Collection Name The name of the collection.  This is a title level collection as defined at 'Resources > Manage Inventory > Manage Collections'.
    Creation Date Stores the creation date. Date fields can consist of a partial date, such as just the year or a month and year.
    Creation Date (Calendar) Stores the creation date. Calendar Date fields always consist of a month, date, and year. If the information is not provided, 01 is added, so that a date of 2020 is rendered 01/01/2020. This date format is useful when filtering the report by date.
    Creator Stores the name of the user that created the record
    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)  

    Has Local Extensions

    Indicates if the Community Zone-linked record has local extensions (Y/N)

    This field will be fully functional in the August release. 

    ISBN (Normalized)
    The normalized ISBN.
    ISSN (Normalized) The normalized ISSN.
    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)

    Recent data may not be available if it has not yet been received from CONSER.
    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
    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.
    Managed by Provider Indicates if the electronic resource is managed by the provider
    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.
    Modification Date Stores the modification date. Date fields can consist of a partial date, such as just the year or a month and year.
    Modification Date (Calendar) Stores the modification date. Calendar Date fields always consist of a month, date, and year. If the information is not provided, 01 is added, so that a date of 2020 is rendered 01/01/2020. This date format is useful when filtering the report by date.
    Modified By Stores the user name that modified the record
    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.
    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
    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

    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.

    Ex Libris works with content providers worldwide to enrich the metadata available in the Alma Community Zone. To enrich the journal/serial content in the CZ, we work directly with the Library of Congress CONSER feed for electronic serials, which we match against our knowledge base to enrich with all of the relevant metadata fields that they supply (for more details, see Community Zone Serial Records Enrichment). We receive weekly updates from CONSER and enrich the CZ records with all relevant metadata, including the 050 fields (when available).

     

    In the case of book content, we work with multiple providers who are willing to share their metadata with the Alma community globally (for more details, see Community Zone Monograph Records Enrichment). If you have local access to these classifications, you may want to consider working with the local extension for these records whenever an update is not available. (For more details, see Working with Local Extension Fields for Community Zone-linked Records)

    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.