GLIB - Google Library Inventory project

Solution Overview

Self-service reporting on Google Library Inventory database (GLIB) for library staff. GLIB stores data from Google scanning projects that date from 2004 to present. GLIB tables contain

• Item and bibliographic metadata for inventory of volumes sent to Google for scanning
• URNs that link to full text for scanned materials
• Transaction records that track items through the Google scanning workflow including when an item was scanned or not scanned
• Detailed information about the quality of the scan 
• Information regarding physical condition of the item that affects the scan, including preventing scanning 

The document purpose is to discover the Business Needs of the project including business objectives, current problems and situations to solve, assumptions and constrains. The document should provide a clear idea on the project scope, requirements and success criteria.

Solution Background

GLIB data was previously available in Cognos library reporting system which was retired in 2020. This project will restore reporting capability in HART. 

Business Need

• Address underlying data integrity issues by populating Alma system generated identifiers in place of Aleph identifiers that are subject to change and deletion by staff. 
• Investigate options for remediation that will restore item metadata for deleted and missing items
• Evaluate database structure with the goal of reducing or eliminating capture of Alma metadata that is already available in other database tables
• Establish new processes for maintaining the base. How often to refresh GRIN report table and conditions look-up, updating record identifiers for barcodes that no longer exist in Alma (destructive scanning workflow), updating record identifiers when items or a FIG holding is moved to a different bib.

Provide calculated fields to easily report on

• Scanned (Y/N)
• Date of scan
• Date not scanned
• Active item (Y/N)
• Metadata available (Y/N)

What business problems should be addressed? What benefits should the project bring?

Solution Timelines

• Solution Design: Click or tap to enter a date.
• Development/Feature Freeze: Click or tap to enter a date.
• QA Testing: Click or tap to enter a date.
• Bug Fixes: Click or tap to enter a date.
• UAT Testing: Click or tap to enter a date.
• Go Live: Click or tap to enter a date.
• Other Dates: Specify other key project dates

Communication & Responsibilities

BI Engineering Team

Project Stakeholder Team

Solution Scope/Deliverables

• Barcode Look-up Dashboard for GLIB
  • Modified version of the Barcode Lookup dashboard that includes the current status of items sent for scanning. Input a list of up to 9,999 barcodes or use a csv file as input for larger sets. Return core metadata regarding the status of the item record, whether scanned, physical condition(s), availability of full text, URN, and core bibliographic metadata. Include in results the barcodes that were not found in GLIB.
  • Identify materials sent to Google with a particular condition (Foldouts, Tight Gutter, Poor condition, Publication date, Overchop, Duplicate book) and whether scanned or not.
  • Output from tables: GLIB Items, GRIN Report, Alma Items, Alma Bibs.
• Google scanning statistics Dashboard
  • Items sent for scanning in the past month, year (calendar and fiscal), range of years or all years.
  • Number of successfully scanned items, number of items that were not scanned and condition that prevented scan 
  • Number of items available in full text
  • Number with overall error percentage above a certain number (if this indicates a poor quality scan)
  • Provide filters for dates, library and location
  • Support action links or some other functionality to get item details?
  • Output from tables: GLIB Items, GRIN Report, Alma Items, Alma Holdings, Alma Bibs
• Change to viewability of item analysis
  • Identify items where viewability has changed from FULL_VIEW in quarter (or in whatever time period we decide to update GRIN report). Is this actionable in Alma by suppressing or un-suppressing FIG holdings?
  • Output from tables: GLIB Items, GRIN Report, Alma Items, Alma Holdings, Alma Bibs
• Analysis of serial items scanned and not scanned
  • Show physical items and scanned items or the same bib in a side-by-side view or comparison.
  • Include counts of physical and digitized items so serials with some but not all volumes digitized can be identified.
  • For serial bibs with a FIG holding, show volume/issue display with FIG data for items that have been sent to Google and which have and have not been scanned. 
  • Output from tables: GLIB Items, GRIN Report, Alma Items, Alma Holdings, Alma Bibs
• Collection analysis Dashboard
  • By library, location, LC subject, call number, etc. create a shelf list that includes title, author and other core bibliographic data along with counts of physical items and items digitized by Google. The list includes bibs with and without scanned item
  • Output from tables: Alma bibs, Alma holdings, Alma items, GLIB Items. 

Provide any mock up or design screenshots

Target Audience

Data Sources and Backend Architecture

<<Provide list of each data source to be used i.e. DB Name, Schema Name, Table Names>>

<<Provide any details on required ETL, dependencies, timliness of the load job, frequency of execution, or high level relationship diagrams of data structures.>>

Background Documents

Find background doc on Harvard-Google workflows including initial data ingest, updates and ongoing process for new projects

Google Library Inventory dataBase specification (1/28/2008)

Cognos: FIG Barcode lookup report 

Cognos SQL for FIG Barcode lookup report

Cognos: FIG Barcode lookup sample output

Cognos: GLIB data model

Alma to GLIB database field mappings

GLIB Data Source in HART - Analytics use cases