Rialto Collection Development
The subject area includes folders for project details, project measures, recommendation details, bibliographic details, and physical item details.
The Rialto Collection Development subject area includes folders for project details, project measures, recommendation details, bibliographic details, and physical item details. It also incorporates user and date dimensions for comprehensive reporting. Users can track project progress, measure outcomes, and analyze key metrics, including the number of active projects, recommendations acted upon, and overall workflow efficiency. These insights help ensure alignment with institutional priorities and broader strategies, including shared print initiatives.
This subject area is available to all Alma users with the Design Analytics role.
Field Descriptions
The following fields are available for Rialto Collection Development:
Rialto Collection Development — Field Descriptions
Project Measures
|
Field
|
Description
|
Additional Information
|
Data Type
|
Data Size
|
|---|---|---|---|---|
|
Num of Projects (Total)
|
The total number of collection development projects.
|
|
NUMERIC
|
|
|
Num of Projects (Deselection)
|
The number of collection development projects of Deselection type.
|
|
NUMERIC
|
|
|
Num of Projects (Retention) |
The number of collection development projects of Retention type.
|
|
NUMERIC
|
|
|
Num of Projects (Project Created)
|
The number of collection development projects with status Retention.
|
|
NUMERIC
|
|
|
Num of Projects (Recommendations Generated)
|
The number of collection development projects with status Recommendations Generated.
|
|
NUMERIC
|
|
|
Num of Projects (Review in Process)
|
The number of collection development projects with status Review in Process.
|
|
NUMERIC
|
|
|
Num of Projects (Project Completed)
|
The number of collection development projects with status Project Completed.
|
|
NUMERIC
|
|
|
Num of Projects(Project Modified)
|
The number of collection development projects with status Project Modified.
|
|
NUMERIC
|
|
|
Num of Initial Recommendations (Total)
|
The total number of recommendations generated for a project.
|
|
NUMERIC
|
|
|
Num of Initial Recommendations (Deselection)
|
Total number of recommendations generated for projects of Deselection type.
|
|
NUMERIC
|
|
|
Num of Initial Recommendations (Retention)
|
Total number of recommendations generated for projects of Retention type.
|
|
NUMERIC
|
|
|
Num of Remaining Recommendations
|
Number of recommendations remaining in the recommendations list.
|
This is the Analytics implementation of the Items in list field in the UI. If there are no user changes to the recommendations list, the number of remaining recommendations is equal to the number of initial recommendations.
|
NUMERIC
|
|
|
Num of Unique Titles
|
Count of distinct bibliographic titles (MMS IDs) represented in the recommendations.
|
|
NUMERIC
|
|
|
Num of Unique Items
|
Count of distinct physical items (Items IDs) represented in the recommendations.
|
|
NUMERIC
|
|
Project Details
|
Field
|
Description
|
Field Location in Alma
|
Data Type
|
Data Size
|
|---|---|---|---|---|
|
Number of Recommendations Generated
|
The total number of recommendations that were generated for the project, regardless of later handling or removal.
|
Collection Development > Retention or Deselection
|
NUMERIC
|
|
|
Project Creation Date
|
The creation date of the project.
|
Collection Development > Retention or Deselection
|
DATE
|
|
|
Project Creator
|
The name of the project creator.
|
Collection Development > Retention or Deselection
|
VARCHAR
|
255
|
|
Project Description
|
The description of the project.
|
Collection Development > Retention or Deselection
|
VARCHAR
|
4000
|
|
Project ID
|
The ID of the project.
|
Collection Development > Retention or Deselection
|
NUMERIC
|
|
|
Project Modification Date
|
Modification date of the project.
|
Collection Development > Retention or Deselection
|
DATE
|
|
|
Project Modified By
|
The name of the project modifier.
|
Collection Development > Retention or Deselection
|
VARCHAR
|
255
|
|
Project Name
|
The name of the project.
|
Collection Development > Retention or Deselection
|
VARCHAR
|
255
|
|
Project Status
|
The status of the project.
|
Collection Development > Retention or Deselection
|
VARCHAR
|
255
|
|
Project Type
|
The type of the project.
|
Collection Development > Retention or Deselection
|
VARCHAR
|
255
|
|
Recommendations Generation Date
|
The date when recommendations were last generated for the project.
|
Collection Development > Retention or Deselection > View Recommendations
|
DATE
|
|
|
Within My Institution
|
Flag indicating whether the project is restricted to reviewing items only within the institution's own libraries.
|
Collection Development > Retention or Deselection
|
VARCHAR
|
3
|
Project Recommendations Details
|
Field
|
Description
|
Field Location in Alma
|
Additional Information
|
Data Type
|
Data Size
|
|---|---|---|---|---|---|
|
Handled Action
|
System-generated indication of how a handled recommendation was processed.
|
Not available in Alma UI.
|
For example, withdrawn, moved, added to set, via a job.
|
VARCHAR
|
50
|
|
Item ID
|
Identifier of the physical item associated with the recommendation
|
Collection Development > Items for Retention / Deselection > Summary Section
|
Used to join the Physical Items dimension.
|
VARCHAR
|
255
|
|
MMS ID
|
Identifier of the bibliographic record (title) associated with the recommendation.
|
Collection Development > Items for Retention / Deselection > Summary Section
|
Used to join the Bibliographic Details dimension.
|
VARCHAR
|
255
|
|
Recommendation ID
|
System-generated unique identifier of the recommendation row.
|
Not available in Alma UI.
|
|
NUMERIC
|
|
|
Recommendation Status
|
The status of the recommendation.
|
Not available in Alma UI. Only active recommendations are displayed in the Items for Retention / Deselection list.
|
Possible values:
|
VARCHAR
|
255
|
Bibliographic Details
Ex Libris works with content providers worldwide to enrich the metadata available in the Alma Community Zone. To enrich the journal/serial content in the CZ, we work directly with the Library of Congress CONSER feed for electronic serials, which we match against our knowledge base to enrich with all of the relevant metadata fields that they supply (for more details, see Community Zone Serial Records Enrichment) and enrich the CZ records with all relevant metadata, including the 050 fields (when available).
In the case of book content, we work with multiple providers who are willing to share their metadata with the Alma community globally (for more details, see Community Zone Monograph Records Enrichment). If you have local access to these classifications, you may want to consider working with the local extension for these records whenever an update is not available. (For more details, see Working with Local Extension Fields for Community Zone-linked Records.)
The Bibliographic Details table contains two kinds of fields: those derived from the MARC record and those that come from Alma. Although in analytics there is no distinction made between these fields, for explanatory purposes, we have divided them into two tables below.
The Bibliographic Details table includes all bibliographic records in the catalog whether they have inventory or not.
| Field | Note | Mapping from MARC21 | Mapping from UNIMARC | Mapping from Dublic Core | Data Type | Data Size |
|---|---|---|---|---|---|---|
|
Action Note
|
A note that contains information about the retention and the retention reason of the bibliographic record.
|
583
|
Not relevant
|
Not relevant
|
VARCHAR
|
4000
|
|
Active Course Code
|
Active Course Code is the code of the course in the Alma course reserves. For more information see here.
|
|
|
|
VARCHAR
|
4000
|
|
Active Course Name
|
Active Course Name is the name of the course in the Alma course reserves. For more information see here.
|
|
|
|
VARCHAR
|
4000
|
|
Author
|
The term Author refers to the individual or group of individuals responsible for creating or producing the work being documented. The author is the primary contributor to the work, and their name is typically listed prominently in the bibliographic record to identify the originator of the content. Depending on the type of work and the citation style, the author's name may be followed by additional information such as their credentials, institutional affiliation, and the date of publication.
|
100,110,111
|
700,701,710,711
|
Currently empty, planned to come from dc:creator, dcterms:creators
|
VARCHAR
|
4000
|
|
Author (Contributor)
|
The Author (Contributor) role refers to the specific role or function played by an individual or group in the creation or production of a work. This role is important for cataloging and documenting the contributions of different individuals or entities to a particular resource. The Author (Contributor) role is a way to categorize and describe the responsibilities of contributors beyond just being the primary author.
|
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
|
VARCHAR
|
4000
|
|
Begin Publication Date
|
The Begin Publication Date refers to the earliest date associated with the publication or release of a particular work. It is a critical piece of information that helps users understand when the work was first made available to the public. The publication date can be essential for citing the work correctly, tracking its historical context, and assessing its relevance to specific time periods.
|
008 pos. 07-10
|
100.Date1
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
BIB 008 MARC
|
The contents of the MARC 008 bibliographic field. The BIB 008 field in a MARC bibliographic record is a fixed-length data element used to provide additional information about the bibliographic record itself. It contains various control information that helps catalogers and library systems manage and process the record.
|
008
|
|
Not relevant for Dublin Core
|
VARCHAR
|
50
|
|
BIB LDR MARC
|
The BIB LDR refers to the Leader field (LDR) within the bibliographic record. The Leader is a fixed-length data element that provides control information about the bibliographic record itself. It is a critical component of MARC records, and each position within the Leader serves a specific purpose. The Leader field is typically 24 characters in length. The Leader field is used to convey fundamental information about the structure, organization, and characteristics of the bibliographic record.
|
LDR
|
|
Not relevant for Dublin Core
|
VARCHAR
|
50
|
|
Bibliographic Acquisition Accession Number Note
|
The identification code assigned to materials acquired in a single and separate transfer of custody.
|
541 e
|
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
Bibliographic ID
|
A Bibliographic ID is a unique identifier assigned to a specific bibliographic entry or resource. It serves as a way to distinguish and locate a particular work within a library's catalog or database. The purpose of a bibliographic ID is to facilitate efficient retrieval and management of bibliographic records and to ensure that each record is distinct.
|
010 excluding numeric subfields
|
020 a
|
dcterms:identifier dcterms:ISBN, dcterms:identifier dcterms:ISSN
|
VARCHAR
|
255
|
|
Bibliographic Level
|
The Bibliographic Level is a classification that describes the scope and content of a bibliographic record. It helps users understand the nature of the resource being described in the record. The bibliographic level is often indicated using a one-letter code or abbreviation. Common bibliographic levels include: Monograph (m), Serial (s), Collection (c), Integration (i), Monographic Series (a), and so forth.
|
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
|
VARCHAR
|
255
|
|
Bibliographic Lifecycle
|
The Lifecycle of the bibliographic record. Possible values are Deleted and In Repository. This allows you to filter reports and to remove Deleted records.
|
|
|
|
VARCHAR
|
50
|
|
Bibliographic Rank
|
Alma assesses the comprehensiveness and depth of MARC 21 bibliographic entries, considering various elements such as identifiers, names, subjects, informative LDR and 008 fields, publication details, among others. This evaluation is reflected in the Bibliographic Rank, designed as a useful aid for libraries in pinpointing records requiring further scrutiny. For more information, see here.
|
|
|
|
INT
|
|
|
Bibliographic Source of Acquisition Note
|
The name of the people or organization that is the source of the material.
|
541 a
|
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
Brief Level
|
Brief Level refers to the level of detail provided in a bibliographic description. It indicates how much information is included in the bibliographic record, with brief descriptions containing less detailed information compared to full or comprehensive descriptions. In Alma, ten levels of brief records can be defined from 01 through 10, where 01 represents the most brief record and 10 represents a full record. For more information see here.
|
|
|
|
VARCHAR
|
2
|
|
Category of Material
|
The Category of Material is a classification or designation that describes the format or physical nature of the material being cataloged. It helps users and catalogers understand the medium in which a resource is presented.
|
Position 0 of the 007 field
|
200 b
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
Chinese Classification
|
The Chinese Classification of the bibliographic record. For more information, see here.
|
VARCHAR
|
50
|
|||
|
Collection ID
|
The ID of the collection or collections the bibliographic record is associated with as defined at Resources > Manage Inventory > Manage Collections.
Relevant only for bibliographic records that are part of a collection.
One MMS_ID can be attributed to multiple titles collections, therefore a delimited list of collections are defined for the MMS.
|
|
|
|
VARCHAR
|
4000
|
|
Collection Name
|
The Name of the collection or collections the bibliographic record is associated with as defined at Resources > Manage Inventory > Manage Collections.
Relevant only for bibliographic records that are part of a collection.
|
|
|
|
VARCHAR
|
4000
|
|
Created with AI
|
Indicates that the bibliographic record of the resource was created by the AI Assistant.
|
|
|
|
VARCHAR
|
4
|
|
Creation Date
|
The timestamp of the bibliographic record creation date.
|
|
|
|
DATETIME
|
|
|
Creation Date (Calendar)
|
The creation date without a timestamp. This date format is useful when filtering the report by date.
|
|
|
|
DATE
|
|
|
Creator
|
The name of the user that created the record
|
|
|
|
VARCHAR
|
255
|
|
DC Coverage
|
DC Coverage refers to an element used to provide information about the spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under which the resource is relevant.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dc:coverage
dcterms:coverage dcterms:spatial dcterms:temporal |
VARCHAR
|
|
|
DC Description
|
DC Description refers to Dublin Core (DC) metadata elements used to describe resources in a standardized way, particularly in digital libraries and online cataloging systems.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dc:description
dcterms:description dcterms:abstract |
VARCHAR
|
4000
|
|
DC Format
|
The file format, physical medium, or dimensions of the resource. The information in this field is entered as free text.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dc:format
dcterms:format |
VARCHAR
|
256
|
|
DC License
|
DC License is a Dublin Core element used to specify the terms and conditions associated with the use of a resource. It provides information about the licensing or copyright status of a digital or physical resource, allowing users to understand how they can legally use, share, or redistribute the resource. The DC License element is particularly important in digital libraries, repositories, and online cataloging systems where access to digital content is provided.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
It will be populated by dcterms:license
|
VARCHAR
|
4000
|
|
DC Provenance
|
DC Provenance refers to an element used to provide a statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dcterms:provenance
|
VARCHAR
|
4000
|
|
DC Relation
|
DC Relation refers to an element used to provide information about a related resource to the described resource.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dc:relation
dcterms:relation dcterms:isVersionOf dcterms:hasVersion dcterms:isReplacedBy dcterms:replaces dcterms:isRequiredBy dcterms:requires dcterms:isPartOf dcterms:hasPart dcterms:isReferencedBy dcterms:references dcterms:isFormatOf dcterms:hasFormat dcterms:conformsTo |
VARCHAR
|
4000
|
|
DC Rights
|
DC Rights refers to an element used to provide information about the intellectual property rights or copyright status of a resource. This element helps users understand the legal rights and permissions associated with the resource and whether there are any restrictions on its use.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dc:rights and dcterms:rights
|
VARCHAR
|
4000
|
|
DC Source
|
DC Source refers to an element used to provide information about a related resource from which the described resource is derived.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dc:source
dcterms:source |
VARCHAR
|
4000
|
|
DC Type
|
DC Type refers to an element used to provide information about the nature or genre of the resource.
|
Relevant only for Dublin Core
|
Relevant only for Dublin Core
|
dc:type
dcterms:type |
VARCHAR
|
255
|
|
Dewey Classification
|
The Dewey classification of the record.
|
|
|
|
VARCHAR
|
255
|
|
Dewey Classification Top Line
|
The first 3 digits of the Dewey Classification
|
|
|
|
VARCHAR
|
15
|
|
Earliest Possible Publication Year
|
A normalized version of the publication date to the earliest possible value when the exact date is not known. It is taken from MARC21 008 pos. 07-10 or UNIMARC 100.Date1.
This field is normalized with all non-numeric characters converted to 0s. Values below 1500 and over 6000 will have the value 1.
|
|
|
|
VARCHAR
|
255
|
|
Edition
|
Edition refers to a specific version or variation of a publication. The edition information provides details about changes, updates, or variations that have occurred since the original publication. Including the edition helps users and researchers identify the specific version of a book or other resource they are looking for.
|
250 subfields a,b
|
205 a,b,f,g
|
dcterms:isVersionOf
|
VARCHAR
|
255
|
|
Electronic location and access
|
The location and access URl for the electronic resource.
|
856 all subfields
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
End Publication Date
|
The End Publication Date is the second date available in the 008 field, and it is used to indicate "Date 2." It is described as "A date specified by the code in 008/06 (Type of date/Publication status)."
|
008 pos. 11-14
|
100.Date2
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
Enriched with AI
|
Indicates that the bibliographic record of the resource was enriched by the AI Assistant.
|
|
|
|
VARCHAR
|
4
|
|
Export to National Libraries
|
This field appears only when the Customer Parameter national_catalog is defined. The field name is as defined in the parameter. Possible values:
|
|
|
|
VARCHAR
|
255
|
|
Export to WorldCat
|
Indicates that publication status is applied to a record.
Possible values:
|
|
|
|
VARCHAR
|
255
|
|
Form of Item
|
The Form of Item refers to a specific code or indicator that describes the physical format or medium of the resource being cataloged. This information helps library users understand the physical characteristics of the item and whether it is in a print or non-print format.
|
008 pos. 29 (Maps and Visual Material) or 23 (other material configurations)
|
|
Not relevant for Dublin Core
|
VARCHAR
|
1
|
|
General Note
|
A General Note is a field used to provide additional information or commentary about the resource being described. General notes can include various types of information that may not fit into specific structured fields within the bibliographic record. These notes are often used to convey contextual details, historical significance, or other relevant information about the resource.
|
500 a, 5
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
Government Publication
|
A Government Publication is a term used to identify materials that are published or produced by government entities at various levels of government, including federal, state, local, and international governments.
For more information regarding the values of MARC 008 Pos. 28, see here.
|
008 pos. 28
According to MARC21 Format for Bibliographic Data, 008 pos. 28 is Government Publication for the following material types: Books, Computer Files, Continuing Resources, Maps, and Visual Materials.
For Music 008 pos. 28 is Accompanying matter. For Mixed material 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
|
VARCHAR
|
1
|
|
ISBN
|
ISBN is a unique identifier for books, and it is used to facilitate the identification and cataloging of books and related materials.
Field in analytics includes also cancelled and invalid ISBNs. |
020 a, z 776 z
|
010 a
|
dcterms:identifier dcterms:ISBN
|
VARCHAR
|
255
|
|
ISBN (Normalized)
|
An ISBN that has been formatted or standardized according to established rules or conventions.
|
|
|
|
VARCHAR
|
255
|
|
ISBN Valid
|
A unique identifier for books and related materials. To be considered valid, an ISBN must adhere to the established ISBN standards and conventions.
Field in analytics does not include cancelled and invalid ISBNs. |
020 a
|
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
ISSN
|
An ISSN (International Standard Serial Number) is a unique identifier for serial publications, which include periodicals, journals, magazines, and other recurring publications.
Field in analytics includes also cancelled and invalid ISSNs. |
022 l,a 776 x (for non-physical records)
|
011 a f
|
dcterms:identifier dcterms:ISSN
|
VARCHAR
|
255
|
|
ISSN (Normalized)
|
An ISSN that has been formatted or standardized according to established rules or conventions.
|
|
|
|
VARCHAR
|
255
|
|
ISSN Valid
|
A unique identifier for serial publications. To be considered valid for bibliographic records, an ISSN must adhere to the established standards and conventions for ISSN formatting and structure.
Field in analytics does not include cancelled and invalid ISBNs. |
022 a
|
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
Language Code
|
Language codes are used to indicate the language(s) in which a particular resource is written or presented. Language codes are typically standardized to ensure consistency in cataloging and bibliographic records.
|
008 pos. 35-37
|
101 a
|
Currently comes from dc:language. Planned to come from dc:language and dcterms:language
|
VARCHAR
|
255
|
|
Language Description
|
The language name of the title, based on the Language Code field on the record.
|
|
|
|
VARCHAR
|
255
|
|
Language Of Cataloging
|
The Language of Cataloging refers to the language in which the cataloging or metadata for a particular resource is created.
|
040 b
|
100 a,22-24
|
Not relevant for Dublin Core (Value None is displayed)
|
VARCHAR
|
4000
|
|
LC Classification Top Line
|
The combined LC code and classification call 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:
The LC Classification Top Line will contain one value. For MARC21, if the bibliographic record has:
Recent data may not be available if it has not yet been received from CONSER.
|
|
|
|
VARCHAR
|
50
|
|
Link ID
|
The link ID, if the record is linked to the Community Zone or Network Zone. 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.
|
|
|
|
VARCHAR
|
50
|
|
Linked to CZ
|
Indicates if the record is linked to the Community Zone.
|
|
|
|
VARCHAR
|
3
|
|
Linked to NZ
|
Indicates if the record is linked to the Network Zone.
|
|
|
|
VARCHAR
|
3
|
|
Local Note
|
A Local Note is a type of note that provides specific information or instructions related to a library's unique policies, holdings, or services. Local notes are typically used to convey information that is specific to the individual library or cataloging institution and may not be relevant to libraries elsewhere. For Borrowing Requests, the Source is stored in this field.
|
590 a, 5
|
|
Not Relevant for Dublin Core
|
VARCHAR
|
4000
|
|
043 - Local Param 01
|
These fields of information are from MARC fields in Alma, which were configured specifically for your institution. All MARC fields other than control fields can be added as local parameters. Accordingly, MARC fields from 010 to 999 can be mapped to local parameters, including indicators. It is possible to define and select specific subfields for export, rather than including all subfields by default.
You can define:
To utilize these fields, it is necessary to contact Ex Libris Support and provide them with the three-digit MARC field codes, as well as any specific subfields or indicators you would like included. |
|
|
|
VARCHAR
|
4000
|
|
Managed by Provider
|
Indicates if the electronic resource is managed by the provider. Possible values are Yes or No.
Relevant only for electronic resources.
|
|
|
|
VARCHAR
|
3
|
|
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
This field holds a fixed set of values designated for all record formats. For DC, the mapping is controlled from Configuration Resources > Cataloging > DCMI Material Type Mapping page. Any dc:type value not defined on this pages gets by default the value Computer File. For more information, see DCMI Material Type Mapping.
|
VARCHAR
|
4000
|
|
Material Type Code
|
Code of the material type described above (in Material Type).
|
MARC control LDR Material Type
|
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
MMS ID
|
The MMS ID of the inventory item (physical, electronic, or digital).
|
VARCHAR
|
255
|
|||
|
Modification Date
|
The latest (most recent) timestamp of the bibliographic record modification date.
|
DATETIME
|
|
|||
|
Modification Date (Calendar)
|
The latest (most recent) modification date without a timestamp. This date format is useful when filtering the report by date.
|
DATE
|
|
|||
|
Modified By
|
The name of the user that modified the record.
|
VARCHAR
|
255
|
|||
|
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.
|
VARCHAR
|
50
|
|||
|
Network Number
|
A Network Number typically refers to a unique identifier assigned to a bibliographic record within a library network or consortium.
|
035 a z
|
053 a z
|
dc:identifier , dcterms:identifier
|
VARCHAR
|
4000
|
|
OCLC Control Number (019)
|
The OCLC Control Number (019 field) is used by OCLC to record and index OCLC control numbers of records that have been deleted or will be processed as duplicate records.
For more information on the OCLC Control Number 019 and its subfields, see here.
Leading zeros are not displayed.
|
019 a
When the subfield begins with one of the following prefixes:
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
OCLC Control Number (035a)
|
Subfield "a" in the 035 field is used to record the main OCLC Control Numbers.
For more information on the OCLC Control Number 035 and its subfields, see here.
Leading zeros are not displayed.
|
035 a
When the subfield begins with one of the following prefixes:
|
035 a
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
OCLC Control Number (035a+z)
|
The OCLC Control Number can include both the main OCLC Control Number in subfield "a" and any related or canceled OCLC Control Numbers in subfield "z." This practice is useful for indicating changes or updates to cataloging records and for maintaining a historical record of previous control numbers associated with the same resource.
For more information on the OCLC Control Number 035 and its subfields, see here.
Leading zeros are not displayed.
|
035a+z
When the subfield begins with one of the following prefixes:
|
035a+z
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
OCLC Control Number (035z)
|
Subfield "z" in the 035 field is used to record related or canceled OCLC Control Numbers, providing a historical record of control numbers associated with a specific resource.
For more information on the OCLC Control Number 035 and its subfields, see here.
Leading zeros are not displayed.
|
035 z
When the subfield begins with one of the following prefixes:
|
035 z
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
Open Access
|
Open Access (OA) refers to a publishing model that provides unrestricted and free access to scholarly and research publications on the Internet. It signifies that the full text or content of the publication is freely available to anyone, without requiring payment or subscription. Values are Yes and No.
|
Based on 506 f 506 2
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4
|
|
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
|
VARCHAR
|
255
|
|
Originating System
|
The system where the bibliographic record originated.
If Unknown is displayed in this field, see the following document: How to set up Alma so that the “Originating System” in Analytics will be properly populated.
|
|
|
|
VARCHAR
|
4000
|
|
Originating System ID
|
The ID of the record in the originating system where the bibliographic record originated.
|
VARCHAR
|
255
|
|||
|
Originating System Version
|
The Originating System Version is the metadata record field that enables uploading records in the correct sequence by preventing the update of an existing record with an older version of the same record. This prevents older bibliographic records from overlaying or merging with newer records. The Originating System Version field is created from the record’s 005 control field the first time the record is imported. For information regarding normalizing the Originating System Version field, see the Update originating system information process and the procedure To configure normalization for managing the Originating System and Originating System Version information.
|
VARCHAR
|
16
|
|||
|
Peer Reviewed
|
Indicates if the article was peer reviewed.
|
VARCHAR
|
4
|
|||
|
Place Code
|
The Place Code is a code that represents the place of publication for a printed or published resource.
|
008 pos. 15-17
|
102$$a
|
dcterms:spatial
|
VARCHAR
|
50
|
|
Place of Publication - City
|
The city where a printed or published resource was published or produced.
|
Derived from the place code in 008 pos. 15-17.
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".
|
Not relevant for UNIMARC
|
Not relevant for Dublin Core
|
VARCHAR
|
200
|
|
Place of Publication - Country
|
The country where a printed or published resource was published or produced.
|
Derived from the place code in 008 pos. 15-17.
For a list of country codes, see:
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".
|
Derived from the place code 102$$a.
For a list of country codes, see:
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.
|
Not relevant for Dublin Core. Value No place, unknown, or undetermined is displayed)
|
VARCHAR
|
200
|
|
Place of Publication - State
|
The state where a printed or published resource was published or produced.
|
Derived from the place code in 008 pos. 15-17.
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".
|
Not relevant for UNIMARC
|
Not relevant for Dublin Core
|
VARCHAR
|
200
|
|
Preservation Status
|
The preservation status of the title in Rosetta Plus/Pro.
Possible values:
|
|
|
|
VARCHAR
|
255
|
|
Provider Name
|
The name of the provider who manages the bibliographic record that is included in the CZ (Community Zone). Relevant only for electronic titles that are linked to the CZ and when an external provider manages the CZ record.
|
|
|
|
VARCHAR
|
255
|
|
Publication Date
|
The Publication Date refers to the date when a printed or published resource was officially issued, published, or made publicly available.
|
The publication date is determined as follows:
|
The publication date is determined as follows:
|
dc:date, dcterms:date, dcterms:created, dcterms:available, dctrems:issued, dcterms:dateAccepted
|
VARCHAR
|
255
|
|
Publication Place
|
The Publication Place refers to the city or location where a printed or published resource was officially published, issued, or produced.
|
260 a. When 260 a is empty, it is taken from 264 a
|
210 a 214 a
|
Not relevant for Dublin Core (use Place Code)
|
VARCHAR
|
255
|
|
Publisher
|
The Publisher refers to the entity or organization responsible for producing, printing, and distributing a printed or published resource.
|
260 b
264 b
|
210 c
214 c
|
dcterms:publisher, dc:publisher
|
VARCHAR
|
255
|
|
Record Format
|
The format of the bibliographic record. Examples:
|
|
|
|
VARCHAR
|
4000
|
|
Resource Type
|
Constructed based on existing bibliographic fields such as the LDR and 008. For more information, see The Resource Type Field.
|
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
Series
|
A Series refers to a related group of publications or resources that share common characteristics, themes, or subjects and are published under a common title or series name.
|
800 t,v
810 t,v
811 t,v
830 a,n,p,v
|
410 a,h,i,o,t,x
|
dcterms:isPartOf
|
VARCHAR
|
4000
|
|
Series Statement
|
A Series Statement refers to the title or name of a series to which a printed or published resource belongs.
|
490 a,v x
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
Source of Description Note
|
A note used by the Community Zone with details on AI enrichment.
|
588 $$a
|
Not relevant
|
Not relevant for Dublin Core
|
VARCHAR
|
1000
|
|
Subjects
|
Subjects refer to the specific topics, themes, or subjects covered by a printed or published resource.
|
6XX excluding 69X, 630, 689
|
600 a,b 602 603-8 610 616 617
|
dc:subject dcterms:LCSH,MESH,DDC,UDC,LCC
|
VARCHAR
|
4000
|
|
Subjects (Names)
|
Subjects (Names) refers to the specific individuals, organizations, or entities associated with a printed or published resource.
|
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
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
|
Suppressed From Discovery
|
Indicates whether the record is suppressed from external discovery systems.
|
|
|
|
VARCHAR
|
3
|
|
Title
|
The Title refers to the name or title of a printed or published resource. The title is one of the most critical elements of bibliographic cataloging because it helps users identify and distinguish one resource from another.
|
245 a,b
249 a,b,c,v
|
200 a,c,d,e,h,i
|
dc:title
|
VARCHAR
|
4000
|
|
Title (Complete)
|
The information from MARC field 245, subfields $a, $n, $p, $h, $b, $c, $f, $g, $k, $s.
|
245 a,n,p,h,b,c,f,g,k,s
|
200 a-i
|
dc:title, dcterms:title, dc:alternative
|
VARCHAR
|
4000
|
|
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
|
VARCHAR
|
4000
|
|
Title (Normalized)
|
The normalized Title. This field is useful when you want to compare titles that may have been catalogued differently. 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:
|
245 a,b,n,p
249 a,b,c,v
|
200 a,c,d,e,h,i
|
dc:title
|
|
4000
|
|
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
|
VARCHAR
|
110
|
|
Title Committed to Retain
|
Title Committed to Retain refers to a commitment made by a library to retain and preserve a specific resource. This commitment is important for ensuring the long-term availability and accessibility of important scholarly or historical materials.
Indicates (Yes/No) if the bibliographic record is marked as Committed to Retain.
|
Configurable from Configuration > Resources > Collection Retention > Bibliographic Collection Retention Definition. For more information, see Bibliographic Record Retention.
|
|
Not relevant for Dublin Core
|
VARCHAR
|
4
|
|
Type of date
|
The Type of Date refers to the nature or purpose of a date included in the record. It specifies what the date represents or signifies within the bibliographic context. The type of date can provide important information to users and catalogers about the significance of the date included in the record.
|
008 pos. 6
For more information on the options available for Type of date in 008 pos. 6, see here.
|
100 pos 8
|
Not relevant for Dublin Core
|
VARCHAR
|
255
|
|
Uniform Resource Identifier
|
A Uniform Resource Identifier (URI) is a string of characters used to identify a resource on the internet or within a particular system. URIs are often used to provide direct links or references to online resources related to the bibliographic entry, such as a digital version of a book, an electronic journal article, or additional related materials.
|
856 u
|
856 u
|
dc:identifier (dcterms:URI) ,dcterms:identifier (dcterms:URI)
|
VARCHAR
|
4000
|
|
Uniform Resource Identifier Field Exists
|
Indicates whether a Uniform Resource Identifier (URI) Exists for the bibliographic record. Values are 0 or 1, where "0" means No and "1" means Yes.
Indicates if 856 subfield u contains data.
|
|
|
Not relevant for Dublin Core
|
INT
|
|
|
Uniform Title
|
A Uniform Title is a standardized title used to represent a specific work, especially when that work has been published under multiple titles or in various editions, languages, or formats.
|
240 130
|
500
The Uniform Title is only mapped if the first indicator = 1.
If the first indicator for UNIMARC 500 is empty or 0, the value is not mapped to Analytics.
|
Not relevant for Dublin Core
|
VARCHAR
|
4000
|
Classification Dimensions
Dewey Classification
The Dewey Classification is displayed in Analytics in the Dewey Classifications shared dimension, available in several subject areas. Dewey classification information is derived from the bibliographic record in most subject areas, except for the Physical Items subject area, where it can be derived from either the holdings record or the bibliographic record.
From the Bibliographic Record:
- For MARC21
Taken from field 082$$a
https://www.loc.gov/marc/bibliographic/bd082.html - For UNIMARC
Taken from field 676$$
There are three levels of the Dewey Classification stored in Alma Analytics. Each level is referred to by a numbered group (Group1, Group2, and Group3).
The group fields display the names as follows:
Dewey Classifications Groups
Using the hierarchy option in this dimension, the user can drill down from Group1 to Group3. In each level, the user can see measures accumulated to the relevant group.
For example:
-
000 Computer science, information & general works
o 010 Bibliography
o 000 Computer science, information & systems
-
005 Computer programming, programs & data
-
000 Computer science
-
004 Data processing & computer sciences
-
This is presented in Alma Analytics as follows:
Dewey Classifications
If there is more than one classification code, the last one appears.
| Field | Description | Data Type | Data Size |
|---|---|---|---|
| Group1 | The name (label) of the first Dewey classification level. | VARCHAR | 500 |
| Group2 | The name (label) of the second Dewey classification level. | VARCHAR | 500 |
| Group3 | The name (label) of the third Dewey classification level. | VARCHAR | 500 |
| Dewey Number |
The Dewey Number is a unique classification code assigned to a specific subject or topic category. The first 3 digits of the Dewey Classification. |
VARCHAR | 15 |
| Dewey Classifications | The hierarchy column that allows the user to drill down from the first level of the Dewey Classification to the third level. |
LC Classifications
The Library of Congress Classification (LCC) is displayed in Analytics in the LC Classification shared dimension, available in several subject areas. LC classification information is derived from the bibliographic record in most subject areas, except for the Physical Items subject area, where it can be derived from either the holdings record or the bibliographic record.
From the Bibliographic Record:
- For MARC21
Taken from field 050$$a. If 050$a has no content, 090$a is used.
https://www.loc.gov/marc/bibliographic/bd050.html - For UNIMARC
Taken from field 680$$a
There are five levels of the LC Classification stored in Alma Analytics. Each level is referred to by a numbered group (Group1, Group2, Group3, Group4 and Group5).
Using the hierarchy option in this dimension, the user can drill down from Group1 to Group4. In each level, the user can see measures accumulated to the relevant group.
For example:
- SF1-1100 Animal culture
- SF87 Acclimatization
- ….
- SF191-275 Cattle
- SF250.5-275 Dairy processing. Dairy products
- SF221-250 Dairying
This is presented in Alma Analytics as follows:
LC Classifications
If there is more than one classification code, the last one appears.
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)
| Field | Description | Data Type | Data Size |
|---|---|---|---|
| Group1 | Group1 is the name given for the first level of the LC Classification and is the primary division used to organize and group related topics, subjects, or materials. | VARCHAR | 500 |
| Group2 | Group2 is the name given for the second level of classification. | VARCHAR | 500 |
| Group3 | Group3 is the name given for the third level of classification. | VARCHAR | 500 |
| Group4 | Group4 is the name given for the fourth level of classification. | VARCHAR | 500 |
| Group5 | Group5 is the name given for the fifth level of classification. | VARCHAR | 500 |
| Classification Code | Classification Code refers to a unique alphanumeric identifier assigned to a specific subject or topic category within the library's classification system. The Classification Code is composed of letters and numbers that represent various facets of a work, such as its subject, genre, or format.
For example, in the LC classification "PN1997.2.D56," the "PN" portion represents the general subject area (Performing Arts), and the "1997.2.D56" further refines the classification to a specific work or aspect within that category. |
VARCHAR | 50 |
| End Range | End Range refers to the concluding point of a designated range within a classification system. The End Range specifies the final classification number or identifier within a defined range that encompasses a set of related subjects, topics, or materials.
For example, in PS501-689 (Collections of American literature), the end range is PS689. Possible end range values are hard coded to the end of LC Classification groups. |
VARCHAR | 50 |
| End Range Number | The numbers that come after the letter(s) in the end range. | DOUBLE | |
| Start Range | Start Range refers to the beginning point of a designated range within a classification system. The Start Range indicates the initial classification number or identifier within a specified range that encompasses a set of related subjects, topics, or materials.
For example, in PS501-689 (Collections of American literature), the start range is PS501. Possible start range values are hard coded to the beginning of LC Classification groups. |
VARCHAR | 50 |
| Start Range Number | The numbers that come after the letter(s) in the start range. | DOUBLE | |
| LC Classifications | The Hierarchy column that enables 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. | Hierarchy |
For a Knowledge Article related to LC Classifications, see Analytics LC Classification code shows Unknown even though a call number is present in Alma.
NLM Classifications
| Field | Description | Additional Information | Mapping from MARC 21 | Data Type | Data Size |
|---|---|---|---|---|---|
|
Has W1
|
Indicates that the 060 field of the bibliographic record has a value containing the W1 code. This indicates that the item is a journal. A second value in the 060 field is the subject classification code that appears for the NLM Classification Code analytics field.
|
|
|
|
|
|
NLM Classification Code
|
The letters at the beginning of the NLM classification code entered in the MARC field.
|
|
Taken from the 060 $a field or, if empty, from the 096 $a field of the MARC record.
|
VARCHAR
|
250
|
|
NLM Classification Number
|
The numbers that come after the letters of the NLM classification code.
|
|
Taken from the 060 $a field or, if empty, from the 096 $a field of the MARC record.
|
VARCHAR
|
50
|
|
NLM Group 1-5
|
The names of the levels of classification.
|
The group name as defined by NLM.
|
|
VARCHAR
|
4000
|
Physical Item Details
The Physical Item Details table is a fact table that stores all measures relating to specific physical items such as number of items, time loaned, etc. This table also holds details about the physical items, including barcode and material type. The primary key is ITEM_ID.
|
Field
|
Description
|
Additional Information
|
Data Type
|
Data Size
|
|---|---|---|---|---|
|
Accession Number
|
A sequential code used to file items on the shelf.
|
|
|
|
|
Barcode
|
The unique identifier of the specific physical item.
|
This field is limited to 128 characters.
|
|
|
|
Base Status
|
Indicates the availability of the item in its permanent location (in place/not in place).
|
|
|
|
|
Chron I
|
The main level of chronology - usually the year.
|
|
|
|
|
Chron J-M
|
Additional chronology fields.
|
|
|
|
|
Creation Date
|
Holds the date the physical item was created.
|
This date is assigned by Alma when the physical item is created.
|
DATE
|
|
|
Creator
|
Holds the username of the operator that created the physical item.
|
|
VARCHAR
|
255
|
|
Description
|
Description of the item.
|
|
|
|
|
Display Temp Call Number
|
A normalized temporary call number for display.
|
|
|
|
|
Due Back Date
|
Indicates the date that an item in a temporary location is due back to its permanent location.
|
|
|
|
|
Due Back Date (Calendar)
|
Indicates the date without the timestamp that an item in a temporary location is due back to its permanent location.
|
|
|
|
|
Enum A
|
The main level of enumeration - usually the volume.
|
|
|
|
|
Enum B-H
|
Additional enumeration fields.
|
|
|
|
|
Expected Receiving Date
|
The date when a purchased item is expected to arrive at the library.
|
|
|
|
|
Expected Receiving Date (Calendar)
|
The date without the timestamo when a purchased item is expected to arrive at the library.
|
|
|
|
|
Fulfillment Note
|
The Fulfillment note.
|
For more information, see the Physical Item Editor Page - Notes Tab table in Updating Item-Level Information.
|
|
|
|
Has Committed to Retain
|
Indicates if the library has committed to retain the item. This enables librarians to mark items and prevent them from being withdrawn.
|
This feature is also supported in import, export and API workflows.
|
|
|
|
Holdings ID
|
The unique identifier of the holdings.
|
|
|
|
|
Internal Note
1-3 |
Internal notes 1-3
|
For more information, see the Physical Item Editor Page - Notes Tab table in Updating Item-Level Information.
|
|
|
|
Inventory Date
|
The last time the inventory was checked.
|
This field is a calendar field that can be edited manually using the item editor. It can be used for any need. The common use is to track missing items. To do this, enter the date that a missing item was last searched for in the Inventory Date field.
|
|
|
|
Inventory Date (Calendar)
|
The last date without the timestamp when the inventory was checked.
|
|
|
|
|
Inventory Number
|
The inventory number.
|
|
|
|
|
Inventory Price
|
The price of the physical inventory for each physical item.
|
|
|
|
|
Is Magnetic
|
Whether the item is magnetic material or not.
|
This is used in the circulation desk in order not to desensitize magnetic material
|
|
|
|
Item Call Number
|
The item call number for display.
|
|
|
|
|
Item Call Number Type
|
The item call number type.
|
|
|
|
|
Item Copy ID
|
The ID of the copy of the item.
|
The field “Item Copy ID” folder comes from the item record and not from the holdings record. It is visible in the physical item editor in the “general” tab and is called “Copy ID”.
|
|
|
|
Item Policy
|
The name of the item policy that defines the conditions under which a request for this item can be fulfilled.
|
|
|
|
|
Last Loan Date
|
The last time the item was loaned.
|
This loan measure includes migrated data.
|
|
|
|
Last Loan Date (Calendar)
|
The last date without the timestamp that the item was loaned.
|
|
|
|
|
Last Loan Date (Not in House)
|
The last time the item was actually loaned.
|
This field is available only for loans that were handled in Alma and does not include migrated data.
|
|
|
|
Last Loan Date (Not in House) (calendar)
|
The last date without the timestamp that the item was actually loaned.
|
|
|
|
|
Library Address Line 1
|
The first line of the address of the institution. It usually includes the building number and the street name.
|
Configured from Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is Address Line 1.
|
VARCHAR
|
1000
|
|
Library City
|
The city of the library.
|
Configured from Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is City.
|
VARCHAR
|
255
|
|
Library Code
|
The library code.
|
|
VARCHAR
|
50
|
|
Library Country
|
The country of the library.
|
Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is Country.
|
VARCHAR
|
320
|
|
Library Name (Active)
|
The library name of active (not deleted) libraries.
|
|
VARCHAR
|
255
|
|
Library Postal Code
|
The postal code of the library.
|
Configured from Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is Postal code.
|
VARCHAR
|
200
|
|
Library State Province
|
The state or province of the library.
|
Configured from Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is State/Province.
|
VARCHAR
|
320
|
|
Lifecycle
|
Indicates whether the item is active or deleted
|
The following are possible values:
|
|
|
|
Location Code
|
Stores the code of the location of the physical item.
|
|
|
|
|
Material Type
|
Describes the nature of the material represented by the item record
|
|
VARCHAR
|
4000
|
|
Modification Date
|
Holds the date the physical item was modified
|
|
DATETIME
|
|
|
Modified By
|
Holds the user name that modified the physical item
|
|
VARCHAR
|
255
|
|
Originating System ID
|
The ID of the item in the source system from which it has been imported
|
|
|
|
|
Permanent Call Number
|
A code used to file the items on the shelf
|
When there is no call number, this field's value is set to Unknown.
|
|
|
|
Permanent LC Classification Top Line
|
Stores the LC class number top line that represents the code and numbers until the first period, followed by a letter.
|
For example, when lc_class_number is NB933.F44, the top line is NB933).
|
|
|
|
Physical Condition
|
The physical condition of the item.
|
Possible values:
|
|
|
|
Physical Item ID
|
The ID of the physical item
|
|
|
|
|
Process Type
|
The type of process for the physical item
|
These are process types defined by Alma. Possible values are:
The values for this field are not the values of the Process Type field in Alma in the Physical Item Editor – General Information Tab. Those values are configurable sub-process types that appear when the Alma process type is in progress.
|
|
|
|
Provenance Code
|
A code used to identify separate items that belong to different groups (but may be shelved together)
|
|
|
|
|
Public Note
|
The public note of the item.
|
|||
|
Receive Number
|
A sequential number assigned by the library to help maintain inventory.
|
For more information, see Configuring Physical Item Sequences.
|
|
|
|
Receiving Date (Calendar)
|
The date the material was actually received/activated for the first time
|
|
|
|
|
Receiving Date and Time
|
The date and time the material was actually received/activated for the first time
|
|
|
|
|
Replacement Cost
|
The replacement cost
|
In order to filter your report based on the Replacement Cost field, you must add a second copy of this field and edit the formula with the following CAST("Physical Item Details"."Replacement cost" AS DOUBLE). This causes Alma Analytics to treat the field as numeric.
|
|
|
|
Retention Note
|
A free-text note concerning the library's commitment to retain the item.
|
|
|
|
|
Retention Reason
|
The reason the library has committed to retain the item.
|
The list of reasons can be configured by an administrator.
|
|
|
|
Statistics Note 1-3
|
Holds statistic notes
|
For more information, see the Physical Item Editor Page - Notes Tab table in Updating Item-Level Information.
|
|
|
|
Storage Location ID
|
The ID of the storage location.
|
|
|
|
|
Temp Call Number Type
|
A call number type provided when the item is in a temporary location
|
|
|
|
|
Temp Physical Location In Use
|
Whether the item is currently (at the time at which the report is run) in a temporary location or in a permanent location.
For example:
An item was moved from a permanent location to a temporary location on November 28, 2017. It was loaned on November 29, 2017, and when it was loaned, it was still in a temporary location. It was returned from loan on December 13, 2017. On December 14, 2017 it was returned to its permanent location.
If an Analytics report was run between November 28 and December 13, the Temp Physical Location In Use is Yes. If the report was run before November 28 or after December 13, the Temp Physical Location In Use is No.
|
|
|
|
|
Temporary Item Policy
|
The code of the temporary item policy
|
|
|
|
|
Temporary Library
|
The temporary library
|
|
|
|
|
Temporary Library Code (Active)
|
The code of the active (not deleted) temporary library
|
|
|
|
|
Temporary Library Name (Active)
|
The name of the active (not deleted) temporary library
|
|
|
|
|
Times Loaned
|
The number of loans, including all loans in Alma.
|
|
|
|
|
Weeding Date
|
A date assigned by the library as the weeding date. By default it is the date that the weeding number was assigned
|
|
|
|
|
Weeding Number
|
A sequential number assigned by the library to help maintain inventory.
|
For more information, see Configuring Physical Item Sequences.
|
|
|
Project Creator
| Field | Description | Additional information | Data Type | Data Size |
|---|---|---|---|---|
| Project Creator Birth Date | Stores the birth date of the project creator. |
DATE
|
|
|
| Project Creator Campus Code | Stores the campus code of the project creator. |
VARCHAR
|
50
|
|
| Project Creator Cataloger Level | The cataloger level of the project creator. |
VARCHAR
|
255
|
|
| Project Creator Creation Date | The project's creation date for the project creator. |
DATE
|
|
|
| Project Creator Creator | The user that created the project creator's user record. |
VARCHAR
|
255
|
|
| Project Creator Disable All Login Restrictions | Indicates if the project creator has IP login restrictions disabled. |
VARCHAR
|
3
|
|
|
Project Creator Expiry Date
|
Stores the date on which the project creator is to expire and no longer be able to get service from the system.
|
Changing the project creator's expiry date is one way to control item due dates that extend beyond the end of a semester and must be shortened to the end of the semester. For more information, see How to Make Items Have Due Dates at the End of the Semester.
|
DATE
|
|
| Project Creator First Name | Stores the project creator’s first name. |
VARCHAR
|
255
|
|
| Project Creator Full Name | The project creator's first and last name. | There is no option to include the middle name. |
VARCHAR
|
511
|
| Project Creator Has Role Other Than Patron | Indicates if the patron has a role other than Patron. |
VARCHAR
|
3
|
|
| Project Creator Has Role Other Than Patron and Instructor | Indicates if the patron has a role other than Patron and Instructor. |
VARCHAR
|
3
|
|
| Project Creator Identifier 1 - 2 | The pre-configured identifiers for the project creator. | The identifier field allows you to enrich the project creator details exported to Analytics with additional identifiers. Choosing a specific identifier to be included in the project creator details is done in Alma (in a table that is currently restricted to Ex Libris staff). For assistance in defining this field, contact Ex Libris Support.
Only one value per identifier is supported.
|
VARCHAR
|
4000
|
| Project Creator Is Blocked | Indicates if the patron has an active block on the project creator record. |
VARCHAR
|
3
|
|
| Project Creator Job Category | Stores the job category definition to which the project creator belongs based on the Job Categories code table. |
VARCHAR
|
255
|
|
| Project Creator Job Description | Stores free-form text that describes the function of the project creator in the library. |
VARCHAR
|
255
|
|
|
Project Creator Last Activity Date
|
The last activity date in the project creator's user record. This refers to the last date that the project creator made a request or borrowed or returned an item.
|
|
DATE
|
|
| Project Creator Last Name | Stores the project creator’s last name. |
VARCHAR
|
255
|
|
| Project Creator Linked From Institution Code | In a fulfillment network, this is the ID of the external institution from which the user was copied. | Applies to the linked user in a fulfillment network. See Managing Users for more information. |
DOUBLE
|
|
| Project Creator Linked From Institution Name | In a fulfillment network, this is the name of the external institution from which the user was copied. | Applies to the linked user in a fulfillment network. See Managing Users for more information. |
VARCHAR
|
255
|
|
Project Creator Linked To Other Institution
|
Indicates if the project creator accessed Primo/Alma for services in another institution. Note that this does not necessarily indicate that the services were actually supplied or that a linked account was created.
|
Applies to the user in the source institution. Populated only if the user created a link from their institution to another institution via a fulfillment network. See Linking Users in Collaboration Networks for more information.
Possible values:
|
VARCHAR
|
10
|
| Project Creator Middle Name | Stores the middle name of the project creator. |
VARCHAR
|
255
|
|
| Project Creator Modification Date | The date of the last modification that is recorded in the project creator's user record. |
DATE
|
|
|
| Project Creator Modified By | The last person/system that modified the project creator's user record. |
VARCHAR
|
255
|
|
| Project Creator Patron Letters Opt In | The letters for which the project creator has opted in. |
VARCHAR
|
2000
|
|
| Project Creator Patron Letters Opt Out | The letters for which the project creator has opted out. |
VARCHAR
|
2000
|
|
| Project Creator Preferred First Name | Stores the project creator’s preferred first name |
See Preferred first / middle / last names for more information. |
VARCHAR
|
255
|
| Project Creator Preferred Language | The preferred language. |
VARCHAR
|
4000
|
|
| Project Creator Preferred Last Name | Stores the project creator’s preferred last name. | See Preferred first / middle / last names for more information. |
VARCHAR
|
255
|
| Project Creator Preferred Middle Name | Stores the project creator’s preferred middle name. | See Preferred first / middle / last names for more information. |
VARCHAR
|
255
|
| Project Creator Primary identifier | Stores the primary identifier that the project creator uses in order to log on to Alma. |
VARCHAR
|
255
|
|
|
Project Creator Purge Date
|
The purge date recorded in the project creator's user record.
|
|
DATE
|
|
| Project Creator Resource Sharing Library Code | The code of the resource-sharing library assigned to the project creator. |
VARCHAR
|
4000
|
|
| Project Creator Resource Sharing Library Name | The resource-sharing library assigned to the project creator. |
VARCHAR
|
4000
|
|
| Project Creator Statistical Categories 01-10 | These fields allow you to map ten statistical categories. This allows you to filter reports based on advanced project creator information typically stored in the statistical category fields. For more information, see Configuring Statistical Categories for Analytics. | No data will appear if statistical categories are scoped to specific libraries. (See Managing project creator Statistics). Data appears only when it is on the institutional level. |
VARCHAR
|
4000
|
|
Project Creator Status
|
Indicates if the project creator is active.
|
Possible values:
|
VARCHAR
|
8
|
| Project Creator Status Date | The date of the last status change of the project creator. |
DATE
|
|
|
| Project Creator User Email | The preferred email for correspondence of the project creator. |
VARCHAR
|
255
|
|
| Project Creator User Group | Stores the group with which the project creator is associated, such as Faculty, Graduate, or Student. |
VARCHAR
|
4000
|
|
| Project Creator User Group Code | The project creator group code. |
VARCHAR
|
255
|
|
| Project Creator User ID | Stores a unique internal ID of the project creator. |
VARCHAR
|
50
|
|
|
Project Creator User Record Type
|
Indicates if the project creator is a Public, Staff, or Contact project creator.
|
The possible values are:
See Managing Users for more information
|
VARCHAR
|
4000
|
| Project Creator User Title | The title of the project creator. | For more information, see Configuring User Titles. |
VARCHAR
|
50
|
| Project Creator User Type | Stores the values Internal and External. |
Possible values:
|
CHAR
|
20
|
Some fields in the Project Creator dimension are derived from the User Details page.
Project Creation Date
|
Field
|
Description
|
Additional Information
|
Data Type
|
Data Size
|
|---|---|---|---|---|
|
Project Creation Date
|
The creation date of the project.
|
The date in the format DD/MM/YYYY
|
DATE
|
|
|
Project Creation Start of Week
|
The date of the first business day of the week.
|
The date in the format DD/MM/YYYY
|
DATE
|
|
|
Project Creation Week Number
|
The number of the week of the year.
|
There are 52 weeks in a year.
|
VARCHAR
|
2
|
|
Project Creation Month Key
|
The month of the date in number format.
|
For example, February shows the number 2 in this column. This field is useful when you want to sorth by month.
|
INT
|
|
|
Project Creation Month
|
The month of the date in text format.
|
For example, February.
|
VARCHAR
|
20
|
|
Project Creation Full Month
|
The year and the month that the project was created.
|
The month in text format and the year. For example, Feb 25 (for February 2025)
|
VARCHAR
|
20
|
|
Project Creation Quarter
|
The quarter in the year in which the project was created.
|
The quarter of the date in a display format such as Q1
|
VARCHAR
|
20
|
|
Project Creation Year
|
The creation year.
|
The year of the date in the format YYYY . For example, 2025
|
VARCHAR
|
20
|
|
Project Creation Fiscal Month Key
|
The fiscal month of the date in number format.
|
For example, If the fiscal year starts in June, this column shows the number 1 for June, the number 2 for July, and so on.
|
INT
|
|
|
Project Creation Fiscal Year
|
The fiscal year of the date in string format.
|
The year is presented according to the description in the mapping table "Fund and Ledger Fiscal Period". For more information, see Configuring Fund and Ledger Fiscal Periods
|
VARCHAR
|
50
|
|
Project Creation Year-Month
|
The year and the month in which the purchase request was modified.
|
The year and the month in the format YYYY-MM
|
VARCHAR
|
250
|
|
Project Creation Date Filter
|
Used to filter project results by date.
|
Possible values:
|
VARCHAR
|
100
|
|
Project Creation Date |
Stores the Hierarchy column that allows the user to drill down from the year to the month to the specific modification date. |
|
|
|
Project Modified By
|
Field
|
Description
|
Additional Information
|
Data Type
|
Data Size
|
|---|---|---|---|---|
|
Project Modified By Birth Date
|
The birth date of the user that modified the project.
|
|
DATE
|
|
|
Project Modified By Campus Code
|
The campus code of the user that modified the project.
|
The full list of campus codes and names can be found in Configuration > General > Libraries > Define Campuses.
|
VARCHAR
|
50
|
|
Project Modified By Cataloger Level
|
The cataloger level of the user that modified the project.
|
For this to display in the UI, the Cataloger Permission Levels must be defined (in addition to the default level). See Cataloging Privileges for more information.
|
VARCHAR
|
255
|
|
Project Modified By Creation Date
|
The creation date of the user that modified the project.
|
|
DATE
|
|
|
Project Modified By Creator
|
The creator that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Disable All Login Restrictions
|
|
|
VARCHAR
|
3
|
|
Project Modified By Expiry Date
|
The expiry date of the user that modified the project.
|
After expiration, the user cannot login.
|
DATE
|
|
|
Project Modified By External ID
|
The external ID of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By First Name
|
The first name of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Full Name
|
The full name of the user that modified the project.
|
|
VARCHAR
|
511
|
|
Project Modified By Has Role Other Than Patron
|
Indicates if the user that modified the project has a role in addition to Patron.
|
|
VARCHAR
|
3
|
|
Project Modified By Has Role Other Than Patron and Instructor
|
Indicates if the user that modified the project has a role in addition to Patron and Instructor.
|
|
VARCHAR
|
3
|
|
Project Modified By Identifier 1-2
|
Two pre-configured user identifiers for the user that modified the project.
|
|
VARCHAR
|
4000
|
|
Project Modified By Is Blocked
|
Indicates if the user that modified the project is blocked. This is recorded in the record for the user that modified the project.
|
|
VARCHAR
|
3
|
|
Project Modified By Job Category
|
The job category of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Job Description
|
The job description of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Last Activity Date
|
The last date that a patron made a request or borrowed, or returned an item.
|
|
DATE
|
|
|
Project Modified By Last Name
|
The last name of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By User Linked from Institution Code
|
In a fulfillment network, this is the ID of the external institution from which the user was copied.
|
|
DOUBLE
|
|
|
Project Modified By User Linked from Institution Name
|
In a fulfillment network, this is the name of the external institution from which the user was copied.
|
|
VARCHAR
|
255
|
|
Project Modified By Linked to Other Institution
|
Indicates if the user that modified the project accessed Primo/Alma for services in another institution. Note that this does not necessarily indicate that the services were actually supplied or that a linked account was created.
|
Possible values:
|
VARCHAR
|
10
|
|
Project Modified By Middle Name
|
The middle name of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Modification Date
|
The date of the last modification of the record for the user that modified the project.
|
|
DATE
|
|
|
Project Modified By Modified By
|
The last person/system that modified the record for the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Patron Letters Opt In
|
The letters for which the user that modified the project has opted in. This is recorded in the record for the user that modified the project.
|
|
VARCHAR
|
2000
|
|
Project Modified By Patron Letters Opt Out
|
The letters for which the user that modified the project has opted out. This is recorded in the record for the user that modified the project.
|
|
VARCHAR
|
2000
|
|
Project Modified By Preferred First Name
|
The preferred first name of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Preferred Language
|
The preferred language of the user that modified the project.
|
|
VARCHAR
|
4000
|
|
Project Modified By Preferred Last Name
|
The preferred last name of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Preferred Middle Name
|
The preferred middle name of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By Purge Date
|
The purge date of the user that modified the project.
|
For more information, see Purging Users.
|
DATE
|
|
|
Project Modified By Resource Sharing Library Code
|
The code associated with the resource sharing library. This is recorded in the record for the user that modified the project.
|
|
VARCHAR
|
4000
|
|
Project Modified By Resource Sharing Library Name
|
The name of the resource sharing library in the record for the user that modified the project. This is the name of the library associated with the user that modified the project.
|
|
VARCHAR
|
4000
|
|
Project Modified By Statistical Category 1-10
|
Statistical categories (01-10) that are recorded in the record for the user that modified the project.
|
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.
|
VARCHAR
|
4000
|
|
Project Modified By Status
|
The status recorded for the record of the user that modified the project.
|
|
VARCHAR
|
8
|
|
Project Modified By Status Date
|
The last date when the status of the record for the user that modified the project was modified.
|
|
DATE
|
|
|
Project Modified By User Email
|
The user's email address of the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By User Group
|
The user group of the user that modified the project.
|
|
VARCHAR
|
4000
|
|
Project Modified By User Group Code
|
The user group code associated with the user group. This is recorded in the record for the user that modified the project.
|
|
VARCHAR
|
255
|
|
Project Modified By User Record Type
|
The record type for the user that modified the project.
|
VARCHAR
|
4000
|
|
|
Project Modified By User Title
|
The title of the user that modified the project.
|
For more information see Configuring User Titles.
|
VARCHAR
|
50
|
|
Project Modified By User Type
|
The user type in the record for the user that modified the project.
|
CHAR
|
20
|
Project Modification Date
|
Field
|
Description
|
Additional Information
|
Data Type
|
Data Size
|
|---|---|---|---|---|
|
Project Modification Date
|
The modification date of the project.
|
The date in the format DD/MM/YYYY |
DATE
|
|
|
Project Modification Start of Week
|
The date of the first business day of the week.
|
The date in the format DD/MM/YYYY
|
DATE
|
|
|
Project Modification Week Number
|
The number of the week of the year.
|
There are 52 weeks in a year.
|
VARCHAR
|
2
|
|
Project Modification Month Key
|
The month of the date in number format.
|
For example - February will show the number 2 in this column. This field is useful when you want to sort by month.
|
INT
|
|
|
Project Modification Month
|
The month of the date in text format.
|
The month, for example, February.
|
VARCHAR
|
20
|
|
Project Modification Full Month
|
The year and month that the project was modified.
|
The month in text format and the year. For example - Feb 25 (for February 2025)
|
VARCHAR
|
20
|
|
Project Modification Quarter
|
The quarter in the year in which the project was modified.
|
The quarter of the date in a display format, such as Q1
|
VARCHAR
|
20
|
|
Project Modification Year
|
The year in which the project was modified.
|
The year of the date in the format YYYY. For example - 2025
|
VARCHAR
|
20
|
|
Project Modification Fiscal Month Key
|
The fiscal month of the date in number format.
|
For example - If the fiscal year starts in June, this column will show the number 1 for June, the number 2 for July, and so on.
|
INT
|
|
|
Project Modification Fiscal Year
|
The fiscal year of the date in string format.
|
The year is presented according to the description in the mapping table "Fund and Ledger Fiscal Period". For more information, see Configuring Fund and Ledger Fiscal Periods.
|
VARCHAR
|
50
|
|
Project Modification Year-Month
|
The year and the month in which the project was modified.
|
The year and the month in the format YYYY-MM
|
VARCHAR
|
250
|
|
Project Modification Date Filter
|
Used to filter project results by date.
|
Possible values:
|
VARCHAR
|
100
|
|
Modification Date
|
The date in a hierarchy format
|
Stores the Hierarchy column that allows the user to drill down from the year to the month to the specific modification date. Using this column allows the user to view cumulative measures at each level of the hierarchy.
|
|
|
Recommendations Generation Date
|
Field
|
Description
|
Additional Information
|
Data Type
|
Data Size
|
|---|---|---|---|---|
|
Recommendations Generation Date
|
The generation date of the recommendation.
|
The date in the format DD/MM/YYYY |
DATE
|
|
|
Recommendations Generation Start of Week
|
The date of the first business day of the week.
|
The date in the format DD/MM/YYYY
|
DATE
|
|
|
Recommendations Generation Week Number
|
The number of the week of the year.
|
There are 52 weeks in a year.
|
VARCHAR
|
2
|
|
Recommendations Generation Month Key
|
The month of the date in number format.
|
For example - February will show the number 2 in this column. This field is useful when you want to sort by month.
|
INT
|
|
|
Recommendations Generation Month
|
The month of the date in text format.
|
The month, for example, February.
|
VARCHAR
|
20
|
|
Recommendations Generation Full Month
|
The year and month that the recommendation was generated.
|
The month in text format and the year. For example - Feb 25 (for February 2025)
|
VARCHAR
|
20
|
|
Recommendations Generation Quarter
|
The quarter in the year in which the recommendation was generated.
|
The quarter of the date in a display format, such as Q1
|
VARCHAR
|
20
|
|
Recommendations Generation Year
|
The year in which the recommendation was generated.
|
The year of the date in the format YYYY. For example - 2025
|
VARCHAR
|
20
|
|
Recommendations Generation Fiscal Month Key
|
The fiscal month of the date in number format.
|
For example - If the fiscal year starts in June, this column will show the number 1 for June, the number 2 for July, and so on.
|
INT
|
|
|
Recommendations Generation Fiscal Year
|
The fiscal year of the date in string format.
|
The year is presented according to the description in the mapping table "Fund and Ledger Fiscal Period". For more information, see Configuring Fund and Ledger Fiscal Periods.
|
VARCHAR
|
50
|
|
Recommendations Generation Year-Month
|
The year and the month in which the recommendation was generated.
|
The year and the month in the format YYYY-MM
|
VARCHAR
|
250
|
|
Recommendations Generation Date Filter
|
Used to filter the recommendation-generated results by date.
|
Possible values:
|
VARCHAR
|
100
|
Institution
The shared Institution dimension enables the Network Zone to view reports by institution. 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.
This dimension is available across all subject areas. It contains the following fields:
| Field | Description | Additional information | Data Type | Data Size |
|---|---|---|---|---|
| Institution Address Line 1 | The first line of the address of the institution. It usually includes the building number and the street name. | Configured from: Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is Address Line 1. |
VARCHAR | 1000 |
| Institution City | The city of the institution. | Configured from: Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is City. |
VARCHAR | 255 |
| Institution Code | The code of the institution. | Configured from: Configuration > General > Add a Library or Edit Library Information > Summary tab.
The label in Alma is Code located on the right pane. |
VARCHAR | 50 |
| Institution Country | The country of the institution. | Configured from: Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is Country. |
VARCHAR | 320 |
| Institution Name | The name of the institution. | Configured from: Configuration > General > Add a Library or Edit Library Information > Summary tab.
The label in Alma is Organization unit name. |
VARCHAR | 255 |
| Institution Postal Code | The postal code of the institution. | Configured from: Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is Postal code. |
VARCHAR | 200 |
| Institution State Province | The state or province of the institution. | Configured from: Configuration > General > Add a Library or Edit Library Information > Contact Information tab. This is taken from the address configured as the Preferred address.
The label in Alma is State/Province. |
VARCHAR | 320 |
| Institution Timezone | The timezone of the institution. | The timezone is set during implementation. | VARCHAR | 255 |