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

    Borrowing Requests

    Using the Borrowing Requests area, the Design Analytics user can create reports/dashboards for the Borrowing Requests area and is able to answer the following types of business questions:
    • Which partners were requested
    • Request counts
    • Which type of users issue the requests
    • Time statistics between request and arrival
    • How many requests were rejected
    • How many requests were completed
    borrowing_requests_star.gif
    Star Diagram – Borrowing Requests

    Field Descriptions

    The following lists the fields available in Borrowing Requests.
    borrowing_requests_descriptions.png
    Borrowing Requests – Field Descriptions

    Borrowing Request Details

    The Borrowing Requests table is a fact table that stores all measures relating to specific borrowing requests from a specific partner. This table also holds details about the borrowing requests, including request status, request format, and locate status. The primary keys are ID and PARTNER_ID.
    Borrowing Requests Details
    Field Description Additional Information
    Request Level Measurements
    Num of Requests Holds the number of patron borrowing requests This includes the number of requests from all potential partners in the Rota
    Num of Requests Filled Holds the number of requests that have a receiving date  
    Number of Request Renewals Holds the number of request renewals  
    Num of Request Renewal Rejections Holds the number of request renewal rejections  
    Num of General Messages Holds the number of general messages  
    Num of Locate Failed Requests The number of failed locate requests Includes data for requests that were created from May 2021 and later
    Partner Level Measurements
    Num of Partners in Rota (Total) Holds the total number of partners in the Rota  
    Num of Partners in Rota (Consulted) Holds the number of consulted partners in the Rota  
    Num of Active Partner Requests Holds the number of borrowing requests whose Partner Active Status is set to Active  
    Num of Digital Accesses  Holds how many requested digital files were actually accessed by patrons  
    Num of Non Fulfilled Partner Requests Holds the number of borrowing requests whose Partner Active Status is set to Reject (indicates that the request to this partner cannot be fulfilled)  
    Num of Canceled Partner Requests Holds the number of canceled partner requests  
    Num of Expired Partner Requests Holds the number of expired partner requests  
    Num of Rapid Local Override The number of times librarians overrode the RapidIILL block for borrowing requests when the borrowing library has the requested item locally.  
    Days of Request for Partner Holds the number of days of request for partner. The time begins when the request is sent to the partner and ends when the request is either sent to a different partner or is 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 to Material Arrival Number of days from when the request was created until the material arrived 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 Sent to Material Arrival Number of days from when the request was sent to the partner until the material arrived 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 Sent to Non-Fulfilled Number of days past from when the request was sent to the partner until it was rejected (non-fulfilled) 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 Arrival to Patron Loan Number of days from when the material arrived until the patron loaned the item 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 Patron Check-In to Return Number of days from when the patron checked in the item until it was returned to the ILL 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.
    Hours of Request for Partner Holds the number of hours of request for partner. The time begins when the request is sent to the partner and ends when the request is either sent to a different partner or is 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 to Material Arrival Number of hours from when the request was created until the material arrived 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 Sent to Material Arrival Number of hours from when the request was sent to the partner until the material arrived 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 Sent to Non-Fulfilled Number of hours past from when the request was sent to the partner until it was rejected (non-fulfilled) 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 Arrival to Patron Loan Number of hours from when the material arrived until the patron loaned the item 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 Patron Check-In to Return Number of hours from when the patron checked in the item until it was returned to the ILL 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.
    Minutes of Request for Partner Holds the number of minutes of request for partner. The time begins when the request is sent to the partner and ends when the request is either sent to a different partner or is 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 to Material Arrival Number of minutes from when the request was created until the material arrived 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 Sent to Material Arrival Number of minutes from when the request was sent to the partner until the material arrived 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 Sent to Non-Fulfilled Number of minutes past from when the request was sent to the partner until it was rejected (non-fulfilled) 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 Arrival to Patron Loan Number of minutes from when the material arrived until the patron loaned the item 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 Patron Check-In to Return Number of minutes from when the patron checked in the item until it was returned to the ILL 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.
    Digital Resource First Access Date

    The date and time that the digital resource was first accessed

     
    Digital Resource First Access Date (Calendar)

    The date that the digital resource was first accessed (without the time)

     
    Identifier Holds the ISSN/ISBN of the requested resource  
    Internal ID Holds the Unique ID of the borrowing request See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Item ID Holds the Item ID of the borrowing resource  
    Item Loan ID Holds the item loan ID after the item was loaned  
    Fulfillment Request ID Hold Request ID  
    Item Loan Date Holds the date that the material was loaned by the patron  
    Item Return Date Holds the date that the item was returned to the ILL  
    Item Arrival Date Holds the date that the material arrived to the library  
    Journal Title The title of the journal of the borrowing request  
    Additional Notes The additional notes added under the Notes tab of the Resource Sharing Borrowing Requests page  
    Chapter Title The chapter title of the borrowing request  
    Chapter Number The chapter number of the borrowing request  
    Is Filled Indicates if the borrowing request was filled  
    Issue The issue of the borrowing request  
    Pages The pages of the borrowing request  
    Volume The volume of the borrowing request  
    Label The labels on the borrowing request This field is relevant for customers with Rapido.
    Label History The deleted labels on the borrowing request This field is relevant for customers with Rapido.
    Level of Service The level of service of the borrowing request  
    Lending Library The lending library  
    Lending Institution The lending institution  
    Partner Active Status Indicates whether the partner record is Active/Rejected/Non-Active/Cancelled/Expired  
    Citation Type Indicates whether the resource is an article or book  
    Locate Status Indicates whether the resource is 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  
    BL Request Targets British Library codes for where to search for the material  
    BL Customer ID Holds the customer code and password of the British Library system  
    BL Requested Delivery Terms British Library codes for the delivery format and speed  
    BL Requested Actions British Library codes for other instructions for queries  
    Needed by Date Holds the date by which this material is needed See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Request Non-Fulfilled Date Holds the date that the request was rejected for this partner  
    Request Sending Date Holds the date that the request was sent to the partner  
    Item Check-In Date Holds the date that the item was returned to the library by the patron  
    Item Loan Indicator Indicates whether the requested resource was loaned  
    Patron Information Indicator Indicates whether more information is needed from the patron  
    Request Completed Indicator Indicates whether the lifecycle of the request is in progress or it is completed  
    Max Fee Holds the maximum fee that the patron is willing to pay for this service See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Agree Copyright Indicates whether the patron has checked the Agree Copyright check box See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Note A text field for comments See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Creator Stores the creation date  
    Modification Date Stores the user name that modified the record  
    Modified By Stores the modification date  
    Borrowing Request Status Holds the status of the request See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Cancellation Reason The cancellation reason of the borrowing request This enables you to follow trends and understand why requests are being cancelled.
    Copyright Status The copyright approval status  
    Shipping Cost The shipping cost. See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Shipping Cost Currency The currency of the shipping cost. See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Shipping Date The date and time the lender shipped the item to the borrower. Date fields can consist of a partial date, such as just the year or a month and year.
    Shipping Date (Calendar) The date the lender shipped the item to the borrower. 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.
    External Identifier The ID of the library that fulfills the borrowing request See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Request Type The request format and the request type  
    Requested Format Indicates the format of the request (Digital/Physical) See the field location in Alma in the figure Borrowing Requests - Edit, below.
    Supplied Format The format in which the borrowing request was supplied to the patron Possible values: Physical or Digital
    borrowing_request_details.png
    Borrowing Requests - Edit

    Borrowing Creation Date

    The Creation Date table is a dimension table that stores details about the borrowing 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 that are displayed 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 to the specific date on which the borrowing request was created. The total number of borrowing requests is listed next to the relevant level in the hierarchy.
    Borrowing Creation Date
    Field Description Additional Information
    Borrowing Creation Date and Time Stores the borrowing creation date in the date format 2/29/2012 and the time in hours and minutes  
    Borrowing Creation Date Stores the borrowing creation date in the date format 2/29/2012  
    Borrowing Creation Start of Week The date of the first business day of the week  
    Borrowing Creation Week Number The number of the week of the year  
    Borrowing 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
    Borrowing Creation Month Stores the month of the date in month description format such as February  
    Borrowing Creation Full Month Stores the month and the year of the date in a display format such as Feb 12  
    Borrowing Creation Quarter Stores the quarter of the date in a display format such as Q1  
    Borrowing Creation Year Stores the year of the date in string format such as 2012  
    Borrowing Creation Fiscal Month Key Stores the fiscal year of the date in number format such as 2 for February.  
    Borrowing Creation Fiscal Year Stores the fiscal year of the date in string format such as 2012  
    Borrowing Creation Date Filter Used to filter report results by date.  
    Borrowing Creation 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.  

    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 Indicator Indicates if the request originated from Rapido.  
    Rapido Label The Rapido label  
    Rapido Label History The Rapido label history  
    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  

    Due Date

    The Due Date table is a dimension table that stores details about the due date of transactions, such as month, year, and quarter. The primary keys are Date_Key.
    Loan 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 Month Key Stores the fiscal month of the date in number format such as 2 for February  
    Due Fiscal Year Stores the fiscal year of the date in string format such as 2012.  
    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 to which the borrowing request was sent. 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 Status Holds the partner status (Active/Reject/Non Active) See the field location in Alma in the figure Borrowing Requests - Partners, below.
    Partner Deleted Status Indicates if the partner was deleted.  
    Profile Type Holds the protocol type with which we 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 the 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 an item back to this 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_new.png
    Borrowing Requests - Partners

    Requester

    The Requester table is a dimension table that stores the details about the Staff and Public users that request the item. The primary key of the table is USER_ID.
    The field descriptions can be found in the User Details shared dimension.
    • Many institutions store information about individuals, including personal details and information about their activities. Due to privacy concerns, some institutions are required to anonymize the data on a regular basis.
    • Alma offers the option to delete such user information for fulfillment and resource sharing activities. The information is deleted for activities that have been completed, such as completed loans, closed fines and fees, or resource sharing borrowing requests.
    • You can configure Alma to delete the more specific information (for example, User ID) and retain the more general user information (for example, User Group and Job Title).
    • The information that is not anonymized can be included in Analytics reports.
    • For more information concerning anonymization, see Security and Data Privacy.
    Field Description Additional information
    User ID Stores the unique ID of the user  
    Primary identifier Stores the primary identifier that the user uses in order to log on to Alma See the field location in Alma in the image below.
    User Title The title of the user  
    User Type Stores the values Internal and External.
    • Internal - An internal user is one whose core user details are managed within the system such as user name, password, contact information, and so forth.
    • External - An external user is one whose core user details are managed by a student information system.
    See the field location in Alma in the image below.
    User Group Stores the group with which the user is associated such as Faculty, Graduate, or Student See the field location in Alma in the image below.
    User Record Type Indicates if the user is a Public User or a Staff User See the field location in Alma in the image below.
    First Name Stores the user’s first name See the field location in Alma in the image below.
    Full Name The user's first and last name There is no option to include the middle name.
    Last Name Stores the user’s last name See the field location in Alma in the image below.
    Middle Name Stores the middle name of the user See the field location in Alma in the image below.
    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.
    Job Description Stores free-form text that describes the function of the user in the library See the field location in Alma in the image below.
    Job Title Stores the job category definition to which the user belongs based on the Job Categories code table See the field location in Alma in the image below.
    Gender Possible values are taken from the Genders code table (Configuration > User Management > User Details > Genders) See the field location in Alma in the image below.
    Birth Date Stores the birth date of the user See the field location in Alma in the image below.
    Campus Code Stores the campus code of the user See the field location in Alma in the image below.
    Status Date Stores the date on which the patron was registered in the institution See the field location in Alma in the image below.
    Status Indicates if the user is active See the field location in Alma in the image below.
    Creation Date Stores the date that the user was created in the system See the field location in Alma in the image below.
    Last Activity Date The last date that a patron made a request or borrowed or returned an item  
    Modified By Stores the name of the user that modified the user record See the field location in Alma in the image below.
    Modification Date Stores the date of the modification of the user record See the field location in Alma in the image below.
    Expiry Date Stores the date on which the user is to expire and no longer be able to get service from the system See the field location in Alma in the image below.
    Changing the user expiry date is one way to control item due dates that extend beyond the end of a semester and must be shortened to the end of the semester. For more information, see How to Make Items Have Due Dates at the End of the Semester.
    Locked Out Date Indicates the date on which the user is locked out. A user is locked out if he tries to access the Alma system several times with incorrect credentials.  
    Purge Date Stores the date on which the user record is to be deleted from Alma See the field location in Alma in the image below.
    Default Language Stores the default language of the user See the field location in Alma in the image below.
    Failed Authentication Stores the number of times that the user tried to access Alma with an incorrect password  
    Creator Stores the user name of the user that created the user in the system See the field location in Alma in the image below.
    External ID Stores the ID of the user in the originating system  
    Identifier 1 Stores identifier 1. The identifier field allows you to enrich the user details exported to Analytics with additional identifiers. Selecting a specific identifier to be included in the user details is done in Alma (in a table that is currently restricted to Ex Libris staff). For assistance in defining this field, contact Ex Libris Support.
    Only one value per identifier is supported.
    Identifier 2 Stores identifier 2. See details for the Identifier 1 field above.  
    IdP Service in Use Indicates if an identity provider service is in use  
    Statistical Categories 1-10 These fields allow you to map ten statistical categories. This allows you to filter reports based on advanced user information typically stored in the statistical category fields. For more information, see Configuring Statistical Categories for Analytics.  
    Resource Sharing Library Code The code of the resource sharing library assigned to the user.  
    Resource Sharing Library The resource sharing library assigned to the user.  
    Cataloger Level The cataloger level of the user  
    Has Role Other Than Patron indicates if the patron has a role other than Patron  
    Has Role Other Than Patron and Instructor  Indicates if the patron has a role other than Patron and Instructor  
    Is Blocked Indicates if the patron is blocked  
    Patron Letters Opt In The letters for which the patron has opted in  
    Patron Letters Opt Out The letters for which the patron has opted out  
    User – Linked From Other Institution Indicates if the user is linked from another institution Possible values:
    • yes
    • no
    User – Linked From Institution Code The code of the institution from which the user is linked  
    User – Linked From Institution Name The name of the institution from which the user is linked  
    Linked To Other Institution Indicates if the user is linked to another institution  
    User Group Code The user group code  
    users_report1.png
    users_report2.png
    user_details_page_new.png

    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  
    Library Name Stores the library name  
    Library Name (Active) Stores the library name of active (not deleted) libraries  
    Library Description Stores the library description  
    Unit Type Store the type of organization unit Values can be Institution/Library

    Bibliographic Details

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

    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
    Electronic location and access The location and access URl for the electronic resource 856 all subfields    
    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
    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 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
    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 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,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 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
    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 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,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 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)

    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

    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.
    Assigned To
    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  
    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  
    IdP Service in Use Indicates if an identity provider service is in use  
    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.