Requests
Using the Requests subject area, the Design Analytics user may create reports and dashboards that help to answer the following types of business questions:
- How many items were requested per patron type?
- How many items were requested per material type?
- What is the fill rate for requests per material\patron type?
- How long does it take from the time that the request is placed until it is fulfilled?
- Which titles have the highest demand? (based on open requests)
Star Diagram – Requests
Report Creation Tips
Requests are linked to the MMSID of the item, so when creating reports for requests, use the MMSID 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 and can either be completed as fulfilled or as canceled.
Typically you would run different reports for each population. For example - for active requests you can run a report on titles with high number of requests, and for completed requests you can run a trend analysis of average time to patron collection.
Both active and inactive rejected requests appear in reports, although inactive requests cannot be retrieved in the Alma UI. To prevent inactive requests from appearing in reports, the requests must be deleted. To delete inactive requests, contact Ex Libris Support.
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.
| 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.
.
| 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.
.
| 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 step. (The amount of time that the request was waiting for the remote storage facility to 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.
| Field | Description | Additional Information |
|---|---|---|
| Active Request Flag | An active request is a request that is still in process. | This flag is used to filter based on currently active requests (typically used for reports on titles with high demand) or completed requests (typically used for trend analysis and fill rate calculations). |
| Cancellation Reason | The cancellation reason inserted when a request is cancelled. | |
| Current Process | The name of the current activity. | Possible values are:
For a list of the request statuses as they appear in Alma, see Creating a Request. |
| Creator | The creator of the request. | 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. |
| In Transit Flag | This field reflects an internal process and not the In Transit request status. Y indicates that the item is in transit to re-shelving after a patron returns the item. N indicates that the requested item is on its way to the requester (circulation desk/work department). | |
| 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 if a pickup slip was printed. | |
| Related to Resource Sharing Request | Indicates if the request is related to a resource sharing request. | |
| Request ID | The ID of the request. | |
| Search Type | Indicates whether the request is item level or title level. | |
| Status Note | The status note. | |
| Triggered Recall | Indicates if the request triggered a recall. | |
| 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 work order 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.
| 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.
| 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 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. | |
| 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.
| 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 if the digitization request requires approval. | |
| Requires Copyright Clearance | Indicates if the digitization request requires copyright clearance. | |
| Requires Deposit | Indicates if the digitization request requires a deposit. | |
| Reject Reason | The reject reason of the digitization request. | |
| Partial Digitization Flag | Indicates if the digitization request is full or partial. | |
| Patron Digitization Flag | Indicates if 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.
| 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 Alma User Details Page – General Information. |
| User Type | Stores the values Internal and External. |
See the field location in Alma in Alma User Details Page – General Information. |
| User Group | Stores the group with which the user is associated such as Faculty, Graduate, or Student | See the field location in Alma in Alma User Details Page – General Information. |
| User Record Type | Indicates if the user is a Public User or a Staff User | See the field location in Alma in Alma User Details Page – General Information. |
| First Name | Stores the user’s first name | See the field location in Alma in Alma User Details Page – General Information. |
| Last Name | Stores the user’s last name | See the field location in Alma in Alma User Details Page – General Information. |
| Middle Name | Stores the middle name of the user | See the field location in Alma in Alma User Details Page – General Information. |
| Job Description | Stores free-form text that describes the function of the user in the library | See the field location in Alma in Alma User Details Page – General Information. |
| 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 Alma User Details Page – General Information. |
| Gender | Stores male or female | See the field location in Alma in Alma User Details Page – General Information. |
| Birth Date | Stores the birth date of the user | See the field location in Alma in Alma User Details Page – General Information. |
| Campus Code | Stores the campus code of the user | See the field location in Alma in Alma User Details Page – General Information. |
| Status Date | Stores the date on which the patron was registered in the university | See the field location in Alma in Alma User Details Page – General Information. |
| Status | Indicates if the user is active | See the field location in Alma in Alma User Details Page – General Information. |
| Creation Date | Stores the date that the user was created in the system | See the field location in Alma in Alma User Details Page – General Information. |
| Modified By | Stores the name of the user that modified the user record | See the field location in Alma in Alma User Details Page – General Information. |
| Modification Date | Stores the date of the modification of the user record | See the field location in Alma in Alma User Details Page – General Information. |
| 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 Alma User Details Page – General Information. 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 Alma User Details Page – General Information. |
| Default Language | Stores the default language of the user | See the field location in Alma in Alma User Details Page – General Information. |
| 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 Alma User Details Page – General Information. |
| 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. Choosing 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. | |
| Identifier 2 | Stores identifier 2. See details in "identifier 1" above. | |
| Statistical Categories 1-5 | These fields allow you to map five statistical categories. This allows you to filter reports based on advanced user information typically stored in the statistical category fields. | |
| 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. |
Alma User Details Page – General Information
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.
| Field | Description | Additional Information |
|---|---|---|
| Request Type Code | The request type code. | |
| Request Type Description | The type of request. Electronic Digitization Request, Move Permanently, Move Temporarily, Patron Physical Item Request, Patron | Possible values are: Binding, Booking Request, Patron Electronic Digitization Request, General Hold Request, Library |
Request Status
The Request Status table is a dimension table that stores details about the request status. The primary key is CODE.
| Field | Description | Additional Information |
|---|---|---|
| Request Status Code | The request status code. | |
| Request Status | The status of the request. | Values can be:
|
Material Type
The Material Type table is a dimension table that stores details about the material type. The primary key is CODE.
| 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.
| Field | Description | Additional Information |
|---|---|---|
| Request Date Month | The month of the request. | For example: January, February). |
| 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 Full Month | The month and the year of the request. | For example: January 2014. |
| 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 | The date of the request. | |
| 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 Completion Date
The Request Completion Date is a dimension table that stores details about the request completion date. The primary key is DATE_KEY.
| Field | Description | Additional Information |
|---|---|---|
| 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 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 Date | The date of the request completion. |
Owning Library
The Owning Library table is a dimension table that stores details about the library unit. The primary key is DATE_KEY.
The field descriptions are the same as those of 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 |
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.
| Field | Description | Additional Information |
|---|---|---|
| Date Needed Month | The month of the date that the request is needed. | |
| 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 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 Date | The date that the request is needed. |
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.
| 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 |
| MMS ID | The MMS ID of the library. | |
| PO Line ID | The ID of the PO line. | |
| Holding ID | The unique identifier of the holding | |
| Permanent Call Number | A code used to file the items on the shelf | |
| 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). |
| Accession Number | A sequential code used to file items on the shelf. | |
| 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. | |
| Summary Holding | Free-text enumeration and chronology data | |
| Permanent Call Number Type | The call number type. | Possible values are:
|
| 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. | |
| Institution ID | The ID of the institution | |
| Alternative Call Number Type | An alternative call number type | |
| Description | Description of the item | |
| Num of Items | Stores the number of items (one for each 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 | |
| Display Alternative Call Number | A normalized alternative call number for display | |
| Call Number Normalized | The normalized call number | |
| Dewey Top Line | Store the first 3 digits of the Dewey classification | |
| Physical Item ID | The ID of the physical item | |
| Originating System ID | The ID of the item in the source system from which it has been imported | |
| Permanent Physical Item Location Code | The code of the physical item location | |
| Temporary Physical Location In Use | Whether the item is in a temporary location or in a permanent location | |
| Temporary Library | The temporary library | |
| Temporary Physical Location | The temporary physical 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 |
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.
| Field | Description | Additional Information |
|---|---|---|
| Course Code | The code of the course | |
| Course Name | The name of the course | |
| Course Status | The status of the course | |
| Course Year | The year of the course | |
| Course Term | The term of the course | |
| Academic Department | The academic department of the course | |
| Processing Department | The processing department of the course | |
| Number of Participants | The number of participants in the course | |
| Weekly Hours | The weekly hours of the course | |
| Searchable ID 1-3 | Searchable ID 1-3 of the course | |
| Course Creator | The creator of the course | |
| Course Modified By | The person who modified the course | |
| Course Modification Date | The date that the course was modified | |
| Course Section | The section of the course | |
| Course Create 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. |
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.