Lending Requests
Using the Lending Requests area, the Design Analytics user may create reports/dashboards for the lending requests area and is able to answer the following types of business questions:
- Which partners where requested?
- Lending Request counts
- Which type of users issue the requests
- Time statistics between request and sent

Star Diagram – Lending Requests
Field Descriptions
The following lists the fields available in Lending Requests:

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.
Field | Description | Additional Information |
---|---|---|
Num of Requests | Holds the number of lending requests | |
Number of Non-fulfilled Requests | Holds the number of rejected requests | |
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 | |
Days of Request | Holds the number of days from when the request was created until the request was completed | |
Days of Request Created to Material Sent | Number of days from when the lending request was created until the material was sent to the requested partner | |
Days of Material Sent to Return | Number of days from when the material sent to the partner until the material returned to the library | |
Lending Request Status | Holds the status of the request | See the field location in Alma in the figure Lending Requests - Edit, below. |
Internal ID | Holds the Unique ID of the lending request | |
Assign To | The staff user that is assigned to handle the lending request | |
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. |
Item ID | Holds the Item ID of the borrowing resource | |
Item Barcode | Holds the item barcode | |
Item Sent Date | Holds the date that item was sent to the partner | |
Item Return Date | Holds the date that the item returned to the library | |
Identifier | Holds the ISSN/ISBN of the requested resource | |
Requester Email | Holds the email address of the requester | See the field location in Alma in the figure Lending Requests - Edit, below. |
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. |
Note | Text field for comments | See the field location in Alma in the figure Lending Requests - Edit, below. |
Creator | Stores the creation date | |
Modification Date | Stores the modification date | |
Modified By | Stores the user name that modified the record | |
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. |
Requested Format | Indicates the format of the request (Digital/Physical) | See the field location in Alma in the figure Lending Requests - Edit, below. |
Citation Type | Indicates whether the resource is an article or book | |
Locate Status | Indicates whether the resource has been located or not | |
Item Policy | Hold the item policy | |
Material Type | Holds the Item material type | |
Overdue | Indicates if the item is overdue | |
Overdue Sent Date | The date the last overdue message was sent |

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.
Field | Description | Additional Information |
---|---|---|
Lending Creation Date | Stores the lending request creation date in a date format such as 2/29/2012 | |
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 |
The rest of the fields are the same as for Loan Date.
Field | Description | Additional Information |
---|---|---|
Loan Date | Stores the loan date in the date format 2/29/2012 | |
Loan 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 |
Loan Month | Stores the month of the date in month description format such as February | |
Loan Full Month | Stores the month and the year of the date in a display format such as Feb 12 | |
Loan Quarter | Stores the quarter of the date in a display format such as Q1 | |
Loan Year | Stores the year of the date in string format such as 2012 | |
Loan Fiscal Year | Stores the fiscal year of the date in string format such as 2012. | |
Loan Time | Stores the time in the hours:minutes:seconds format for the loan date | |
Loan 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. |
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.
The fields are the same as for Loan Date.
Field | Description | Additional Information |
---|---|---|
Loan Date | Stores the loan date in the date format 2/29/2012 | |
Loan 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 |
Loan Month | Stores the month of the date in month description format such as February | |
Loan Full Month | Stores the month and the year of the date in a display format such as Feb 12 | |
Loan Quarter | Stores the quarter of the date in a display format such as Q1 | |
Loan Year | Stores the year of the date in string format such as 2012 | |
Loan Fiscal Year | Stores the fiscal year of the date in string format such as 2012. | |
Loan Time | Stores the time in the hours:minutes:seconds format for the loan date | |
Loan 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.
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. |
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 |

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.
Field | Description | Additional Information |
---|---|---|
Library Code | Stores the library code | |
Library Description | Stores the library description | |
Library Name | Stores the library name | |
Unit Type | Store the type of organization unit | Values can be Institution/Library |
Location
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.
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 Desc | 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. |
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.
Field | Source in Alma (for Internal Reference) | Mapping from MARC |
---|---|---|
Title | Taken from display.title in the display section of the operational record | MARC 245 subfields a,b |
Author | Taken from display.author in the display section of the operational record | List values, delimiter is (;)
|
ISBN | Taken from search.isbn in the search section of the operational record | List values, delimiter is ; MARC 020 a,e,z |
ISSN | Taken from search.issn in the search section of the operational record | List values, delimiter is ; MARC 022 a,y,e,z |
Publisher | Taken from display.publisher_const_b in the display section of the operational record | MARC 260 b MARC 264 b Remove special characters and replace spaces. |
Publication Date | Taken from display.date_of_publication in the display section of the operational record | MARC 260 c |
Publication Place | Taken from display.place_of_pu blication in the display section of the operational record | MARC 260 a |
Place Code | Taken from display.place_code in the display section of the operational record | For MARC21 this is taken from 008 pos. 15-17 |
Material Type | Taken from search. material_type in the search section of the operational record | MARC control LDR Material Type |
Begin Publication Date | Taken from display.begin_pub_date in the search section of the operation | For MARC21 this is taken from 008 pos. 7-10 |
End Publication Date | Taken from display.end_pub_date in the search section of the operation | For MARC21 this is taken from 008 pos. 11-14 |
Category of Material | Taken from display. category_of_material in the display section of the operational record | Position 0 of the 007 field of the bibliographic record |
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 |
Bibliographic ID | Taken from display.bib_id in the display section in the operational record | MARC 010 excluding numeric subfields |
Network Number | Taken from search. other_system_number in the search section of the operational record | This field is called "other system number" in Alma List values. The delimiter is ; MARC 035 excluding numeric subfields |
Edition | Taken from display.complete_edition in the display section of the operational record | MARC 250 subfields a,b |
Language Code | Taken from display.language in the display section in the operational record | For MARC21 this is taken from 008 pos. 35-37 |
Series | Taken from display.series_small in the display section in the operational record | List values, delimiter is ;
|
Subjects | Taken from display.subjects in the display section of the operational record | List values, delimiter is ; MARC 6XX excluding numeric |
Type of Date | Taken from display. type_of_date in the search section of the operational record | For MARC21 this is taken from 008 pos. 6 |
Uniform Title | Taken from display.uniform_title in the display section of the operational record | MARC 240 excluding numeric subfields MARC 130 subfields a,p |
Resource Type | Constructed based on existing bibliographic fields such as the LDR and 008. For more information, see Working with the Resource Type Field. |
The following table describes other fields in the shared dimension (taken from Alma and not MARC):
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. |
MMS ID | Stores the MMS ID of the item |
LC Classification Top Line | Stores the combined LC code and classification numbers until the first period followed by a letter such as NB933 when the lc_class_number is NB933.F44 |
Dewey Classification | Stores the Dewey Classification |
Dewey Classification Top Line | Stores the first 3 digits of the Dewey Classification |
Local Param1 | This field allows you to enrich the bibliographic information exported to Analytics with additional information stored in MARC 9XX local 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). Following configuration of this field by Ex Libris Support, its value will be available in analytics. |
Local Param2 | See the description above. |
Local Param3 | See the description above. |
Local Param4 | See the description above |
Local Param5 | See the description above |
Creator | Stores the name of the user that created the record |
Creation Date | Stores the creation date |
Modified By | Stores the user name that modified the record |
Modification Date | Stores the modification date |
Suppressed from Discovery | Indicates whether the record is suppressed from external discovery systems |
Bibliographic Lifecycle | The Lifecycle of the item. Possible values are Deleted and In Repository. This allows you to filter reports by In Repository/Deleted items. |
Network ID | This field is used by institutions implementing a Network Zone. It is the same as the MMS ID of the bibliographic record in the Network Zone and can be used to create reports that show the MMS ID in the member institution (using the existing MMS ID), as well as the corresponding MMS ID in the Network Zone. |
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. |
ISSN (Normalized) | The normalized ISSN. This field is useful when you want to use the normalized ISBN from one subject area to compare with a report with fields from a different subject area. |
ISBN (Normalized) | The ISBN. Created for uniformity with Title (Normalized) and ISSN (Normalized). |
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.
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 | |
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 | |
Enum A | The main level of enumeration - usually the volume | |
Is Magnetic | Whether the item is magnetic material or not. | |
Expected Arrival Date | The date when a purchased item is expected to arrive at the library | |
Due Back Date | Indicates the date that the item is due back at the library | |
Inventory Date | The last time inventory was checked (not currently in use) | |
Last Loan Date | The last time the item was loaned | |
Statistics Note 1-3 | Holds statistic notes | |
Receiving Date | The date the material was actually received/activated for the first time | |
Temporary Call Number Type | A call number type provided when the item is in a temporary location | |
Display Temporary 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 | |
Temporary Physical Location In Use | Whether the item is in a temporary location or in a permanent location | |
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 |
Institution
The shared Institution dimension allows the network institution to view reports according to institution. It is available in every subject area. It contains the following fields:
Field | Description | Additional information |
---|---|---|
Institution Code | The code of the institution. | |
Institution Name | The name of the institution. |
If an analytics report is run from a member institution 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.