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

    Funds Expenditure

    Analytics
    Using the Funds Expenditure subject area, the Design Analytics user may create reports and dashboards that help to answer the following types of business questions:
    • How much was expended last year per month?
    • What is the comparison of encumbrances versus expenditures versus allocations?
    • How much was expended per item material type or per item type?
    • What is the share of E/P expenditures out of the total expenditures?
    • How much was paid per vendor?
    • How much was expended per reporting code?
    • How much was expended per fund, ledger, or library out of the allocations?
    • How much was expended per library?
    fund_expenditures_star_diagram.png
    Star Diagram - Funds Expenditure
    • Do not create reports with fields from the Funds Expenditure subject area and attribute fields (yellow fields) from the Physical Items subject area or you will receive incorrect results.
    • When PO Lines, POs, Invoices, and Licenses are deleted in Alma, they are no longer available in Alma Analytics.
    • Information on PO lines without transactions is available in Alma Analytics, except for migrated PO lines without transactions, which can be added by contacting Ex Libris Support.

    Field Descriptions

    The following sections present the fields available in Funds Expenditure.
    funds_expenditure_field_descriptions.png
    Funds Expenditure - Field Descriptions

    Fund Transactions

    The Fund Transactions table is the fact table that stores all the measures (activities) of specific transactions. There are three types of transactions:
    • expenditure
    • allocation
    • encumbrance
    Each transaction is associated with a fund and each fund is associated with a fiscal period:
    • The allocation transaction is made on the fund level and is used to allocate budgets to a fund
    • The encumbrance transaction is created from the PO line. Another transaction with negative amounts is made after the invoice line is created. In a common scenario, the encumbrance amount is zero after the invoice arrives. Sometimes there are differences in the amounts between the two transactions, so that the remaining encumbrance amount is not always zero.
    • The expenditure transaction is created from the invoice line and represents the actual payment for the item

    Report Creation Tips

    Only funds with transactions appear in reports created with the fields of the Fund Transactions subject area.
    • Creating a report based on expenditures
      Because of the way encumbrance transactions are created (with a plus and minus transaction), when building a report on the transaction level, it is common to use the Transaction Item Type = "expenditure" filter. Many of the out-of-the-box reports are built this way.
    • Combining invoice and PO amounts in reports
      The fact that in the same SA there are amounts from the transaction level as well as amounts from the PO and invoice level can create duplications when combined together. To ensure that you get correct results in your reports, follow the below guidelines:
      • When adding the PO Line Total Price field, also add the PO Line Reference field to your report columns. (It can be excluded from display, but it has to be selected.) Additionally, you must set the Aggregation Rule for the PO Line Total Price field to Sum (found by selecting Edit Formula).
      • When adding the Invoice Line Total Price field or the Transaction Amount field, also add the Invoice Line > Invoice Line-Unique Identifier field to your report columns. (It can be excluded from display, but it has to be selected.)
      The following is an example of the invoice line amount in Alma:
      invoice_line_amount.gif
      Invoice Line Amount
      If you create a report with invoice line amounts as well as amounts from the transaction level (in this example the remaining encumbrance) you get incorrect results:
      invoice_line_amt_incorrect.gif
      Invoice Line Total Price - Incorrect
      If you add the invoice number, the results are correct:
      invoice_line_amt_correct.gif
      Invoice Line Total Price - Correct
    • Creating a report that displays the sum of invoice lines in separate groups
      To receive correct totals of invoice lines when divided into groups of invoices, edit the formula of the Invoice Line Total Price column and set the aggregation rule to Sum.
    The following table describes the fields in the Fund Transactions dimension.
    Fund Transactions
    Field Description Additional Information
    Transaction Amount Stores the transaction amount Typically you filter the report to show amount per transaction type.
    Transaction Allocation Amount Stores the transaction allocation amount Typically you filter the report to show amount per transaction type.
    Transaction Encumbrance Amount Stores the transaction encumbrance amount Typically you filter the report to show amount per transaction type.
    Transaction Expenditure Amount Stores the transaction expenditure amount of all types (electronic, physical, and general)  Typically you filter the report to show amount per transaction type.
    Transaction Expenditure Amount of type Electronic Format Stores the transaction expenditure amount of type electronic format
    For a video explaining how to use these fields, see Analyze Fund Expenditures by Physical or Electronic Types.
    Transaction Expenditure Amount of type General Format Stores the transaction expenditure amount of type general format
    Transaction Expenditure Amount of type Physical Format Stores the transaction expenditure amount of type physical format
    Transaction Foreign Currency Amount The transaction amount when it is in a currency other than dollars.  
    Transaction Foreign Currency Encumbrance Amount The transaction encumbrance amount when it is in a currency other than dollars.  
    Transaction Foreign Currency Expenditure Amount The transaction expenditure amount when it is in a currency other than dollars.  
    Transaction VAT Stores the value-added tax  
    Transaction Cash Balance The Allocated Balance - the Expenditure Balance  
    Transaction Available Balance The Allocated Balance - the Expenditure Balance - th e Encumbered Balance  
    PO Line Quantity Stores the number of items in the PO line. You must add the PO Line Reference field to the report to ensure that the PO Line Quantity is calculated correctly.
    PO Line Total Price Stores the total price (includes additional charges, if any). Add the PO Line Reference field to the report to ensure that the PO Line Total Price is calculated correctly.
    PO Line Pct Stores 100 times the Transaction Amount/PO Line Total Price  
    Number of POLs The number of PO lines of all types (electronic, physical, and general)  
    Number of POLs of type Electronic Format The number of PO lines of type electronic Format  
    Number of POLs of type General Format The number of PO lines of type general format  
    Number of POLs of type Physical Format The number of PO lines of type physical format  
    Number of POLs without Transactions The number of PO lines without transactions  
    Invoice Line Quantity Stores the number of elements ordered in the invoice line.  
    Invoice Line Total Price Stores the total amount (includes additional charges, if any). Add the Invoice Line > Invoice Line-Unique Identifier field to the report to ensure that the Invoice Line Total Price is calculated correctly.
    Invoice Line Pct Stores 100 times the Transaction Amount / Invoice Line Total Price  
    % remaining (Considering expended and encumbered) (Available Balance / Allocated Balance) * 100  
    % remaining (Considering only expended) (Cash Balance / Allocated Balance) * 100  

    Fund Transactions Details

    The Fund Transactions Details table is the dimension table that stores more details about specific transactions. The primary key is FUND_TRANSACTION_ID.
    Fund Transactions Details
    Field Description Additional Information
    Transaction ID The ID of the transaction  
    Transaction Date Stores the date that the transaction occurred  
    LC Classification Code Stores the LC classification code, the letters with which the LC class number starts such as BF or QA  
    LC Classification Number Stores the LC classification number, that is, the numbers followed by the letters until the first period followed by a letter  
    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 Top Line Store the first 3 digits of the Dewey Classification  
    Transaction Item Type Includes the allocation types available in Alma: Allocation, Encumbrance, and Expenditure, and Non-transactional, which indicates that the PO lines do not have a transaction because no funds are associated with them.  
    Transaction Item Sub Type Displays the relevant Transaction Item Sub-Type of the specific Transaction Item Type.  
    • The sub-types for Allocation are Allocation and Transfer.
    • The sub-types for Encumbrance are Encumbrance and Disencumbrance
    • The sub-type for Expenditure is Expenditure.
     
    Fund Transaction Reference A number that can be used to reference a particular allocation to a fund, set from the Transaction tab of the Funds and Ledgers page (Acquisitions > Acquisitions Infrastructure > Funds and Ledgers).  
    Exchange Rate The exchange rate between the fund's currency and that of the invoice.  
    Exchange Rate Date The date that the exchange rate was calculated.  
    Explicit Ratio A set exchange rate between the fund's currency and that of the invoice.  
    Source Amount The amount of the source currency.  
    Source Currency The currency from which you want to convert the invoice currency.  
    Related Record Indicates the related resource sharing record. Currently, only related records of type Resource Sharing are included in this analytics field.

    Transaction Dates

    Since each transaction is associated with a fund and each fund is associated with a specific fiscal period, this date dimension includes a logic that changes the actual dates if they do not fall into the fiscal year assigned to the fund according to the following logic:
    • If the transaction date is greater than the fund end fiscal date, the transaction date is set to the fund end fiscal date
    • If the transaction date is less than the fund start fiscal date, the transaction date is set to the fund start fiscal date
    For more information about improvements made to the date fields, see the Analytics: Date Fields Improvements video (4:27 mins).
    Transaction Dates
    Field Description Additional Information
    Transaction Date Month Key Stores the month of the date in number format such as 2 for February This field is useful when you want to sort by the month, which does not work properly when using the alphabetical field.
    Transaction Date Start of Week The date of the first business day of the week  
    Transaction Date Week Number The number of the week of the year  
    Transaction Date Month Stores the month of the date in month description format such as February  
    Transaction Date Full Month Stores the month and the year of the date in a display format such as Feb 12 This field is useful when comparing data on a month basis between years.
    Transaction Date Quarter Stores the quarter of the date in a display format such as Q1  
    Transaction Date Year Stores the year of the date in number format such as 2012  
    Transaction Date Fiscal Month Stores the fiscal month of the date in a number format such as 9 for September  
    Transaction Date Fiscal Full Month Stores the fiscal month and the year of the date in a display format such as Feb 12 This field is useful when comparing data on a month basis between year
    Transaction Date Fiscal Quarter Stores the fiscal quarter of the date in a display format such as Q1  
    Transaction Date Fiscal Full Quarter Stores the fiscal quarter and the year of the date in a display format such as Feb 12  
    Transaction Date Fiscal Year Stores the fiscal year of the date in a string format such as 2012. If the fiscal year description is stored in the institution fiscal period configuration table, this value is taken from there.
    Transaction Date Fiscal Year Desc Stores the fiscal year of the date in string format such as 2012. If the fiscal year description is stored in the institution fiscal period configuration table, this value is taken from there.
    Transaction Date Stores the transaction date in a date format such as 2/29/2014.  

    Fiscal Period

    The Fiscal Period table is a dimension table that stores details about the fiscal periods defined for the institution.
    Fiscal Period
    Field Description Additional Information
    Fiscal Period Start Date Stores the start date of the fiscal period of the institution  
    Fiscal Period End Date Stores the end date of the fiscal period of the institution Date fields can consist of a partial date, such as just the year or a month and year.
    Fiscal Period End Date (Calendar) Stores the end date of the fiscal period of the institution 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.
    Fiscal Period Start End Stores the start and end dates of the fiscal period of the institution Date fields can consist of a partial date, such as just the year or a month and year.
    Fiscal Period Start End (Calendar) Stores the start and end dates of the fiscal period of the institution 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.
    Fiscal Period Description Stores the description of the fiscal period as stored in the FundLedgerFiscalPeriodTable mapping table or stores the fiscal year if the description is empty  
    Fiscal Period Status Stores the status of the fiscal period such as Active, Inactive, Draft, or Close  
    Fund Fiscal Period Filter The filter on the fiscal period Possible values:
    • Current fiscal period
    • Previous fiscal period
    • Two fiscal periods ago
    fund_and_ledger_fiscal_period_new.png
    Acquisitions Configuration - Fund and Ledger Fiscal Period

    Library Unit

    The Library Unit table is a dimension table that stores details about the library that manages acquisitions. The data for this dimension in the Funds Expenditure subject area comes from the POL owner.
    The field descriptions can be found in the Library Unit shared dimension.
    Library Unit
    Field Description Additional Information
    Library Code Stores the library code  
    Library Code (Active) Stores the code of active (not deleted) libraries This field is empty if the library is deleted.
    Library Name Stores the library name  
    Library Name (Active) Stores the library name of active (not deleted) libraries This field is empty if the library is deleted.
    Library Description Stores the library description  
    Unit Type Store the type of organization unit Values can be Institution/Library

    Reporting Code

    The Reporting Code table is a dimension table that stores details about the reporting code and transactions where it is used. The primary key of the table is CODE.
    Each institution may categorize transactions in different ways. Usually this will be done by applying a unique reporting code.
    Reporting Code
    Field Description Additional Information
    Reporting Code Stores the reporting code that is used. Taken from the the fund transaction
    Reporting Code - 1-5 Five fields that store the reporting codes.  
    Reporting Code Description -1-5 Five fields that store the description of the 5 reporting code fields  

    LC Classifications

    Users may view measures accumulated to the relevant group, including expenditures, encumbrances, and allocations grouped by classifications.
    The field descriptions can be found in the LC Classifications shared dimension.

    For Physical Items, Alma takes LC classification information from the holdings record level. For all other subject areas, it is taken from the bibliographic record level.

    Ex Libris works with content providers worldwide to enrich the metadata available in the Alma Community Zone. To enrich the journal/serial content in the CZ, we work directly with the Library of Congress CONSER feed for electronic serials, which we match against our knowledge base to enrich with all of the relevant metadata fields that they supply (for more details, see Community Zone Serial Records Enrichment). We receive weekly updates from CONSER and enrich the CZ records with all relevant metadata, including the 050 fields (when available).

     

    In the case of book content, we work with multiple providers who are willing to share their metadata with the Alma community globally (for more details, see Community Zone Monograph Records Enrichment). If you have local access to these classifications, you may want to consider working with the local extension for these records whenever an update is not available. (For more details, see Working with Local Extension Fields for Community Zone-linked Records)

    LC Classifications
    Field Description Additional information
    Start Range Stores the start range of the group such as PS501  
    End Range Stores the end range of the group such as PS689  
    Classification Code Stores the letters in the beginning of the range such as PS
    • In the Fulfillment subject area, if there is more than one classification code, the last one appears.
    • The Classification Code comes from the bibliographic record, except for in the Physical Items subject area where it comes from the holdings record.
    Start Range Number Stores the numbers that come after the letter in the start range  
    End Range Number Stores the numbers that come after the letter in the end range  
    Group1 Stores the name of the first level  
    Group2 Stores the name of the second level  
    Group3 Stores the name of the third level  
    Group4 Stores the name of the fourth level  
    Group5 Stores the name of the fifth level  
    Classifications Stores the Hierarchy column that allows the user to drill down from the first level of the classification to the fourth level. Using this column provides the user with the option to view the accumulative measures. Note that the fifth level is not included in this field.  

    Dewey Classifications

    Users can view measures accumulated to the relevant group, including expenditures, encumbrances, and allocations grouped by classifications. The field descriptions can be found in the Dewey Classifications shared dimension.
    Dewey Classifications
    Field Description Additional information
    Dewey Number Holds the first 3 digits of the Dewey Classification.
    The Dewey Number comes from the bibliographic record, except for in the Physical Items subject area where it comes from the holdings record.
    Group1 Stores the name of the first level.  
    Group2 Stores the name of the second level.  
    Group3 Stores the name of the third level.  
    Dewey Classifications Stores the Hierarchy column that allows the user to drill down from the first level of the Dewey Classification to the third level. Using this column provides the user with the option to view the accumulative measures (loans or returns) in each level of the hierarchy.  

    Other Classifications

    The Other Classifications table is a dimension table that contains fields for classification systems other than LC and Dewey. Like LC and Dewey classifications, you can drill down to different levels, or groups. At each level, the measures associated with the selected group are displayed.
    Other Classifications
    Field Description Additional Information
    Chinese Classifications
    Classification Code The Chinese classification code If the code is not found or in an incorrect format Unknown is displayed.
    Group 1-7 (Chinese) Stores the name of the levels of classification in Chinese  
    Group 1-7 (English) Stores the names of the levels of classification in English  
    Chinese Classifications (Taiwan)
    Classification Code The Chinese (Taiwan) classification code If the code is not found or in an incorrect format Unknown is displayed.
    Group 1-3 (Chinese-Taiwan) Stores the name of the levels of classification in Chinese-Taiwan  
    Group 1-3 (English) Stores the names of the levels of classification in English  
    NLM Classifications
    NLM Classification Code Stores the NLM classification code
    • If the code is not found or in an incorrect format, Unknown is displayed.
    • If there are multiple codes, only the first is displayed.
    • Taken from the 060 or 096 fields of the bibliographic record.
    NLM Classification Number Stores the numbers that come after the NLM letter code  
    NLM Group 1-5 Stores the names of the levels of classification  
    U.S. SuDoc Classifications
    U.S. SuDoc Classification Code

    Stores the SuDoc Classification code with which to find a match to the SuDoc Classification code from the bibliographic record

    • The SuDoc Classification Code is derived from government document fields in the bibliographic record.
    • If the code is not found or in an incorrect format, Unknown is displayed.
    • If there are multiple codes, only the first is displayed.
    U.S. SuDoc Classification Number Stores the numbers that come after the SuDoc letter code The SuDoc Classification Number is derived from the published SuDoc Classification table on the Federal Depository Library Program (GPO) Website
    U.S. SuDoc Agency Stores the name of the top level (parent) U.S. government agency Unlike other classification systems, the SuDoc system groups publications together by the publishing agency, that is, a U.S. government agency.
    U.S. SuDoc SubAgency Stores the name of subordinate bureaus and divisions of the parent U.S. agency A subagency is displayed if a publication is published by a subordinate bureau or division within a parent agency.

    If the top level agency is the publishing agency, then that agency is also listed as the subagency.

    U.S. SuDoc Title Stores the name of either the title of the publication or indicates miscellaneous publications Title designates either a specific publication title or category of the publication.

    Fund 

    The Fund table is a dimension table that stores the details about the fund with which the transaction is associated. The primary key of the table is FUND_LEDGER_ID.
    There are the following types of funds:
    • Ledger
    • Summary
    • Allocated Fund
    Funds are kept in a parent-child relationship so that each fund has a connection to its parent.
    funds_hierarchy_example.gif
    Funds Hierarchy Example

    Creating Reports According to Fund Type

    You can create reports according to fund type. If the procedures in this section are not implemented, the sums of all of the fund types may be added together in the transaction amount.
    • To create a report displaying funds of just one type, filter the Fund Type column according to Ledger, Allocated fund, or Summary fund:
      filter_by_fund.png
      Filter By Fund
    • To create a report showing all of the fund types, add a column that displays any unique identifier of the fund, such as Fund Ledger Code:
      fund_ledger_code.png
      Fund Ledger Code
    Fund
    Field Description Additional Information
    Fund Currency Stores the fund's currency  
    Fund Code Stores the fund code unique to each institution and fiscal period This code is not unique, since each year another entry is made for the same code
    Fund ID Stores the unique ID of the fund  
    Fund Name Stores the fund name  
    Fund Description The contents of the Description field of the Summary tab of the fund  
    Fund Status Indicates if the fund is active or inactive  
    Fund Note Stores the note  
    Fund Owner Code The owner code of the fund   
    Fund Owner Name The owner name of the fund   
    Parent Fund Name Stores the parent fund name  

    Parent Fund Code

    Stores the parent fund code  
    Parent Fund ID Stores the unique ID of the fund's parent  
    Fund Type Stores one of the following types:
    • Ledger
    • Summary
    • Allocated
     
    Fund Area Code Stores values defined in the Fund Types table and attributed to funds, for example: Endowed, Gift, General, Grant, Income, and Resource Sharing. For more information, see Configuring Fund Types. This field is named Fund type in Alma and is created via a mapping table. See the figures Fund and Ledger - Summary Details and Fund Types, below.
    Fund Area Description Stores the fund area description  
    Fund External ID The fund ID used by an external system.  
    Fund Ledger Hierarchy Stores the Hierarchy column that allows the user to drill down from the ledger to the summary to the specific allocated fund. Using this column provides the user with the option to view the accumulative measures in each level of the hierarchy.  
    fund_ledger_new2.png
    Fund and Ledger- Summary Details
    fund_type_new.png
    Fund Types

    Fund Rules

    The Fund Rules table is a dimension table that stores details about the fund rules.
    Fund Rules
    Field Description Additional Information
    Expenditures prior to fiscal period (days) The number of days, prior to the fiscal period start date, that new expenditures can be created.  
    Fiscal period end encumbrance grace period (days) The number of days, after the fiscal period end date, that new encumbrances can be created.  
    Encumbrances prior to fiscal period (days) The number of days, prior to the fiscal period start date, that new encumbrances can be created.  
    Fiscal period end expenditure grace period (days) The number of days, after the fiscal period end date, that new expenditures can be created.  
    Overencumbrance allowed Whether the fund allows you to add an encumbrance whose amount exceeds the fund's available balance (the allocated balance less any expenditures and encumbrances). Possible values are:
    • No
    • Yes – Alma checks the specified limit in the fund and performs a calculation against the fund’s amount. (If no limit is specified, the limit is assumed to be 0, which means that Yes will function like No.)
    • No Limits – indicates that overencumbrances are allowed without limits. Alma does not check the specified limit or whether the fund has money.
     
    Overencumbrance limit percent The maximum percentage of allowed encumbrances permitted before the system blocks the creation of an encumbrance. When that amount is reached, the transaction creation is blocked.  
    Overencumbrance warning percent The percentage of allowed overencumbrances permitted before the system provides a warning. When that amount is reached, an alert is displayed that the overencumbrance warning threshold has been reached. If the user confirms that the transaction should be added, an alert is added for the entity that created the fund transaction.  
    Overexpenditure allowed Whether the fund allows you to add an expenditure whose amount exceeds the fund's available balance. Possible values are:
    • No
    • Yes
    • No Limits – indicates that overexpenditures are allowed without limits.
     
    Overexpenditure limit sum The amount of overexpenditure (checked against the allocated balance) before the system blocks the creation of an overexpenditure.  
    Overexpenditure warning sum The amount of overexpenditure before the system provides a warning.  
    Override Rules Information (Yes/No) Override the rules set by the ledger.  
    Transfers prior to fiscal period (days) The number of days, prior to the fiscal period start date, that new money transfers can be created.  

    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.
    The primary key of the table is VENDOR_ID.
    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.  
    Creator The user who created the vendor  
    Modification Date The date the vendor was modified  
    Modified By The user who modified the vendor  
    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

    PO Line Approver

    The PO Line Approver table is a dimension table that stores details about the approver of the PO line.
    PO Line Approver
    Field Description Additional Information
    PO Line Approver Birth Date The birth date  
    PO Line Approver Cant Edit Restricted Users Indicates if the user can edit restricted user groups      
    PO Line Approver Campus Code The campus code  
    PO Line Approver Creation Date The creation date  
    PO Line Approver Creator The creator  
    PO Line Approver Disable All Login Restrictions Indicates if the user has IP login restrictions disabled      
    PO Line Approver Expiry Date The expiry date  
    PO Line Approver External ID The external ID  
    PO Line Approver Failed Authentication Indicates if authentication failed  
    PO Line Approver First Name The first name  
    PO Line Approver Full Name The full name  
    PO Line Approver Gender The gender  
    PO Line Approver Identifier 1-2 Identifiers 1-2  
    PO Line Approver IdP Service In Use Indicates if an identity provider service is in use  
    PO Line Approver Job Category The job category  
    PO Line Approver Job Description The job description  
    PO Line Approver Last Name The last name  
    PO Line Approver Last Activity Date The last date that a patron made a request or borrowed or returned an item  
    User – PO Line Approver Linked from Institution Code The linked from institution code  
    User – PO Line Approver Linked from Institution Name The linked from institution name  
    PO Line Approver Linked to Other Institution Indicates if linked to another institution  
    User – Linked From Other Institution Indicates if the user is linked from another institution Possible values:
    • yes
    • no
    PO Line Approver Locked Out Date The locked out date  
    PO Line Approver Middle Name The middle name  
    PO Line Approver Modification Date The modification date  
    PO Line Approver Modified By The user that modified  
    PO Line Approver Preferred First Name The preferred first name  
    PO Line Approver Preferred Language The preferred language  
    PO Line Approver Preferred Last Name The preferred last name  
    PO Line Approver Preferred Middle Name The preferred middle name  
    PO Line Approver Primary Identifier The primary identifier  
    PO Line Approver Purge Date The purge date  
    PO Line Approver Resource Sharing Library The resource sharing library  
    PO Line Approver Resource Sharing Library Code The resource sharing library code  
    PO Line Approver Statistical Category 1-10 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.
    PO Line Approver Status The status  
    PO Line Approver Status Date The status date  
    PO Line Approver User Email The user's preferred email for correspondence  
    PO Line Approver User Group The user group  
    PO Line Approver User Group Code The user group code  
    PO Line Approver User ID The user ID  
    PO Line Approver User Record Type The user record type  
    PO Line Approver User Title The user title  
    PO Line Approver User Type The user type  
    PO Line Approver Cataloger Level The cataloger level of the user  
    PO Line Approver Has Role Other Than Patron Indicates if the patron has a role other than Patron  
    PO Line Approver Has Role Other Than Patron and Instructor  Indicates if the patron has a role other than Patron and Instructor  
    PO Line Approver Is Blocked Indicates if the patron is blocked  
    PO Line Approver Patron Letters Opt In The letters for which the patron has opted in  
    PO Line Approver Patron Letters Opt Out The letters for which the patron has opted out  

    PO Line Creation Date

    The PO Line Creation Date table is a dimension table that stores details about the date that the PO line was created.
    PO Line Creation Date
    Field Description Additional Information
    PO Line Creation Date Stores the date in the date format 2/29/2012  
    PO Line Creation Start Of Week The date of the first business day of the week  
    PO Line Creation Week Number The number of the week of the year  
    PO Line Creation Month Key Stores the month of the date in number format such as 2 for February  
    PO Line Creation Month Stores the month of the date in month description format such as February  
    PO Line Creation Full Month Stores the month and the year of the date in a display format such as Feb 12  
    PO Line Creation Quarter Stores the quarter of the date in a display format such as Q1  
    PO Line Creation Year Stores the year of the date in string format such as 2012  
    PO Line Creation Fiscal Month Key Stores the fiscal month of the date in number format such as 2 for February  
    PO Line Creation Fiscal Year Stores the fiscal year of the date in string format such as 2012.  
    PO Line Creation Date Filter Used to filter report results by date.  

    PO Line Type

    The PO Line Type table is a dimension table that stores details about the PO line type associated with the transaction that determines the type of order created (one time/continuous) and the type of inventory items that is created (Ebook, Ejournal, etc.). The primary key of the table is PO_LINE_TYPE.
    PO Line Type
    Field Description Additional Information
    PO Line Type Name Stores the PO Line Type ID For the list of PO line types, see Enabling/Disabling PO Line Types. See the field location in Alma in the figure PO Line Types, below.
    Adding PO Line Type Name to a report displays only PO lines that have a fund. This is because only PO lines that have a related transaction have a PO Line Type Name value in the Funds Expenditure subject area.
    Acquisition Material Type Stores the acquisition material type. For the list of physical material types, see Configuring Physical Item Material Type Descriptions. See the field location in Alma in the figure PO Line Types, below.
    Acquisition Material Type Description The description of the acquisition material type  
    Format Stores the inventory format of Electronic, Physical, or Generic. Possible values are P, E, and G. This value comes from the Inventory Format column of the PO Line Type mapping table (Acquisitions > Purchase Orders > PO Line Types).
    See the field location in Alma in the figure PO Line Types, below.
    Continuity Stores if it is a one-time, continuous, or standing order PO line. See the field location in Alma in the figure PO Line Types, below.
    material_type_report.png
    po_line_type_new2.png
    PO Line Types

    PO Line

    The PO Line table is a shared dimension table that stores details about the PO and the PO Line.
    The field descriptions can be found in the PO Line shared dimension.
    PO Line
    Field Description Additional Information
    Access Model The public access model for the electronic resource.  
    Acquisition Method Stores the method by which the PO Line is acquired with the default value set as Purchase. This value may affect when the PO Line is sent. See the field location in Alma on the PO Line Summary Page below.
    Acquisition Method Description The description of the acquisition method  
    Additional Order Reference An additional identifier for the PO line  
    Application Used for identifying migrated lines  
    Assigned To Stores the user that is assigned to the order  
    Associated PO Line The target PO line  
    Association Type The type of association between PO lines, such as defined by user or by a process or job.  
    Cancellation Reason Stores the reason that a PO line is canceled and displays only on canceled lines. Values are in the code table POLineCancellationReasons  
    Cancellation Restriction Indicates if a cancellation restriction note, containing a warning upon the cancellation of a PO line, is configured to be displayed. See the field location in Alma on the PO Line Summary Page below.
    Cancellation Restriction Note The warning to be displayed when canceling a PO line. See the field location in Alma on the PO Line Summary Page below.
    CKB ID Stores a reference to the electronic collection PID for electronic PO lines  
    Claiming Date The number of days from the expected receipt/activation date to the date on which the PO line is sent to the claims task list The default value is taken from the Claiming grace period field on the Vendor Account Details.
    Currency The currency of the transaction.  
    Discount The discount amount. See the field location in Alma on the PO Line Summary Page below.
    ERP Number The ERP number of the purchase order Used by customers that want the purchase order to be approved by an ERP system before it is sent to the vendor
    Expected Activation Date Stores the expected date for the resource activation by vendor for electronic PO lines  
    Expected Activation Interval For electronic PO Lines, the number of days after ordering that you expect electronic orders to be activated  
    Expected Receipt after Ordering Interval For physical PO Lines, the number of days after ordering that you expect physical orders to be received See the field location in Alma on the PO Line Summary Page below.
    Expected Receiving Date Stores the expected date for physical items to be received from the vendor for physical PO lines See the field location in Alma on the PO Line Summary Page below.
    Interested Users Displays the interested users for the PO line. in case more than one user is added to the PO line, values are concatenated List of interested user in Alma is displayed in the interested users tab of the PO line. Note that in order to search for a specific user, you should use the contain filter in order to find also cases that more than 1 user was added to the PO.
    Invoice Status The status of the invoice See the field location in Alma on the PO Line Summary Page below.
    Is Claimed Flags the PO Line if there is an open claim to the vendor. A PO line is claimed if the items were not received.  
    Item Description Description of the item The description entered for the PO line. Note that this field is not taken from the bibliographic details. It is useful when no item is related to the PO line. See the field location in Alma on the PO Line Summary Page below.
    Latest Receiving Date The last date the material was received  
    License ID Stores the ID of the license of the PO line that is relevant for electronic PO lines  
    List Price The list price for a single copy of the item See the field location in Alma on the PO Line Summary Page below.
    Manual Renewal Stores an indication that the PO line is renewed manually or automatically  
    Material Supplier The vendor supplying the material being ordered The material supplier field as displayed in Alma PO line page. This is a concatenation of: name (code)/account description (account code).
    Material Type The material type of the PO line See the field location in Alma on the PO Line Summary Page below.
    Net Price A calculation of the total price for the PO line based on the list price per copy, the discount, and the number of copies ordered See the field location in Alma on the PO Line Summary Page below.
    No Charge Indicates if the No Charge checkbox on the PO Line Details page was selected, which is done for titles that were marked for purchase following a process of DDA/PDA, but are open access free-of-charge titles.  
    Note To Vendor Notes to the vendor. See the field location in Alma on the PO Line Summary Page below.
    Order Line Type The order line type as it appears in the order in Alma See the field location in Alma on the PO Line Summary Page below.
    Order Line Type Code A short code for the Order line type  
    PDA Code The patron driven acquisition code  
    PDA Name The patron driven acquisition name  
    PO Approval Date The date the PO was approved  
    PO Creation Date Stores the timestamp of the PO creation date  
    PO Creator Stores the user name that created the PO  
    PO Line Binding During Receiving Indicates that the PO line is marked for binding during receiving  
    PO Line Creation Date Stores the timestamp of the PO line creation date. Date fields can consist of a partial date, such as just the year or a month and year.
    PO Line Creation Date (Calendar) Stores the timestamp of the PO line 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.
    PO Line Creator Stores the user name that created the PO line  
    PO Line Identifier The identifier of the PO line  
    PO Line Inventory Library Code The code of the library of the ordered inventory. Since Analytics shows deleted items and holdings in the Physical Items subject area, this field also displays the matching libraries for deleted inventory that is linked to the PO line.
    PO Line Manual Packaging Indicates if the PO line was manually packaged into a PO  
    PO Line Modification Date Stores the timestamp of the PO line modification date Date fields can consist of a partial date, such as just the year or a month and year.
    PO Line Modification Date (Calendar) Stores the timestamp of the PO line 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.
    PO Line Modified By Stores the user name that modified the PO line  
    PO Line Notes The notes on the PO line Multiple notes are separated by a semicolon
    PO Line Owner Library Code The code of the PO line owner library  
    PO Line Owner Library Name The name of the  PO line owner library  
    PO Line Reference Stores the business identifier of the PO line This is the PO line number in Alma. See the Order Line field in Alma on the PO Line Summary Page below.
    PO Line Routing During Receiving Indicates that the PO line is marked for routing during receiving  
    PO Line Title The title of the PO line  
    PO Line Vendor Title Number The number of the PO line vendor title  
    PO Modification Date Stores the timestamp of the PO modification date Date fields can consist of a partial date, such as just the year or a month and year.
    PO Modification Date (Calendar) Stores the timestamp of the PO 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.
    PO Modified By Stores the user name that modified the PO  
    PO Number Stores the business identifier of the PO related to the PO line. See the field location in Alma on the PO Line Summary Page below.
    Quantity for Pricing The number of items to be paid for. The quantity for pricing and the number of items to create may be different in a case of discounted pricing through a deal such as "buy two items and get a third item at no additional charge." See the field location in Alma on the PO Line Summary Page below.
    Receiving Date (Latest in POL) This field allows you to retrieve the latest receiving date for an item in a PO line. This is useful, since a PO line can have several items and each of the items may have a different receiving date
    Receiving/Activation Note Text enabling the Purchasing Operator to indicate to the Receiving Operator the intended location of serial order items in which no inventory items are created. See the field location in Alma on the PO Line Summary Page below.
    Receiving Status Stores an indication of whether or not all physical items were received in the receiving workbench  
    Reclaim Interval (Days) The interval number of days that Alma will send reclaim letters after the initial claim letter is sent.  
    Renewal Cycle Stores the cycle for the autorenewal job for continuous orders. For example, if it is set to one year, the PO line is renewed in one year. Defined in the RenewalCycle code table.
    Renewal Date Stores the date of the PO line’s next renewal for continuous orders  
    Renewal Note Stores the note of the PO line renewal for continuous orders  
    Renewal Reminder Period Determines how many days before renewal is mail regarding that renewal sent  
    Reporting Code - 1-5 Five fields that store the reporting codes. See the field location in Alma on the PO Line Summary Page below.
    Reporting Code Description -1-5 Five fields that store the description of the 5 reporting code fields  
    Rush Indicates whether the PO line is to be rushed. See the field location in Alma on the PO Line Summary Page below.
    Sent Date Stores the date that the PO/ PO line is sent to the vendor See the field location in Alma on the PO Line Summary Page below.
    Ship to Address ID Stores the library shipping address that should be used by the vendor  
    Shipped To Address City The shipped to city.  
    Shipped To Address Country The shipped to country.  
    Shipped To Address Line 1-5 The shipped to address lines.  
    Shipping Method Stores the method for the vendor to ship the order Per the values in Shipping Method code table defined in the acquisition configuration menu
    Source ID Stores the source file ID used for the EOD lines  
    Source Type Stores the source from which the PO line originated. Values for example: EOD, Manual, Migration, and so forth  
    Status Stores the business status of the PO line as Active, Canceled, or Closed
    There are a number of sub-statuses included in the business status Active. See the Status (Active) field.
    See the field location in Alma on the PO Line Summary Page below.
    Status (Active) Indicates the sub-status of the Status field. For example: Waiting for Invoice, Waiting for Manual Renewal, Recurring Renewal, Under Evaluation, Sent, In Review, Ready to Be Sent, Waiting for Packaging, and Manual Packaging  
    Subscription From Date Stores the date for the beginning of a subscription for continuous orders  
    Subscription To Date Stores the date for the end of a subscription for continuous orders  
    Vendor Access Provider The access provider of the vendor.  
    Vendor Account Code The vendor description as defined in the Alma vendor account definitions  
    Vendor Account Description The vendor description as defined in the Alma vendor account definitions.  
    Vendor Code The vendor code as defined in the Alma vendor details definitions. All the vendors that have been on the order, not just the active vendor.
    Vendor Contact Person ID Stores the related vendor contact person ID  
    Vendor Name The vendor name as defined in the Alma vendor details definitions.
    Vendor Reference Number Store the reference number for the PO line in Alma, as provided by the vendor. Serves as a matching point for identifying a PO line in Alma See the field location in Alma on the PO Line Summary Page below.
    Vendor Reference Number Type Stores the type of the reference number See the field location in Alma on the PO Line Summary Page below.
    • The PO line status is not currently mapped to analytics and will be added in a future release.
    pricing_information.gif
    Some of the fields of the PO Line dimension are taken from the fields of the PO Line Details page:
    purchase_order_line_details_newUI.png
    PO Line Summary Page

    PO Line License

    The PO Line License table is a dimension table that stores information about the license such as the license ID, the license name, and the license creator.
    License Header
    Field Description Additional Information
    License ID The ID of the license  
    License Code The code of the license  
    License Creator Name The first and last name of the user who created the license  
    License Modifier Name The first and last name of the user who modified the license  
    License Name The name of the license  
    License Begins The date the license begins  
    License Ends The date the license ends  
    License Creation Date The date the license was created  
    License Modification Date The date the license was modified  
    License Note The note of the license  
    License Originating Licensor Key The licensor key of the license  
    License Originating Parent Code The originating parent code of the license  
    License Parent ID The parent ID of the license  
    License Review Status The renewal status of the license  
    License Signed By The user who signed the license  
    License Signed On The date the license was signed on  
    License Second Party Signed By The second party who signed on the license  
    License Second Party Signed On The date the second party signed on the license  
    License Status The status of the license  
    License Storage Location The storage location of the license  
    License Type The type of the license Possible Values:
    • License – a standard license
    • Negotiation – a license negotiated by a collaborative network with vendors on behalf of multiple member institutions
    License URI The URI of the license  
    Licensing Agent Name The name of the licensing agent  
    Licensor ID The ID of the licensor  
    Licensor Name The name of the licensor  

    Invoice Line

    The Invoice Line table is a dimension table that stores details about the invoice and invoice line associated with the transaction. The encumbrance created by the PO Line is released by the expenditure created by the Invoice. The primary key of the table is INVOICE_LINE_ID.
    Invoice Line
    Field Description Additional Information
    Invoice - Approval Date Invoice column - the date that the Invoice was approved.  
    Invoice - Approval Status Holds the following values: Pending, Approved, Rejected, Not Required  
    Invoice - Approver Name The first and last name of the user that approved the invoice  
    Invoice - Creation Date Holds the timestamp of the Invoice creation date Date fields can consist of a partial date, such as just the year or a month and year.
    Invoice - Creation Date (Calendar) Holds the timestamp of the Invoice 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.
    Invoice - Creation From The source from which the invoice was created.  
    Invoice - Creator Holds the user name that created the Invoice  
    Invoice - Currency The currency of the invoice  
    Invoice - Date The date on the invoice header.  
    Invoice - Disapprove Reason Will be activated if the invoice is disapproved. Values in Code table
    InvoiceDisapproveReasons
    Invoice - Due Date The due date of the invoice line  
    Invoice - Expended From Fund Indicates if the VAT is expended from the invoice line's funds. If it not, a new adjustment invoice line is added to the invoice which includes invoice VAT amounts  
    Invoice - External Reference Number Holds the External Invoice Reference Number  
    Invoice - Modification Date Holds the timestamp of the Invoice modification date  
    Invoice - Modified By Holds the user name that modified the Invoice  
    Invoice - Number Number of the invoice See the field location in Alma in Alma in the figure Invoice Line Details, below.
    Invoice - Owner Code The owner code of the invoice  
    Invoice - Owner Name The owner name of the invoice  
    Invoice - Payment Method Payment method of the Invoice, (for example: credit card, cache) Values are in CT: PaymentMethod  
    Invoice - Payment Status Indicates if the Invoice was paid or not. See the field location in Alma in the figure Invoice Details, below.
    Invoice - Payment Voucher Amount The amount of the payment voucher  
    Invoice - Payment Voucher Date The date that the voucher was created  
    Invoice - Payment Voucher Number Number of the voucher that the invoice was paid by ERP.  
    Invoice - Prepaid Ind Indicates if the Invoice is prepaid. If the invoice is prepaid then it won't be exported to ERP. See the field location in Alma in the figure Invoice Details, below.
    Invoice - Report Tax Indicates if an invoice needs to report state tax.  
    Invoice - Status Invoice Status Possible values: (Closed, In Review, Ready to be paid, In Approval, Waiting for Payment)
    Invoice - Unique Identifier Identifies the invoice uniquely  
    Invoice - VAT Amount The total VAT amount  
    Invoice - VAT Code The invoice VAT code  
    Invoice - VAT Code % The invoice VAT Code percent  
    Invoice - VAT Code Description The invoice Vat code description  
    Invoice - VAT per invoice line Indicates if the VAT is calculated at the invoice or invoice line level  
    Invoice - VAT Type Indicates if VAT Exclusive or Inclusive in invoice total amount Possible values: Exclusive/Inclusive/Line Exclusive.
    Invoice - Vendor Account Code Related vendor account code.  
    Invoice - Vendor Account Description Related vendor account.  
    Invoice Line - Additional Information The additional information of the invoice line  
    Invoice Line - Creation Date Holds the timestamp of the Invoice Line creation date Date fields can consist of a partial date, such as just the year or a month and year.
    Invoice Line - Creation Date (Calendar) Holds the timestamp of the Invoice Line 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.
    Invoice Line - Creator Holds the user name that created the Invoice Line  
    Invoice Line - Currency The currency of the invoice line  
    Invoice Line - Modification Date Holds the timestamp of the Invoice Line modification date Date fields can consist of a partial date, such as just the year or a month and year.
    Invoice Line - Modification Date (Calendar) Holds the timestamp of the Invoice Line 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.
    Invoice Line - Modified By Holds the user name that modified the Invoice Line  
    Invoice Line - Note The note on the invoice line  
    Invoice Line - Number Identifier for the Invoice line.  
    Invoice Line - Price Note The price note of the invoice line  
    Invoice Line - Status The status of the invoice line: Ready if the line is valid, In Review otherwise. See the field location in Alma in the figure Invoice Line Report, below.
    Invoice Line - Subscription From Date For continuous invoice lines: Start date of the subscription.  
    Invoice Line - Subscription To Date For continuous invoice lines: End date of the subscription.  
    Invoice Line - Type Type of the invoice line. Code table: Invoice Line Type.
    Invoice lines of type Adjustment are not expenditure transactions; therefore, they are not available in reports.
    Invoice Line - Unique Identifier Identifies the invoice line uniquely  
    Invoice Line-VAT Code The invoice line VAT code.  
    Invoice Line-VAT Code % The invoice line VAT code percent  
    Invoice Line-VAT Code Description The invoice line VAT code description  
    Invoice Line-VAT Note Data The invoice line VAT amount  
    Invoice-Internal copy Ind Indicates if an internal copy of the invoice exists  
    Reporting Code - 1-5 Five fields that store the reporting codes. Taken from the invoice line
    Reporting Code Description -1-5 Five fields that store the description of the 5 reporting code fields  
    invoice_line_details_report.gif
    Invoice Line Report
    invoice_line_details_new.png
    Invoice Line Details

    Bibliographic Details

    The Bibliographic Details table is a dimension table that stores bibliographic details about the inventory item that was purchased. The primary key of the table is MMS_ID.
    The field descriptions can be found in the Bibliographic Details shared dimension.

    Ex Libris works with content providers worldwide to enrich the metadata available in the Alma Community Zone. To enrich the journal/serial content in the CZ, we work directly with the Library of Congress CONSER feed for electronic serials, which we match against our knowledge base to enrich with all of the relevant metadata fields that they supply (for more details, see Community Zone Serial Records Enrichment). We receive weekly updates from CONSER and enrich the CZ records with all relevant metadata, including the 050 fields (when available).

     

    In the case of book content, we work with multiple providers who are willing to share their metadata with the Alma community globally (for more details, see Community Zone Monograph Records Enrichment). If you have local access to these classifications, you may want to consider working with the local extension for these records whenever an update is not available. (For more details, see Working with Local Extension Fields for Community Zone-linked Records)

    Bibliographic Details
    Field Source in Alma (for Internal Reference)

    Mapping from

    MARC21

    Mapping from UNIMARC

    Mapping from

    Dublin Core

    Author Taken from display.author in the display section of the operational record 100,110,111 700,701,710,711 Currently empty, planned to come from dc:creator, dcterms:creators
    Author (Contributor) An additional Author field

    711 a,c-e,i,j,n,q,u and its 880

    700 a-e,j,q,u and its 880

    710 a-e,i,n,u and its 880

    700 a-d,f,p

    701 a-d,f,p 

    710 a-h,p

    711 a-h,p

    720 a,f"

    721 a,f

    702 a-d,f,g 

    712 a-h,p

    722 a,f

    Currently empty, planned to come from dc:contributor, dcterms:contributor
    Begin Publication Date Taken from display.begin_pub_date in the search section of the operation 008 pos. 07-10 100.Date1 Not relevant for Dublin Core
    BIB 008 MARC The contents of the MARC 008 bibliographic field 008   Not relevant for Dublin Core
    BIB LDR MARC The contents of the MARC LDR bibliographic field LDR   Not relevant for Dublin Core
    Bibliographic Acquisition Accession Number Note The identification code assigned to materials acquired in a single and separate transfer of custody (from MARC field 541 $e). 541 e   Not relevant for Dublin Core
    Bibliographic ID Taken from display.bib_id in the display section in the operational record 010 excluding numeric subfields 020 a dcterms:identifier dcterms:ISBN, dcterms:identifier dcterms:ISSN
    Bibliographic Level Taken from display.bib_level in the display section of the operational record Position 7 of the LDR field of the bibliographic record Position 7 of the LDR field of the bibliographic record Not relevant for Dublin Core
    Bibliographic Source of Acquisition Note The name of the people or organization that is the source of the material (from MARC field 541 $a) 541 a   Not relevant for Dublin Core
    Category of Material Taken from display. category_of_material in the display section of the operational record.
    Only the first character is displayed in Analytics.
    Position 0 of the 007 field  200 b dc:type
    DC License   Relevant only for Dublin Core Relevant only for Dublin Core Field does not yet exist.  It will be populated by  dcterms:license
    DC Rights   Relevant only for Dublin Core Relevant only for Dublin Core Field does not yet exist.  It will be populated by dc:rights and dcterms:rights
    Edition Taken from display.complete_edition in the display section of the operational record MARC 250 subfields a,b 205 a,b,f,g dcterms:isVersionOf
    Electronic location and access The location and access URl for the electronic resource 856 all subfields    
    End Publication Date Taken from display.end_pub_date in the search section of the operation 008 pos. 11-14 100.Date2 Not relevant for Dublin Core
    Form of Item The form of the item MARC 008 pos. 29 (Maps and Visual Material) or 23 (other material configurations)   dc:format
    General Note The general note 500 a, 5    
    Government Publication The government publication type

    MARC 008 pos. 28

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

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

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

      Not relevant for Dublin Core
    ISBN Taken from search.isbn in the search section of the operational record MARC 020 a,z MARC 776 z 010 a dcterms:identifier dcterms:ISBN
    ISBN Valid The valid ISBN value MARC 020 a   Not relevant for Dublin Core
    ISSN Taken from the MMS Display Table in the search section of the operational record 022 l,a 776 x (for non-physical records) 011 a f dcterms:identifier dcterms:ISSN
    ISSN Valid The valid ISSN value MARC 022 a   Not relevant for Dublin Core
    Language Code Taken from display.language in the display section in the operational record 008 pos. 35-37 101 a Currently comes from dc:language.  Planned to come from dc:language and dcterms:language
    Language Of Cataloging The language in which the cataloging was done 040 b 100 a,22-24 Not relevant for Dublin Core
    Local Note The local note 590 a, 5    
    Material Type See the table, Fields that Identify the Bibliographic Material Type, in the Material Types in Search Results section for a description of material type. MARC control LDR Material Type   Planned to be empty.  Currently comes from dc:type
    Material Type Code Code of the material type described above (in Material Type). MARC control LDR Material Type   Not relevant for Dublin Core
    Network Number Taken from search. other_system_number in the search section of the operational record 035 a z 053 a z dc:identifier , dcterms:identifier
    OCLC Control Number (019) The OCLC control number
    Leading zeros are not displayed.

    019 a

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on 
      Not relevant for Dublin Core
    OCLC Control Number (035a) The OCLC control number
    Leading zeros are not displayed.

    035 a

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on
    035 a Not relevant for Dublin Core
    OCLC Control Number (035a+z) The OCLC control number
    Leading zeros are not displayed.

    035a+z

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on
    035a+z Not relevant for Dublin Core
    OCLC Control Number (035z) The OCLC control number
    Leading zeros are not displayed.

    035 z

    When the subfield begins with one of the following prefixes:  

    • (OCLC)
    • (OCoLC)
    • ocm
    • ocn
    • on
    035 z Not relevant for Dublin Core
    Open Access Indicates if the article is open access Based on 506 f 506 2   Not relevant for Dublin Core
    Original Cataloging Agency The MARC code or the name of the organization that created the original record 040 a 081 b Not relevant for Dublin Core
    Place Code Taken from display.place_code in the display section of the operational record 008 pos. 15-17 102$$a Currently empty, planned to come from dcterms:spatial
    Place of Publication - City The city of publication For a list of country codes, see:

    MARC Code List for Countries

    For a list of country codes, see:

    List of ISO 3166 Country Codes

    Not relevant for Dublin Core (use Place Code)

    If the value of this field in the bibliographic record does not exist in the official list of place codes, the value for this field in Alma Analytics will be "No place, unknown, or undetermined". If there are multiple place codes in this field, only the first value is displayed.

    Place of Publication - Country The country of publication For a list of country codes, see:

    MARC Code List for Countries

    For a list of country codes, see:

    List of ISO 3166 Country Codes

    Not relevant for Dublin Core (use Place Code)

    If the value of this field in the bibliographic record does not exist in the official list of place codes, the value for this field in Alma Analytics will be "No place, unknown, or undetermined". If there are multiple place codes in this field, only the first value is displayed.

    Place of Publication - State The state of publication For a list of country codes, see:

    MARC Code List for Countries

    For a list of country codes, see:

    List of ISO 3166 Country Codes

    Not relevant for Dublin Core (use Place Code)

    If the value of this field in the bibliographic record does not exist in the official list of place codes, the value for this field in Alma Analytics will be "No place, unknown, or undetermined". If there are multiple place codes in this field, only the first value is displayed.

    Publication Date Taken from display.date_of_publication in the display section of the operational record
    The publication date is determined as follows:
    • the bibliographic details publication date comes from 264 subfield c
    • if there is no 264 subfield c, then the publication date comes from 260 subfield c
    • if there is no 264 subfield c and also no 260 subfield c, then the publication date comes from 008 pos. 7-10
    The publication date is determined as follows:
    • the bibliographic details publication date comes from 210 subfield d
    • If there is no 210 subfield d, then the publication date comes from field 214 subfield d.
    • if both fields do not exist, then the publication date comes from field 100 subfield a pos. 9-12 
    dc:date
    Publication Place Taken from display.place_of_publication in the display section of the operational record MARC 260 a. When 260a is empty, it is taken from MARC 264a 210 a 214 a Not relevant for Dublin Core (use Place Code)
    Publisher Taken from display.publisher_const_b in the display section of the operational record

    260 b

    264 b

    210 c

    214 c

    dcterms:publisher, dc:publisher
    Resource Type Constructed based on existing bibliographic fields such as the LDR and 008. For more information, see The Resource Type Field.      
    Series Taken from display.series_small in the display section in the operational record 800 t,v

    810 t,v

    811 t,v

    830 a,n,p,v

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

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

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

       
    Title Taken from display.title in the display section of the operational record

    245 a,b

    249 a,b,c,v

    200 a,c,d,e,h,i dc:title
    Title (Complete) The information from MARC field 245, subfields $p, $n, $s, $k, $f, $g. 245 a,n,p,h,b,c,f,g,k,s 200 a-i Currently empty, planned to come from dc:alternative
    Title (Filing) The title with common words such as "The" and "An" removed to help with sorting the title alphabetically.
    Any text between double arrows (<<>>) is removed.
    For a video describing the use of this field, see Sort Analytics Reports by Filing Title - Ignoring "The", "A", and "An".

    240 a,c,p

    245 a,c,p

    200 a,e

    500

    Not relevant for Dublin Core
    Title (Normalized) The normalized Title. This field is useful when you want to use the normalized title from one subject area to compare with a report with fields from a different subject area. This field is built in the following manner:
    Alma does the following to the 245 field (except subfields c,h,6 and 8) in the following order:
    1. Removes non filing text.
    2. Removes <<>> and anything between them.
    3. Removes these characters: []|,.;:"
    4. Changes these characters to a space: !@#$%^&*()_+-={}\<>?/~'
    5. Changes characters to lowercase.
    6. Packs spaces (replace all sequences of more than one space with a single space).

    245 a,b,n,p

    249 a,b,c,v

    200 a,c,d,e,h,i dc:title
    Title Author Combined and Normalized 100 characters of the normalized title and the first four letters of the author in lowercase letters, with spaces removed See Author and Title Fields See Author and Title Fields See Author and Title Fields
    Type of Date Taken from display. type_of_date in the search section of the operational record 008 pos. 6 100 pos 8 Not relevant for Dublin Core
    Uniform Resource Identifier The uniform resource identifier 856 u 856 u dc:identifier (dcterms:URI) ,dcterms:identifier (dcterms:URI)
    Uniform Resource Identifier Exists Indicates if 856 subfield u contains data      
    Uniform Title Taken from display.uniform_title in the display section of the operational record 240 130 500 Not relevant for Dublin Core
    The following table describes other fields in the shared dimension (taken from Alma and not MARC):
    Administrative Bibliographic Details
    Field Source in Alma (for Internal Reference)
    Active Course Code The code of an active course.
    Active Course Name The name of an active course.
    Bibliographic Lifecycle The Lifecycle of the item. Possible values are Deleted and In Repository. This allows you to filter reports by In Repository/Deleted items.
    Brief Level The level of the brief record
    Chinese Classifications Stores the Chinese Classification
    Collection ID The ID of the collection.  This is a title level collection as defined at 'Resources > Manage Inventory > Manage Collections'.
    Collection Name The name of the collection.  This is a title level collection as defined at 'Resources > Manage Inventory > Manage Collections'.
    Creation Date Stores the creation date. Date fields can consist of a partial date, such as just the year or a month and year.
    Creation Date (Calendar) Stores the creation date. Calendar Date fields always consist of a month, date, and year. If the information is not provided, 01 is added, so that a date of 2020 is rendered 01/01/2020. This date format is useful when filtering the report by date.
    Creator Stores the name of the user that created the record
    Dewey Classification Stores the Dewey Classification
    Dewey Classification Top Line

    Stores the first 3 digits of the Dewey Classification

    Regarding Dublin Core:

    Currently empty.  Planned to come from dc:subject (dcterms:DDC),
    dcterms:subject (determs:DDC)  

    Has Local Extensions

    Indicates if the Community Zone-linked record has local extensions (Y/N)

    ISBN (Normalized)
    The normalized ISBN.
    ISSN (Normalized) The normalized ISSN.
    LC Classification Top Line Stores the combined LC code and classification numbers until the first period which is followed by a letter. If there are no periods then the entire string is taken until there is a space. The length is limited to 50 characters.
    For example:
    • if the LC Classification is | a HB3821.I8 |b R3 then the LC Classification Top Line will be HB3821
    • if the LC Classification is | a DF506.5 |b .G27 then the LC Classification Top Line will be DF506.5
    • if the LC Classification is | a N 7353 |b .K513 1965 then the LC Classification Top Line will be N
    • if the LC Classification is | a NOT YET ORDERED then the LC Classification Top Line will be NOT
    The LC Classification Top Line will contain one value. For MARC21, if the bibliographic record has:
    • both 090 and 050 then the LC Classification Top Line will come from 090
    • 050 and not 090 then the LC Classification Top Line will come from 050
    • 090 and not 050 then the LC Classification Top Line will come from 090

    Regarding Dublin Core:

    Currently empty. Planned to come from:
    (dcterms:LCSH),
    dcterms:subject (determs:LCSH),
    dc:subject (dcterms:LCC),
    dcterms:subject (determs:LCC)

    Recent data may not be available if it has not yet been received from CONSER.
    Link ID The link ID. For more information concerning this field and the next two, see Understanding the fields Link ID Linked to CZ and Linked to NZ in the Bibliographic Details folder.
    Linked to CZ Indicates if the record is linked to the Community Zone
    Linked to NZ Indicates if the record is linked to the Network Zone
    Local Param 1-10 This field allows you to enrich the bibliographic and holdings information exported to Analytics with additional information from MARC fields in Alma.
    In order to make use of this field, you must contact Ex Libris Support and supply them with a three-digit MARC field code (for example, 901). (The field does not need to include a 9.)
    The fields can be number and code fields but not control fields. Therefore, the field must be greater than or equal to 010, because 00X are Control Fields and 01X-09X are Numbers and Code Fields.
    Following configuration of this field by Ex Libris Support, its value will be available in analytics.
    Subfields can be maintained in the Analytics fields identified for Local Param. When this capability is implemented, fields/subfields appear in Alma Analytics with the Alma subfield delimiter (either $$ or ‡) used to delineate the subfield content. Contact Support to enable this feature. Note that reindexing is required to fully implement this capability.
    Note that the local param fields are not related to the MARC type of the record. For example, if field 913 is defined to be in local param 1 then field 913 will always be in local param 1. This is the case if the record is of the type KORMARC, CNMARC, UNIMARC, MARC21, and so forth. It is not possible to have different sets of Local Param 1-10 for different types of MARC.
    The data in the local parameters is limited to 3900 characters.
    Managed by Provider Indicates if the electronic resource is managed by the provider
    MMS ID Stores the MMS ID of the item. This is the MMS ID of the portfolios associated with the electronic collection. It is not the MMS ID of the electronic collection or of the MMS ID of the descriptive bibliographic record added in the Additional tab of the electronic collection editor. If there are no portfolios, the value of this field is empty.
    Modification Date Stores the modification date. Date fields can consist of a partial date, such as just the year or a month and year.
    Modification Date (Calendar) Stores the modification date. Calendar Date fields always consist of a month, date, and year. If the information is not provided, 01 is added, so that a date of 2020 is rendered 01/01/2020. This date format is useful when filtering the report by date.
    Modified By Stores the user name that modified the record
    Network ID This field is used by institutions implementing a Network Zone. It is the same as the MMS ID of the bibliographic record in the Network Zone and can be used to create reports that show the MMS ID in the member institution (using the existing MMS ID), as well as the corresponding MMS ID in the Network Zone.
    Originating System The system where the bibliographic record originated
    Originating System ID The ID of the system where the bibliographic record originated
    Originating System Version The version of the originating system
    Peer Reviewed Indicates if the article was peer reviewed
    Provider Name The name of the provider
    Record Format The format of the bibliographic record. Examples:
    • MARC 21
    • DC
    • KORMARC
    • CNMARC
    • UNIMARC
    Suppressed from Discovery Indicates whether the record is suppressed from external discovery systems

    Periods Outer

    The Periods Outer table is a dimension table that stores details about the transaction date of transactions, such as month, year, and quarter. The difference between this table and the transaction date table is that in this table the transaction dates are not normalized to the fiscal period.
    The primary key is Date_Key.
    Periods Outer
    Field Description Additional Information
    Full Month Desc Stores the month and the year of the date in a display format such as Feb 12  
    Start of Week The date of the first business day of the week  
    Week Number The number of the week of the year  
    Full Month Key Stores the month in a number format such as 9 for September and the year  
    Date Key Stores the date in the date format 2/29/2012  
    Fiscal Full Month Key Stores the fiscal month in a number format such as 9 for September and the year  
    Fiscal Full Quarter Desc Stores the fiscal quarter of the date in a display format such as Q1 and the year  
    Fiscal Full Quarter Key Stores the fiscal quarter of the date in a display format such as 1 and the year  
    Fiscal Month Key Stores the fiscal month of the date in number format such as 2 for February This field is useful when you want to sort by month
    Fiscal Quarter Desc Stores the fiscal quarter of the date in a display format such as Q1  
    Fiscal Quarter Key Stores the fiscal quarter of the date in a display format such as 1  
    Fiscal Year Desc Stores the fiscal year of the date in string format such as 2012.  
    Fiscal Year Key Stores the fiscal year of the date in string format such as 2012  
    Full Quarter Desc Stores the quarter of the date in a display format such as Q1 and the year  
    Full Quarter Key Stores the quarter of the date in a display format such as 1 and the year  
    Month Desc Stores the month of the date in month description format such as February  
    Month Key Stores the month of the date in number format such as 2 for February This field is useful when you want to sort by month
    Quarter Desc Stores the quarter of the date in a display format such as Q1  
    Quarter Key Stores the quarter of the date in a display format such as 1  
    Year Stores the year of the date in string format such as 2012  
    Year Key Stores the year of the date in string format such as 2012  
    Date Filter Used to filter report results by date.  

    Institution

    The shared Institution dimension allows the Network Zone to view reports according to institution. It is available in every subject area. It contains the following fields:
    Institution
    Field Description Additional information
    Institution Code The code of the institution.  
    Institution Name The name of the institution.  
    Institution Timezone The timezone of the institution  
    Data Available As Of When the data became available to analytics  
    Data Updated As Of When the data was taken from Alma  
    If an analytics report is run from the Network Zone in a collaborative network implementing a Network Zone, all member institutions are included in the report for Institution Code and Institution Name.
    If an analytics report is run from an institution that is not part of a collaborative network implementing a Network Zone, only the single institution from which the report is run is included in the report for Institution Code and Institution Name.
    Reports involving data across a collaborative network implementing a Network Zone may take longer to run than reports within one institution.

    Shared Dimensions with Other Subject Areas

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