Titles

Field Descriptions

The following fields are available in Titles.

Titles – Field Descriptions

Title Measures

The Title Measures table is a fact table that stores all measures relating to tiles, such as number of titles, number of physical items, number of portfolios, and number of electronic collections.

Title Measures
Field	Description	Additional Information
Number of Titles (All)	The total number of titles, including active and deleted.
Number of Titles (Active)	The total number of active (non deleted) titles found in the repository.
Number of Titles (Deleted)	The total number of deleted titles.
Number of Titles with Physical Items (Active)	The number of titles with active physical items
Number of Titles with Physical Items or Holdings Records (Active)	The number of titles with active physical items or holding records
Number of Titles with Holdings Records and No Items (Active)	The number of titles with active holding records and no items
Number of Titles with Electronic Portfolios (Active)	The number of titles with active electronic portfolios
Number of Titles with Electronic Collections (Active)	The number of titles with active electronic collections
Number of Titles with Digital Representations (Active)	The number of titles with active digital representations
New for May! Number of Titles linked to CZ	The number of titles linked to the Community Zone
New for May! Number of Titles linked to NZ	The number of titles linked to the Network Zone
New for May! Number of Titles not linked to CZ or NZ	The number of titles not linked to either the Community Zone or the Network Zone
Number of Physical Items (All)	The total physical items, including active and deleted.
Number of Physical Items (Active)	The total number of active physical items.
Number of Physical Items (Deleted)	The total number of deleted physical items.
Number of Holdings (All)	The total number of holdings records.
Number of Holdings (Active)	The number of active holdings.
Number of Holdings (Deleted)	The number of deleted holdings.
Number of Portfolios (All)	The total number of portfolios, including active and deleted.
Number of Portfolios (Active)	The total number of active portfolios.
Number of Portfolios (Deleted)	The total number of deleted portfolios.
Number of Electronic Collections (All)	The total number of electronic collections, including active and deleted.
Number of Electronic Collections (Active)	The total number of active electronic collections.
Number of Electronic Collections (Deleted)	The total number of deleted electronic collections.
Num of Digital Representations (All)	The total number of digital representations, including active and deleted.
Num of Digital Representations (Active)	The total number of active digital representations.
Num of Digital Representations (Deleted)	The total number of deleted digital representations.
Num of Research Assets (Active)	The number of active research assets
Num of Research Assets Files	The number of research asset files

Usage Measures

The Usage Measures table is a fact table that stores all measures relating to usage, such as number of loans, number of link resolver requests, and number of borrowing requests.

Usage Measures
Field	Description	Additional Information
Number of Loans (In House + Not in House)	The total number of loans, including in house and not in house loans.
Number of Loans (In House)	The total number of in house loans.
Number of Loans (Not in House)	The total number of not in house loans.
Number of Link Resolver Services	The number of link resolver services.
Number of Link Resolver Clicked Services	The number of link resolver selected services.
Number of Link Resolver Requests	The number of link resolver requests.
Number of Link Resolver Clicked Requests	The number of link resolver selected requests.
Number of Link Resolver Requests Without Services	The number of link resolver requests without services.
Number of Requests (Active)	The number of active requests.
Number of Requests (Historical)	The number of historical requests.
Number of Borrowing Requests	The number of borrowing requests.
Number of Lending Requests	The number of lending requests.

Usage Measures - Last Year (365 Days)

The Usage Measures table is a fact table that stores all measures relating to usage for the last 365 days, such as Number of Loans, Number of Link resolver Requests, and Number of Borrowing Requests.

Usage Measures - Last Year (365 Days)
Field	Description	Additional Information
Number of Loans (In House + Not in House)	The total number of loans, including in house and not in house loans in the last 365 days.
Number of Loans (In House)	The total number of in house loans in the last 365 days.
Number of Loans (Not in House)	The total number of not in house loans in the last 365 days.
Number of Link Resolver Services	The number of link resolver services in the last 365 days.
Number of Link Resolver Clicked Services	The number of link resolver selected services in the last 365 days.
Number of Link Resolver Requests	The number of link resolver requests in the last 365 days.
Number of Link Resolver Clicked Requests	The number of link resolver selected requests in the last 365 days.
Number of Link Resolver Requests Without Services	The number of link resolver requests without services in the last 365 days.
Number of Reading List Citations	The number of active requests in the last 365 days.
Number of Requests (Active)	The number of historical requests in the last 365 days.
Number of Requests (Historical)	The number of borrowing requests in the last 365 days.
Number of Borrowing Requests	The number of lending requests in the last 365 days.
Number of Lending Requests	The total number of loans, including in house and not in house loans in the last 365 days.

Title Details

The Title Details table is a dimension table that stores information about the title such as the library name and code for physical and electronic inventory.

Title Details
Field	Description	Additional Information
Data uploaded as of	The last date data was uploaded.
Has Active Digital Representations	Indicates if the title has active digital representations
Has Active Electronic Collections	Indicates if the title has active electronic collections
Has Active Electronic Portfolios	Indicates if the title has active electronic portfolios
Has Active Holdings Records	Indicates if the title has active holding records
Has Active Physical Items	Indicates if the title has active physical items
Last Loan Date (In House)	The date of the last in house loan
Last Loan Date (Not In House)	The date of the last not in house loan
Library Code (Physical)	The library code for physical resources.
Library Name (Physical)	The library name for physical resources.
Library Code (Electronic)	The library code for electronic resources.
Library Name (Electronic)	The library name for electronic resources.
Library Code (Digital)	The library code for digital resources.
Library Name (Digital)	The library name for digital resources.
Permanent Call Number	A code used to file the items on the shelf
Coverage Information Combined	The combined coverage information for physical and electronic inventory.	Used when performing an overlap analysis
Summary Holding	A summary of holdings of physical and electronic inventory.	Used when performing an overlap analysis

Bibliographic Details

The Bibliographic Details table is a dimension table that stores the details of the bibliographic record. 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: Removes non filing text. Removes <<>> and anything between them. Removes these characters: []\|,.;:" Changes these characters to a space: !@#$%^&*()_+-={}\<>?/~' Changes characters to lowercase. Packs spaces (replace all sequences of more than one space with a single space).	245 a,b,n,p 249 a,b,c,v	200 a,c,d,e,h,i	dc:title
Title Author Combined and Normalized	100 characters of the normalized title and the first four letters of the author in lowercase letters, with spaces removed	See Author and Title Fields	See Author and Title Fields	See Author and Title Fields
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

Bibliographic IDs

The Bibliographic IDs table is a dimension table that stores the bibliographic IDs of the physical item.

Bibliographic IDs
Field	Description	Additional Information
ISBN 020 a single (Normalized)	Displays the contents of one MARC field 020 subfield a of the ISBN per row for each MMS ID
ISSN 022 a single (Normalized)	Displays the contents of one MARC field 022 subfield a of the ISSN per row for each MMS ID
OCLC Control Number single (035a)	Displays one OCLC per row for each MMS ID

Title Creation Date

The Title Creation Date table is a dimension table that stores details about the title creation date. Key fields are used whenever calculations are required. Description fields may be used for formatting the display of the report. Alma stores the following types of fields:

Calendar Fields – These are date fields as they display in the calendar.
Fiscal Date Fields – These are date fields that match the institution's fiscal period. In the examples below, the fiscal period of the institution is for fiscal year 2012 that starts June 1, 2011 and ends May 31, 2012.

Using this dimension, the user may drill down from year to month to the specific date on which the title was created. The number of the title is accumulated to the relevant level in the hierarchy.

Title Creation Date
Field	Description	Additional Information
Title Creation Date	Stores the title creation date in a date format such as 2/29/2014.
Title Creation Start of Week	The date of the first business day of the week
Title Creation Week Number	The number of the week of the year
Title Creation Month Key	Stores the month of the date in number format such as 2 for February	This field is useful when you want to sort by the month, which does not work properly when using the alphabetical field.
Title Creation Month	Stores the month of the date in month description format such as February
Title Creation 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.
Title Creation Quarter	Stores the quarter of the date in a display format such as Q1
Title Creation Year	Stores the year of the date in number format such as 2012
Title Creation 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 the month, which does not work properly when using the alphabetical field.
Title Creation 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.
Title Creation Date Filter	Used to filter report results by date.

Title Modification Date

The Modification Date table is a dimension table that stores details about modification of titles.

The Title Modification date is the date of the last change to the title.

Key fields are used whenever calculations are required. Description fields may be used for formatting the display of the report. Alma stores the following types of fields:

Calendar Fields – These are date fields as they display in the calendar.
Fiscal Date Fields – These are date fields that match the institution's fiscal period. For the examples below, the fiscal period of the institution is for fiscal year 2012 that starts June 1, 2011 and ends May 31, 2012.

Using this dimension, the user can drill down from year to month to the specific date on which the physical title was created.

Title Modification Date
Field	Description	Additional Information
Title Modification 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.
Title Modification Start of Week	The date of the first business day of the week
Title Modification Week Number	The number of the week of the year
Title Modification Date	Stores the item modification date in a date format such as 2/29/2014.
Title Modification Month	Stores the month of the date in month description format such as February
Title Modification 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.
Title Modification Quarter	Stores the quarter of the date in a display format such as Q1
Title Modification Year	Stores the year of the date in number format such as 2012
Title Modification 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 the month, which does not work properly when using the alphabetical field.
Title Modification 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.
Title Modification Date Filter	Used to filter report results by date.

Dewey Classifications

Titles can be classified with Dewey Classifications.

In Dewey Classifications, topics are ordered in a hierarchy that is indicated by a three digit number. The highest level of the hierarchy is indicated by a number with one significant digit followed by two zeros, such as 600. The second level in the hierarchy is indicated by a number with two significant digits followed by one zero, such as 630. The third level in the hierarchy is indicated by a number with three significant digits such as 636.

Note that the Dewey number is taken from the 852 subfield h of the holdings record and not from the 082 of the bibliographic record.

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.

LC Classification

Using this dimension, the user can drill down from Group1 to Group4. In each level, the user may see measures accumulated to the relevant group and see the number of items grouped by classification.

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.

For a Knowledge Article related to LC Classifications, see Analytics LC Classification code shows Unknown even though a call number is present in Alma.

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.

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.