Requests

Report Creation Tips

Although request data in Alma goes back only 5 years from the Creation Date, in Analytics it goes back as far as the available data.
Requests are linked to the MMS ID of the bibliographic record, so when creating reports for requests, use the MMS ID and not the barcode.

Filtering Results Using the Active Request Flag

An active request is a request that is still in process, as opposed to a completed request, which is no longer in process. Canceled requests are marked with the relevant Rejected status (Rejected, Rejected by Library, Rejected by Patron (see Request Status).

Canceled requests may be considered active if the requested item is still in process, for example, it is being removed from a hold shelf or a work order department. Therefore, requests that were canceled may in some cases still appear with Active Request Flag=Yes and in other cases with Active Request Flag=No.

Rejected requests, both active and inactive, are not retrievable in the Alma user interface, but do appear in reports. To prevent inactive requests from appearing in reports, the requests must be deleted. To delete inactive requests, contact Ex Libris Support.

Another option is to scan in the rejected request ID from the Scan In item page. This completes the request, triggers it to reappear in Requests Monitor, and adds a Request Completion Date in Analytics.

Typically you would run different reports for each population. For example, for active requests, you can run a report on titles with a high number of requests and for completed requests, you can run a trend analysis of average time to patron collection.

The Active Request Flag field is located in the Request Details folder.

Filtering Results Using the Request Type Description Flag

Requests in Alma are used for both internal processes (for example binding) as well as for patron facing processes. User this filter to narrow your results only to the type of requests in which you are interested.

The Request Type Description field is located in the Request Type folder.

Report on Items with High Requests

Since a request in Alma is done on the title level and not on the item level, there is no item information in the Requests subject area. An important need is to see titles with a high number of open requests and to be able to see for this title how many items are available in the library.

In order to do this, create two reports - one in the Requests SA and one in the Physical Items SA. The first report will be used as a sub-query for the second one.

To create a report of all titles with more than three open requests:

Select New > Analysis and then select Subject Area > Requests.
Create a report with the following columns, for example:
- MMS ID (report must include a field common to the physical items SA in order to create the sub-query. MMS ID is a good candidate.)
- # Requests
Filter the report using:
- request type = Patron physical item request
- # Request > x (in this example we used 3)
- Active request = Yes
Report Criteria
Save the report.
Select New > Analysis and then select Subject Area > Physical Items.
Create a report with the following columns, for example:
- MMS ID (this is must in order to use the filter on the requests)
- Title
- Num of Items
- Time loaned
Filter the MMS ID column using the following criteria:
- Operator – is based on the results of another analysis
- Saved Analysis – locate your previously saved report
- Relationship – is equal to any
- Use values in column – MMS Id
MMS ID Filter

The results of the report are titles that have more than three open request with the required item information. In this example, the number of copies and the times loaned.

Titles With More Than 3 Open Requests

Field Descriptions

The following lists the fields available in Requests.

Requests – Field Descriptions

Request Measures

The Request Measures table is the fact table that stores all the measures (activities) of specific requests. The primary key is ID.

Request Measures
Field	Description	Additional Information
# of Requests	The number of requests.
Time to Available (Days/Hours)	The time between the request being placed and its becoming active.	For open requests that are not yet active, analytics calculates the total time until the current date.
Time to Process (Days/Hours)	The time between the request becoming active and its being placed on the shelf for pickup.	For open requests that are active but not yet on the shelf for pickup, analytics calculates the total time until the current date.
Time to Patron Collection (Days/Hours)	The time between the request being placed on the shelf for pickup and its being fulfilled.	For open requests that are placed on the shelf for pickup but are not yet fulfilled, analytics calculates the total time until the current date. When a request is no longer active, it is moved to the History table. In that case, this field reflects the time from the date that the item was moved to the hold shelf until the date it was moved to the History table.
Total Request Time (Days/Hours)	The total amount of time between the request being placed and its being fulfilled.	For open requests, Alma Analytics will calculate the total time until this date.

Request Measures (Average)

The Request Measures (Average) table is a fact table that stores all the average of the measures (activities) of specific requests. The primary key is ID.

Request Measures (Average)
Field	Description	Additional Information
Average Time to Available (Days/Hours)	The average time between the request being placed and its becoming active.
Average Time to Process (Days/Hours)	The average time between the request becoming active and its being placed on the shelf for pickup.
Average Time to Patron Collection (Days/Hours)	The average time between the request being placed on the shelf for pickup and its being fulfilled.
Average Total Request Time (Days/Hours)	The average total amount of time between the request being placed and its being fulfilled.

Request Process Measures

The Request Process Measures is a fact table that stores all the process measures (activities) of specific requests. The primary key is ID.

Each field has a version that displays the results by hours and by days.

.

Request Process Measures
Field	Description	Additional Information
Await Approval Time	The total amount of time that the request was in the Await Approval step. (The amount of time that the request waited for approval.)
Deposit Item Time	The total amount of time that the request was in the Deposit Item step. (The time from when the digital material was ready to be deposited until the digital file was created.)
Digitize Item Time	The total amount of time that the request was in the Digitize Item step. (The time from when the item was ready at the digitization department until it was digitized.)
Document Delivery Time	The total amount of time that the request was in the Document Delivery step. (The time from when the digital material was ready until it was delivered.)
Hold Shelf Processing Time	The total amount of time that the request was in the Hold Shelf Processing step. (The time it took the library to make the item ready to be placed on the hold shelf.)
On Hold Shelf Time	The total amount of time that the request was in the On Hold Shelf step. (The amount of time the item was on the hold shelf until it was either picked up or removed from the hold shelf.)
Pickup from Shelf Time	The total amount of time that the request was in the Pickup from Shelf step. (The amount of time that it took for the staff to pick up the item from the shelving location.)
Transit Item Time	The total amount of time that the request was in the Transit Item step. (The amount of time the item was in transit between circulation desks and libraries.)
Waiting for Remote Storage Time	The total amount of time that the request was in the Waiting for Remote Storage and Communicating With Remote Storage steps. (The amount of time that the request was waiting for the remote storage facility to receive a request and provide an item to fulfill the request.)
Work Order Department Time	The amount of time that the item was in the Work Order Department step. (The amount of time that the item was in the work order department.)

Request Details

The Request Details table is a dimension table that stores details about the request. The primary key is ID.

Request Details
Field	Description	Additional Information
Active Request Flag	An active request is a request that is still in process.	Filter with this flag to Yes to display currently active requests (typically used for reports on titles with high demand). Filter with this flag to No to display completed requests (typically used for trend analysis and fill rate calculations). For more information, see Filtering Results Using the Active Request Flag.
Cancellation Reason	The cancellation reason inserted when a request is cancelled.
Current Process	The name of the current activity.	The following are the possible values for this field. The values as they appear in Alma are displayed in parenthesis, if they are different: AwaitApproval – the request is waiting for approval. DepositItem – the digital material is ready to be deposited, but the digital file has not yet been created. DocumentDelivery – the digital material is in the process of being delivered. PlaceOnHoldShelf (On Hold Shelf) – the item is on the hold shelf, but has not yet been picked up or removed. TransitItem – the item is in transit between circulation desks and/or libraries. WorkOrderDepartment (In Process) – the request is being processed by a work order department. PickupFromShelf – the item has been picked up from the hold shelf. WaitingForRemoteStorage – the request will be handled by remote storage, but has not been sent to the remote storage yet. DigitizeItem – the item is ready at the digitization department and is in the process of being digitized. CommunicatingWithRemoteStorage (Request Communicated to Storage) – The request will be handled by remote storage, and was sent to the remote already. HoldShelfProcessing – the item has arrived at the requested pickup location, but has not been placed on the hold shelf yet. DigitalInventoryDestination (Digital Inventory) – the requested item is in digital inventory. DigitizationDestination (Digitization) – Item has arrived at the digitization department and is awaiting digitization.
Creator	The creator of the request.	After a request is completed or cancelled, this field displays that user. For the original creator of the request, use the Request Creator field. When the request is made by a staff user, this field contains the staff user’s name. When it is created via Primo\API, it contains the value system.
Caused Recall	Indicates if the request caused a recall of an item that is on loan.
In Transit Flag	This field reflects an internal process and not the In Transit request status.	Yes indicates that the item is in transit, for example, to re-shelving after a patron returns the item.
Manual Description	Contains a free text description. For multi-volume requests it describes the specific issue.
Modification Date	The date that the request was modified.
Modified By	The user that modified the request.
No Pickup Flag	Refers to the first step of a request, which is to take the item from the shelf. Indicates that there is no need to take the item off the shelf.
Note	The note entered by the user.
Override on Shelf Request Policy	Indicates that the pickup location was chosen after overriding the default suggestions.
Pickup Location	The pickup location of the requested item.
Pickup Location Type	The pickup location type of the requested item.
Pickup Slip Printed Flag	Indicates whether a pickup slip was printed.
Related to Resource Sharing Request	Indicates whether the request is related to a resource sharing borrowing request.
Request Creator	The original creator of the request	This field displays the original creator of the request as opposed to the Creator field which, after a request is completed or cancelled, displays the user that completed or cancelled the request.
Request ID	The ID of the request.
Search Type	Indicates whether the request is item level or title level.
Triggered Recall	Indicates whether the request triggered a recall. The value changes from Yes to No when the request status changes to Completed. This means that this field is not useful for creating reports that show a history of recalls. Instead, use the Caused Recall field whose value will remain Yes after the request is completed.
Volume Issue	The volume and issue of the request for requests of specific volumes.
Managed by Library (latest step)	Indicates which library managed the latest step of the request
Managed by Unit (latest step)	Indicates which unit (department) managed the latest step of the request
Managed by Desk (latest step)	Indicates which desk managed the latest step of the request
Status (latest step)	The status of the latest step of the request
Associated Course Code	The code of a course that was active during the time the item was requested. The item belonged to a citation that was part of the reading list of the course.
Associated Course Name	The name of a course that was active during the time the item was requested. The item belonged to a citation that was part of the reading list of the course.

For a video describing the Managed By fields, see the Analytics: Managed by Fields for Requests video.

Booking Request Details

The Booking Request Details table is a dimension table that stores details about requests of type booking, and includes parameters relevant only to booking requests. The primary key is ID.

Booking Request Details
Field	Description	Additional Information
Booking Start Time	The start time of the booking request.
Booking End Time	The end time of the booking request.
Booking Original Start Time	The original start time of the booking request.
Booking Original End Time	The original end time of the booking request.
Override Booking Request Policy	The policy of the override booking request.

Move Request Details

The Move Request Details table is a dimension table that stores details about move requests and includes parameters relevant only to move requests. The primary key is ORGANIZATION_ID.

Move Request Details
Field	Description	Additional Information
Move Call Number	The call number of the item in the library to which the item is moved.
Move Call Number Type	The call number type of the item in the library to which the item is moved.
Move Due Back	The due back date of the item in the library to which the item is moved
Move Item Policy	The item policy of the item in the library to which the item is moved
Library Code	The code of the library to which the item is moved.
Library Code (Active)	The code of the active (not deleted) library to which the item is moved.	This field is empty if the library is deleted.
Library Description	The description of the library to which the item is moved.
Library Name	The name of the library to which the item is moved.
Library Name (Active)	The name of the active (not deleted) library to which the item is moved.	This field is empty if the library is deleted.
Campus Code	The code of the campus to which the item is moved.
Campus Description	The description of the campus to which the item is moved.
Campus Name	The name of the campus to which the item is moved.
Location Code	The code of the location to which the item is moved.
Location Name	The name of the location to which the item is moved.
Location Type	The type of the location to which the item is moved.

Digitization Request Details

The Digitization Request Details table is a dimension table that stores details about digitization requests and includes parameters relevant only to digitization requests. The primary key is CODE.

Digitization Request Details
Field	Description	Additional Information
Approval Note	The approval note of the digitization request.
Approval Status	The approval status of the digitization request.
Requires Approval	Indicates whether the digitization request requires approval.
Requires Copyright Clearance	Indicates whether the digitization request requires copyright clearance.
Requires Deposit	Indicates whether the digitization request requires a deposit.
Reject Reason	The reject reason of the digitization request.
Partial Digitization Flag	Indicates whether the digitization request is full or partial.
Patron Digitization Flag	Indicates whether the patron made a digitization request.

Requester

The Requester table is a dimension table that stores details about the requester. The primary key is USER_ID.

The field descriptions can be found in the User Details shared dimension. For a list of user detail fields that can be configured to be anonymized, see Anonymizing Analytics Report Details.

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

Alma User Details Page – General Information

Request Type

The Request Type table is a dimension table that stores details about the request type. The primary key is CODE.

Request Type
Field	Description	Additional Information
Request Type Code	The request type code.	See the table below for a list of request type codes and descriptions
Request Type Description	The type of request.	See the table below for a list of request type codes and descriptions

The following table displays the Request Type Code and the corresponding description:

Request Type Codes and Descriptions
Request Type Code	Request Type Description
AcqWorkOrder	Acquisition technical services
BOOKING	Booking request
ELECTRONIC_TO_DIGITIZATION	Patron electronic digitization request
GENERAL_DIGITIZATION	General digitization request
GENERAL_HOLD	General hold request
LIBRARY_ELECTRONIC_DIGITIZATION	Library electronic digitization request
LIBRARY_PHYSICAL_DIGITIZATION	Library physical digitization request
MOVE_TO_PERMANENT	Move permanently
MOVE_TO_TEMPORARY	Move temporarily
PATRON_PHYSICAL	Patron physical item request
PHYSICAL_TO_DIGITIZATION	Patron digitization request
RESOURCE_SHARING_E2D_SHIPMENT	Ship digitally from electronic
RESOURCE_SHARING_ITEMLESS_P2D_SHIPMENT	Ship digitally
RESOURCE_SHARING_ITEMLESS_PHYSICAL_SHIPMENT	Ship physically
RESOURCE_SHARING_P2D_SHIPMENT	Ship digitally
RESOURCE_SHARING_PHYSICAL_SHIPMENT	Ship physically
RESTORE	Restore item
STAFF_ELECTRONIC_DIGITIZATION	Staff electronic digitization request
STAFF_PHYSICAL_DIGITIZATION	Staff digitization request
TRANSIT_FOR_RESHELVING	Transit for reshelving

Request Status

The Request Status table is a dimension table that stores details about the request status. The primary key is CODE.

Request Status
Field	Description	Additional Information
Request Status Code	The request status code.
Request Status	The status of the request.	Values can be: Active – The request is activated and there is an available item to fulfill the request. Completed – The request is completed (for example, for hold requests, when the item is loaned). Failed - The request has failed. (Alma failed to match an item to the Fulfillment request.) Ready – The request is still in the queue, not activated yet. Currently, there is no available item to fulfill the request. Rejected – The operator canceled an activated request from Alma. Rejected by Library – The request is canceled. The cancellation reason is Canceled at patron's request. Rejected by Patron – The request is canceled. The cancellation reason is Patron no longer interested.

Material Type

The Material Type table is a dimension table that stores details about the material type. The primary key is CODE.

Material Type
Field	Description	Additional Information
Material Type Code	The material type code.
Material Type Description	The material type specified in the request.	Values can be: Audiobook, Audio cassette, Book, Compact Disc, Flash Card, Bound Issue, Issue, DVD, and Other.

Request Date

The Request Date table is a dimension table that stores details about the request date. The primary key is DATE_KEY.

Request Date
Field	Description	Additional Information
Request Date	The date of the request.
Request Date Start of Week	The date of the first business day of the week
Request Date Week Number	The number of the week of the year
Request Time	The time of the request.	This field allows you to create reports such as the number of requests by hour at the circulation desk.
Request Date Full Month	The month and the year of the request.	For example: January 2014.
Request Date Month Key	The month key of the request (for example: 1, 2, 3).	This field is recommended if you want to sort by month.
Request Date Month	The month of the request.	For example: January, February).
Request Date Quarter	The quarter of the request.	For example: Q1, Q2.
Request Date Year	The year of the request.	For example: 2014.
Request Date Fiscal Month Key	The fiscal month key of the request (for example: 1, 2, 3).	This field is recommended if you want to sort by month.
Request Date Fiscal Year	The fiscal year of the request.	For example: 2014.
Request Date Filter	Used to filter report results by date.
New for August! Request Date Year-Month	The year and the month in a format such as 2023-1

Request Completion Date

The Request Completion Date is a dimension table that stores details about the request completion date. The primary key is DATE_KEY.

Request Date
Field	Description	Additional Information
Request Completion Date	The date of the request completion.
Request Completion Start of Week	The date of the first business day of the week
Request Completion Week Number	The number of the week of the year
Request Completion Month	The month of the request completion.	For example: January, February).
Request Completion Month Key	The month key of the request completion (for example: 1, 2, 3).	This field is recommended if you want to sort by month.
Request Completion Fiscal Month Key	The fiscal month key of the request completion (for example: 1, 2, 3).	This field is recommended if you want to sort by month.
Request Completion Full Month	The month and the year of the request completion.	For example: January 2014.
Request Completion Quarter	The quarter of the request completion.	For example: Q1, Q2.
Request Completion Year	The year of the request completion.	For example: 2014.
Request Completion Fiscal Year	The fiscal year of the request completion.	For example: 2014.
Request Completion Date Filter	Used to filter report results by date.
New for August! Request Completion Year-Month	The year and the month in a format such as 2023-1

Owning Library

The Owning Library table is a dimension table that stores details about the library/institution that created request. The primary key of the table is ORGANIZATION_ID.

The field descriptions are the same as those of the Library Unit shared dimension:

Library Unit
Field	Description	Field Location in Alma	Additional Information	Data Type	Data Size
Library Code	The library code	Configuration > General > Libraries > Add a Library or Edit Library Information > Libraries tab > Path [the text after the period]		VARCHAR	50
Library Code (Active)	The code of active (not deleted) libraries	Configuration > General > Libraries > Add a Library or Edit Library Information > Libraries tab > Path [the text after the period]	The same as Library Code without deleted libraries.	VARCHAR	50
Library Name	The library name	Configuration > General > Libraries > Add a Library or Edit Library Information > Libraries tab The label in Alma is Organization Unit Name.		VARCHAR	255
Library Name (Active)	The library name of active (not deleted) libraries	Configuration > General > Libraries > Add a Library or Edit Library Information > Libraries tab The label in Alma is Organization Unit Name.	The same as Library Name without deleted libraries.	VARCHAR	255
Library Description	The library description	Configuration > General > Libraries > Add a Library or Edit Library Information > Libraries tab The label in Alma is Description.		VARCHAR	100
Unit Type	The type of organization unit	Configuration > General > Libraries > Add a Library or Edit Library Information > Libraries tab The label in Alma is Organization Unit Type.	Values can be Institution/Library	VARCHAR	20

Date Needed By

The Date Needed By table is a dimension table that stores details about the date needed by. The primary key is DATE_KEY.

Date Needed By
Field	Description	Additional Information
Date Needed Month	The month of the date that the request is needed.
Date Needed Start of Week	The date of the first business day of the week
Date Needed Week Number	The number of the week of the year
Date Needed Month Key	The month key of the date that the request is needed.
Date Needed Full Month	The full month of the date that the request is needed.
Date Needed Fiscal Month Key	The fiscal month key of the date that the request is needed.
Date Needed Quarter	The quarter of the date that the request is needed.
Date Needed Year	The year of the date that the request is needed.
Date Needed Fiscal Year	The fiscal year of the date that the request is needed.
Date Needed Date	The date that the request is needed.
Date Needed Date Filter	Used to filter report results by date.
New for August! Date Needed Year-Month	The year and the month in a format such as 2023-1

Bibliographic Details

The Bibliographic Details table is a dimension table that stores details about the bibliographic details. The primary key 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: Removes non filing text. Removes <<>> and anything between them. Removes these characters: []\|,.;:" Changes these characters to a space: !@#$%^&*()_+-={}\<>?/~' Changes characters to lowercase. 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
Title Committed to Retain	Indicates (Y/N) if the bibliographic record is marked as Committed to Retain	Configurable from Configuration > Resources > Collection Retention > Bibliographic Collection Retention Definition. For more information, see Bibliographic Record Retention.
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 Field 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	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	The creation date. Date fields can consist of a partial date, such as just the year or a month and year.
Creation Date (Calendar)	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	The name of the user that created the record
Dewey Classification	The Dewey Classification
Dewey Classification Top Line	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	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. (New for August!) If you want to have the labels of the local parameters displayed in analytics, configure the analytics_display_local_params parameter (Configuration > Analytics > General Configuration > Other Settings) to true.
Managed by Provider	Indicates if the electronic resource is managed by the provider
MMS ID	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	The modification date. Date fields can consist of a partial date, such as just the year or a month and year.
Modification Date (Calendar)	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	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
Accession Number	A sequential code used to file items on the shelf.
Alternative Call Number Type	An alternative call number type (Note that Alternative Call Number=Item Call Number.)
Barcode	The unique identifier of the specific physical item
Base Status	Indicates the availability of the item in its permanent location (in place/not in place)
Call Number Normalized	The normalized call number
Chron I	The main level of chronology - usually the year
Chron J-M	Additional chronology fields
Copy ID	When multiple copies of the same title exist at the same library/location, the copy ID is used to identify each of the copies.
Creation Date	The date that the physical item was created.
Creator	the username of the operator that created the physical item
Description	Description of the item
Dewey Top Line	Store the first 3 digits of the Dewey classification
Display Alternative Call Number	A normalized alternative call number for display (Note that Alternative Call Number=Item Call Number.)
Display Temp Call Number	A normalized temporary call number for display
Due Back Date	Indicates the date that an item in a temporary location is due back to its permanent location	Date fields can consist of a partial date, such as just the year or a month and year.
Due Back Date (Calendar)	Indicates the date that an item in a temporary location is due back to its permanent location	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.
Enum A	The main level of enumeration - usually the volume
Enum B-H	Additional enumeration fields
Expected Receiving Date	The date when a purchased item is expected to arrive at the library	Date fields can consist of a partial date, such as just the year or a month and year.
Expected Receiving Date (Calendar)	The date when a purchased item is expected to arrive at the library	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.
Fulfillment Note	The fulfillment note
Has Committed to Retain	Indicates if the library has committed to retain the item
Holding ID	The unique identifier of the holding
Institution ID	The ID of the institution
Internal Note 1-3	Internal notes 1-3
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
Is Magnetic	Whether the item is magnetic material or not.
Item Policy	Defines the conditions under which a request for this item can be fulfilled
Last Loan Date	The last time the item was loaned
Lifecycle	Indicates whether the item is active or deleted
Material Type	Describes the nature of the material represented by the item record
MMS ID	The MMS ID of the library.
Modification Date	The date that the physical item was modified.
Modified By	The user that modified the physical item.
Num of Items	Stores the number of items (one for each item)
Originating System ID	The ID of the item in the source system from which it has been imported
Permanent Call Number	A code used to file the items on the shelf
Permanent Call Number	The permanent call number
Permanent Call Number Type	The call number type.	Possible values are: Source specified in subfield $2 None Superintendent of Documents classification Shelved separately Shelving control number Other scheme National Library of Medicine classification Dewey Decimal classification Unknown Library of Congress classification Title
Permanent LC Classification Code	Stores the letters that the LC class number start with such as BF, QA, etc.
Permanent LC Classification Number	Stores the numbers that follow the letters until the first period that is followed by a letter
Permanent LC Classification Top Line	Stores the LC class number top line that represents the code and numbers until the first period followed by a letter.	For example, when lc_class_number is NB933.F44, the top line is NB933).
Permanent Physical Item Location Code	The code of the physical item location
Physical Item ID	The ID of the physical item
PO Line ID	The ID of the PO line.
Process Type	When the item is being processed (acquisition/loan/bindery/etc) this indicates the type of processing
Provenance Code	A code used to identify separate items that belong to different groups (but may be shelved together)
Receiving Date	The date the material was actually received/activated for the first time
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.
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
Statistics Note 1-3	Holds statistic notes
Summary Holding	Free-text enumeration and chronology data
Temp Call Number Type	A call number type provided when the item is in a temporary location
Temp Physical Location	The temporary physical location (at the time at which the report is run)
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.
Temporary Library	The temporary library
Temporary Library Code (Active)	The active (not deleted) temporary library code
Temporary Library Name (Active)	The active (not deleted) temporary library name
Time Loaned - not sum	The amount of time that the physical item was loaned

Request for Course

The Course table is a dimension table that stores details about the course, including the course name, the course year, and the course creator. The primary key of the table is COURSE_ID.

(Leganto only) Currently, when reading lists can be associated with multiple courses, only the first course appears in Analytics. All courses associated with a reading list will appear in Analytics in an upcoming release (at which point all data, past and present, will appear).

Courses
Field	Description	Additional Information
Academic Department	The academic department of the course
Academic Department Description	The description of the academic department of the course
Course Code	The code of the course
Course Created By	The creator of the course
Course Creation Date	The date that the course was created
Course Instructor	The name of the course instructor	If there is more than one instructor, the names are separated by a semicolon.
Course Instructor Primary Identifier	The primary identifier of the course instructor
Course Instructor with Primary Identifier	The course instructor with the course instructor's primary identifier	This field is useful when a course has more than one instructor. This field allows you to display the instructors together with their primary identifiers.
Course Modification Date	The date that the course was modified
Course Modified By	The person who modified the course
Course Name	The name of the course
Course Section	The section of the course
Course Status	The status of the course
Course Submit List By	The date by which all reading lists for the course should be submitted
Course Term	The term of the course
Course Visibility	Indicates if the course is archived or unarchived
Course Year	The year of the course
No list Expected	Indicates if the No List Expected checkbox for the course is selected or not	Possible values: Checked and Unchecked. You select this checkbox to alert the librarian that this course deliberately does not include a reading list. For more information on this checkbox, see Indicating that Courses Deliberately Have No Reading List.
Number of Participants	The number of participants in the course
Processing Department	The processing department of the course
Rolled Over From Code	The code of the course from which the course was rolled over
Weekly Hours	The weekly hours of the course

Shared Dimensions with Other Subject Areas

For information concerning shared dimensions with other subject areas, see Shared Dimensions.

Vendor

The Vendor table is a dimension table that stores details about vendors. The data is taken from the PO Line for transactions of type encumbrance and from Invoice Line for transactions of type expenditure. Transactions of type allocation are not related to any particular vendor; therefore, they return a NULL/unknown value for all vendor fields. Vendors are the expected suppliers of materials ordered by the library.

Vendor
Field	Description	Additional Information
Vendor Code	Stores the vendor code unique to the institution	All the vendors that have been on the order, not just the active vendor.
Vendor Name	Stores the vendor name
Creation Date	The date the vendor was created.
Modification Date	The date the vendor was modified.
Additional Code	A code in addition to the vendor code.
ERP Code	A code used by an institution's financial system, such as the Enterprise Resource Planning (ERP) system
Vendor Status	The status of the vendor	Possible values: Active Inactive Deleted

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.	Configured from Configuration > General > Add a Library or Edit Library Information > Summary tab. The label in Alma is Code located on the right pane.
Institution Name	The name of the institution.	Configured from Configuration > General > Add a Library or Edit Library Information > Summary tab. The label in Alma is Organization unit name.
Institution Timezone	The timezone of the institution.	The timezone is set during implementation.
Data Available As Of	When the institution data became available in analytics.	Displayed at the bottom of the main Analytics menu.
Data Updated As Of	When the institution data was taken from the Alma database.	Displayed at the bottom of the main Analytics menu.

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.