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

    Lending Requests (Resource Sharing)

    Using the Lending Requests (Resource Sharing)  area, the Design Analytics user may create reports/dashboards for the Lending Requests (Resource Sharing) area and is able to answer the following types of business questions:
    • Which partners were requested?
    • Lending Request counts
    • Which type of users issue the requests
    • Time statistics between request and sent
    lending_requests_star.gif
    Star Diagram – Lending Requests

    Field Descriptions

    The following lists the fields available in Lending Requests:
    lending_requests_descriptions.png
    Lending Requests – Field Deceptions

    Lending Requests Details

    The Lending Requests table is a fact table that stores all measures relating to specific Lending requests. This table also holds details about the lending requests including request status, request format, and locate status. The primary key is ID.
    Lending Requests Details
    Field Description Additional Information
    Actual Shipped Format The shipping format Possible Values:
    • Physical
    • Digital
    • Physical Non-returnable
    Additional Notes The additional notes added under the Notes tab of the Resource Sharing Lending Requests page  
    Borrowing Institution (Rapid ILL) The Rapid ILL borrowing institution  
    Borrowing Library (Rapid ILL) The Rapid ILL borrowing library  
    Citation Type Indicates whether the resource is an article or book  
    Creator Stores the creation date  
    Days of Material Sent to Return Number of days from when the material sent to the partner until the material returned to the library The Day value is the number of complete days. If the value is composed of several time periods, the sum of the values is considered.
    Days of Request Holds the number of days from when the request was created until the request was completed The Day value is the number of complete days. If the value is composed of several time periods, the sum of the values is considered.
    Days of Request Created to Material Sent The number of days from when the lending request was created until the material was sent to the requested partner The Day value is the number of complete days. If the value is composed of several time periods, the sum of the values is considered.
    External Request ID Holds the Request ID that arrived from the partner (external system ID) See the field location in Alma in the figure Lending Requests - Edit, below.
    Hours of Material Sent to Return Number of hours from when the material sent to the partner until the material returned to the library The Hour value is the number of complete hours. If the value is composed of several time periods, the sum of the values is considered.
    Hours of Request Holds the number of hours from when the request was created until the request was completed The Hour value is the number of complete hours. If the value is composed of several time periods, the sum of the values is considered.
    Hours of Request Created to Material Sent Number of hours from when the lending request was created until the material was sent to the requested partner The Hour value is the number of complete hours. If the value is composed of several time periods, the sum of the values is considered.
    Identifier Holds the ISSN/ISBN of the requested resource  
    Internal ID Holds the Unique ID of the lending request  
    Item Barcode Holds the item barcode  
    Item ID Holds the Item ID of the borrowing resource  
    Item Policy Hold the item policy  
    Item Return Date Holds the date that the item returned to the library  
    Item Sent Date Holds the date that item was sent to the partner  
    Journal Title The title of the journal  
    Label The labels on the lending request  
    Label History The deleted labels on the lending request  
    Lending Request Status Holds the status of the request See the field location in Alma in the figure Lending Requests - Edit, below.
    Level of Service The level of service of the lending request  
    Locate Status Indicates whether the resource has been located or not  
    Lost Item Fee Amount The mount of the lost item fee  
    Lost Item Fee Currency The currency of the lost item fee  
    Lost Item Fee VAT The VAT of the lost item fee  
    Material Type Holds the Item material type  
    Minutes of Material Sent to Return Number of minutes from when the material sent to the partner until the material returned to the library The Minute value is the number of complete minutes. If the value is composed of several time periods, the sum of the values is considered.
    Minutes of Request Holds the number of minutes from when the request was created until the request was completed The Minute value is the number of complete minutes. If the value is composed of several time periods, the sum of the values is considered.
    Minutes of Request Created to Material Sent Number of minutes from when the lending request was created until the material was sent to the requested partner The Minute value is the number of complete minutes. If the value is composed of several time periods, the sum of the values is considered.
    Modification Date Stores the modification date  
    Modified By Stores the user name that modified the record  
    Needed by Date Holds the date by which this material is needed See the field location in Alma in the figure Lending Requests - Edit, below.
    Days of Delivery Duration The number of days from when the lending library sent the requested material until the patron received it.  
    Hours of Delivery Duration The number of hours from when the lending library sent the requested material until the patron received it.  
    Minutes of Delivery Duration The number of  minutes from when the lending library sent the requested material until the patron received it.  
    Received Date The date that the requested material was received  
    Note Text field for comments See the field location in Alma in the figure Lending Requests - Edit, below.
    Num of Canceled Requests Holds the number of requests canceled by the borrower  
    Num of Expired Requests Holds the number of requests that expired  
    Num of General Messages Holds the count of messages sent between the borrower and lender  
    Num of Locate Failed Requests The number of failed locate requests Includes data for requests that were created from May 2021 and later
    Num of Recalled Requests The number of recalled requests  
    Num of Requests Holds the number of lending requests This includes the number of requests from all potential partners in the Rota
    Number of Non-fulfilled Requests Holds the number of rejected requests  
    Overdue Indicates if the item is overdue  
    Overdue Sent Date
    The date the last overdue message was sent  
    Rapido Indicator Indicates if the request originated from Rapido.  
    Rapido Pod The Rapido Pod to which the request is linked.  
    Reject Reason The reason the lending request was rejected  
    Requested Format Indicates the format of the request (Digital/Physical) See the field location in Alma in the figure Lending Requests - Edit, below.
    Requester Email Holds the email address of the requester See the field location in Alma in the figure Lending Requests - Edit, below.
    Shipping Cost The shipping cost. See the field location in Alma in the figure Lending Requests - Edit, below.
    Shipping Cost Currency The currency of the shipping cost. See the field location in Alma in the figure Lending Requests - Edit, below.
    lending_requests.png
    Lending Requests - Edit

    Lending Creation Date

    The Creation Date table is a dimension table that stores details about the lending request creation date. Key fields are used whenever calculations are required. Description fields may be used for formatting the display of the report. Alma stores the following types of fields:
    • Calendar Fields – These are date fields as they display in the calendar.
    • Fiscal Date Fields – These are date fields that match the institution's fiscal period. In the examples below, the fiscal period of the institution is for fiscal year 2012 that starts June 1, 2011 and ends May 31, 2012.
    Using this dimension, the user may drill down from year to month and from month to the specific date on which the lending request was created. The number of the lending requests is accumulated to the relevant level in the hierarchy.
    Lending Creation Date
    Field Description Additional Information
    Lending Creation Date Stores the lending request creation date in a date format such as 2/29/2012  
    Lending Creation Start of Week The date of the first business day of the week  
    Lending Creation Week Number The number of the week of the year  
    Lending Creation Month Key Stores the month of the date in number format such as 2 for February This field is useful when you want to sort by month
    Lending Creation Month Stores the month of the date in month description format such as February  
    Lending Creation Full Month Stores the month and the year of the date in a display format such as Feb 12  
    Lending Creation Quarter Stores the quarter of the date in a display format such as Q1  
    Lending Creation Year Stores the year of the date in string format such as 2012  
    Lending Creation Fiscal Month Key Stores the fiscal month of the date in number format such as 2 for February This field is useful when you want to sort by month
    Lending Creation Fiscal Year Stores the fiscal year of the date in string format such as 2012.  
    Lending Creation Date Filter Used to filter report results by date.  
    Lending Creation Date Stores the Hierarchy column that allows the user to drill down from the year to the month to the specific creation date. This column provides the user the option to view the cumulative measures in each level of the hierarchy

    Rapido Attributes

    The Rapido Attributes table is a dimension table that stores details about Rapido.
    Rapido Attributes
    Field Description Additional Information
    Rapido Automatic Renewals Allowed Indicates if automatic renewals of the borrowing request are allowed   
    Rapido Expire Time (in days) The number of days until the borrowing request expires  
    Rapido Fill Locally Indicates if the borrowing request is filled locally Possible values: Yes, No, Test
    Rapido Indicator Indicates if the request originated from Rapido.  
    Rapido Label The Rapido label  
    Rapido Label History The Rapido label history  
    Rapido Number if Renewals The number of times the borrowing request was renewed  
    Rapido Pod Delivery Time (in days) The Rapido Pod delivery time (in days)  
    Rapido Pod Delivery Time (in hours) The Rapido Pod delivery time (in hours)  
    Rapido Pod ID The Rapido Pod ID to which the request is linked.  
    Rapido Pod Loan Period The Rapido Pod loan period  
    Rapido Pod Name The Rapido Pod name  
    Rapido Pod Shipping Cost The Rapido Pod shipping cost  
    Rapido Source of Request The source of the Rapido borrowing request Possible values are:
    • Other
    • ALMA
    • PRIMO_BLANK (a blank Primo form)
    • API

    Due Date

    The Due Date table is a dimension table that stores the details about the item's due date such as month, year, or quarter. The key fields can be used when calculations are required, and the description fields can be used for formatting the display of the report. Alma stores the following types of fields.
    Due Date
    Field Description Additional Information
    Due Date Stores the loan date in the date format 2/29/2012  
    Due Start of Week The date of the first business day of the week  
    Due Week Number The number of the week of the year  
    Due Month Key Stores the month of the date in number format such as 2 for February This field is useful when you want to sort by month
    Due Month Stores the month of the date in month description format such as February  
    Due Full Month Stores the month and the year of the date in a display format such as Feb 12  
    Due Quarter Stores the quarter of the date in a display format such as Q1  
    Due Year Stores the year of the date in string format such as 2012  
    Due Fiscal Year Stores the fiscal year of the date in string format such as 2012.  
    Due Time Stores the time in the hours:minutes:seconds format for the loan date  
    Due Date Stores the Hierarchy column that allows the user to drill down from the year to the month to the specific loan date. Using this column provides the user with the option to view the accumulative measures in each level of the hierarchy.  

    Partner

    The Partner table is a dimension table that stores the details about the partner from which the lending request was received. The primary key of the table is PARTNER_ID.
    Partner
    Field Description Additional Information
    Partner ID Holds the unique partner ID  
    Partner Name Holds the partner name See the field location in Alma in the figure Borrowing Requests - Partners, below.
    Partner Code Holds the partner code See the field location in Alma in the figure Borrowing Requests - Partners, below.
    Partner Description Holds the partner description  
    Partner Status Holds the partner status (Active/Reject/Non Active) See the field location in Alma in the figure Borrowing Requests - Partners, below.
    New for June!
    Partner System Type
    The system type of the resource sharing partner  
    Partner Deleted Status Indicates if the partner was deleted.  
    Profile Type Holds the protocol type used to communicate with the partner (ARTEmail, NCIP) See the field location in Alma in the figure Borrowing Requests - Partners, below.
    Average Supply Time Average time it takes for the supplier to process a request and send the material See the field location in Alma in the figure Borrowing Requests - Partners, below.
    Delivery Delay Average time it takes to send the item back to the supplier See the field location in Alma in the figure Borrowing Requests - Partners, below.
    Currency Holds the currency that this partner is using See the field location in Alma in the figure Borrowing Requests - Partners, below.
    Creation Date Stores the name of the user that created the record  
    Created By Stores the creation date  
    Modification Date Stores the user name that modified the record  
    Modified By Stores the modification date  
    resource_sharing_partner.png
    Borrowing Requests - Partners

    Library Unit

    The Library Unit table is a dimension table that stores details about the library where the borrowing request was created. The primary key of the table is LIBRARYID.
    The field descriptions can be found in the Library Unit shared dimension.
    Library Unit
    Field Description Additional Information
    Library Code Stores the library code  
    Library Code (Active) Stores the code of active (not deleted) libraries This field is empty if the library is deleted.
    Library Name Stores the library name  
    Library Name (Active) Stores the library name of active (not deleted) libraries This field is empty if the library is deleted.
    Library Description Stores the library description  
    Unit Type Store the type of organization unit Values can be Institution/Library

    Location at Time of Loan

    The Location table is a dimension table that stores details about the location of the physical item. The primary key of the table is LIBRARYID and LOCATION_CODE.
    Location
    Field Description Additional Information
    Campus Code Stores the code of the campus where the physical item is located. This value is calculated through the library campus.
    Campus Name Stores the description of the campus. This value is calculated through the library campus.
    Campus Description Stores the name of the campus. This value is calculated through the library campus.
    Library Code Stores the library code to which the location of the physical item belongs. It is recommended to use the Library Code field of the Library Unit dimension instead of this one.
    Library Name Stores the library name to which the location of the physical item belongs. It is recommended to use the Library Name field of the Library Unit dimension instead of this one.
    Library Description Stores the library description to which the location of the physical item belongs.  
    Location Code Stores the code of the location of the physical item.  
    Location Name Stores the name of the location of the physical item.  
    Location Type Stores the type of the location of the physical item, whether it is open stack or closed stack.  
    Call Number Type Stores the call number type used by the location of the physical item.  
    External Name Stores the name to be displayed to patrons for the location of the physical item.  
    Remote Storage Code Points to a remote storage location where the physical items are stored, if one exists.  
    Location Stores the Hierarchy column that allows the user to drill down from the campus to the library and then to the location of the physical item. This column provides the user with the option to have the user view the accumulative measures (num_of_items) in each level of the hierarchy.
    Suppressed from Discovery Indicates if the holdings record is suppressed from discovery because the location is suppressed (but not necessarily the record) From the Suppress from Discovery checkbox for the location in the configuration of the location

    Bibliographic Details

    The Bibliographic Details table is a dimension table that stores the bibliographic details of the borrowing request 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) 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.)

    The Bibliographic Details table contains two kinds of fields, those derived from the MARC record and those that come from Alma. Although in analytics there is no distinction made between these fields, for explanatory purposes we have divided them into two tables below.

    Bibliographic Details
    Field Note

    Mapping from

    MARC21

    Mapping from UNIMARC

    Mapping from

    Dublin Core

    Author   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   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   010 excluding numeric subfields 020 a dcterms:identifier dcterms:ISBN, dcterms:identifier dcterms:ISSN
    Bibliographic Level   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   Position 0 of the 007 field  200 b dc:type
    DC Description    Relevant only for Dublin Core  Relevant only for Dublin Core  dc:description
    dcterms:description
    dcterms:abstract
    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   MARC 250 subfields a,b 205 a,b,f,g dcterms:isVersionOf
    Electronic location and access The location and access URl for the electronic resource 856 all subfields    
    End Publication Date   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
    General Note The general note 500 a, 5    
    Government Publication The government publication type

    MARC 008 pos. 28

    According to MARC21 Format for Bibliographic Data, MARC 008 pos. 28 is Government Publication for the following material types: Books, Computer Files, Continuing Resources, Maps, and Visual Materials.

    For Music MARC 008 pos. 28 is Accompanying matter.  For Mixed material MARC 008 pos. 28 is Undefined.

    Consequently, when using this field, you may want to filter out records with Material Type = Music and Material Type = Mixed material.

      Not relevant for Dublin Core
    ISBN   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   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   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
    Local Note The local note 590 a, 5    
    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   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   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  
    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   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  

    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.      
    Series   800 t,v

    810 t,v

    811 t,v

    830 a,n,p,v

    410 a,h,i,o,t,x Currently empty.  Planned to come from dcterms:isPartOf
    Series Statement The series statement 490 a,v x    
    Subjects   6XX excluding 69X, 630, 689 600 a,b 602 603-8 610 616 617 dc:subject dcterms:LCSH,MESH,DDC,UDC,LCC
    Subjects (Names) The subject names 600 a,b,c,d,e,l,t.u

    610 a,b,c,d,e,l,n,t,u

    611 a,b,c,d,e,j,l,n,q,t,u

       
    Title  

    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,n,p

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

    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 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.
    The data in the local parameters is limited to 3900 characters.
    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

    Physical Item Details

    The Physical Item Details table is a dimension table that stores details about the physical item details. The primary key is ITEM_ID.
    Physical Item Details
    Field Description Additional Information
    Modification Date The date that the physical item was modified.  
    Modified By The user that modified the physical item.  
    Creator the username of the operator that created the physical item  
    Creation Date The date that the physical item was created.  

    Alternative Call Number Type

    An alternative call number type

    (Note that Alternative Call Number=Item Call Number.)

     
    Description Description of the item  
    Barcode The unique identifier of the specific physical item  
    Material Type Describes the nature of the material represented by the item record  
    Item Policy Defines the conditions under which a request for this item can be fulfilled  
    Provenance Code A code used to identify separate items that belong to different groups (but may be shelved together)  
    Base Status Indicates the availability of the item in its permanent location (in place/not in place)  
    Process Type When the item is being processed (acquisition/loan/bindery/etc) this indicates the type of processing  
    Lifecycle Indicates whether the item is active or deleted  
    Chron I The main level of chronology - usually the year  
    Chron J-M Additional chronology fields  
    Enum A The main level of enumeration - usually the volume  
    Enum B-H Additional enumeration fields  
    Has Committed to Retain Indicates if the library has committed to retain the item  
    Retention Note A free-text note concerning the library's commitment to retain the item  
    Retention Reason The reason the library has committed to retain the item  
    Is Magnetic Whether the item is magnetic material or not.  
    Expected Receiving Date The date when a purchased item is expected to arrive at the library  
    Due Back Date Indicates the date that an item in a temporary location is due back to its permanent location  
    Inventory Date The last time inventory was checked (not currently in use)  
    Inventory Number The inventory number  
    Inventory Price The price of the physical inventory for each physical item  
    Last Loan Date The last time the item was loaned  
    Statistics Note 1-3 Holds statistic notes  
    Internal Note
    1-3
    Internal notes 1-3  
    Receiving Date The date the material was actually received/activated for the first time  
    Temp Call Number Type A call number type provided when the item is in a temporary location  
    Display Temp Call Number A normalized temporary call number for display  
    Originating System ID The ID of the item in the source system from which it has been imported  
    Temp Physical Location In Use Whether the item is currently (at the time at which the report is run) in a temporary location or in a permanent location.

    For example:

    An item was moved from a permanent location to a temporary location on November 28, 2017. It was loaned on November 29, 2017, and when it was loaned, it was still in a temporary location. It was returned from loan on December 13, 2017. On December 14, 2017 it was returned to its permanent location.

    If an Analytics report was run between November 28 and December 13, the Temp Physical Location In Use is Yes. If the report was run before November 28 or after December 13, the Temp Physical Location In Use is No.

    Note that for resource sharing lending requests, this field is always "Yes" after the loan is performed.

    Time Loaned - not sum The amount of time that the physical item was loaned  
    Permanent Call Number The permanent call number  
    Fulfillment Note The fulfillment note  
    Receiving Date and Time The date and time the material was actually received/activated for the first time  
    Replacement Cost The replacement cost In order to filter your report based on the Replacement Cost field, you must add a second copy of this field and edit the formula with the following CAST("Physical Item Details"."Replacement cost" AS DOUBLE). This causes Alma Analytics to treat the field as numeric.

    Assigned To

    The Assigned To table is a dimension table that stores details about the user details of the staff member to whom the request is assigned.
     
    Field Description Additional Information
    Campus Code Stores the campus code of the user  
    External ID Stores the ID of the user in the originating system  
    First Name Stores the user’s first name  
    Gender Stores male or female  
    Job Description Stores free-form text that describes the function of the user in the library  
    Job Title Stores the job category definition to which the user belongs based on the Job Categories code table  
    Last Activity Date The last date that a patron made a request or borrowed or returned an item  
    Last name Stores the user’s last name  
    Middle Name Stores the middle name of the user  
    Preferred First Name Stores the user’s preferred first name See the field location in Alma in the image below.
    Preferred Last Name Stores the user’s preferred last name See the field location in Alma in the image below.
    Preferred Middle Name Stores the user's preferred middle name See the field location in Alma in the image below.
    Primary Identifier Stores the primary identifier that the user uses in order to log on to Alma  
    IdP Service in Use Indicates if an identity provider service is in use  
    Status Indicates if the user is active  
    User Group Stores the group with which the user is associated such as Faculty, Graduate, or Student  
    User ID Stores the unique ID of the user  
    User Record Type Indicates if the user is a Public User or a Staff User  
    User Title Stores the title of the user  
    User Type Stores the values Internal and External  

    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.