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
• report transactions that 

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

• Ongoing process for updating item data needs to address cases where scanned barcode is no longer found in Alma
• GLIB item table is missing rows for scanned items not found in Aleph/Alma
• Investigate options for remediation that will restore item metadata for deleted and missing items

Provide calculated fields to easily report on

• Date on file
• Scanned (Y/N)
• Date of scan
• Date not scanned
• In Alma Metadata a Google Scanned (Y/N) flag for items scanned

in need of incomplete 

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

Specify list of expected deliverables to be included as part of solution. Ex:

1. Sales Dashboard
2. Marketing Dashboard
3. Inventory Report

 Requirements (Repeat for each Deliverable)

Example Reports / Dashboard Mock Ups and Design

Provide any mock up or design screenshots

Target Audience

Business Objective/Metrics

<< Identify business need/problem this dashboard/report should solve.>>

Interactivity

<< Specify an interactivity that is desired. Ex. Filtering with prompts, drill-downs, navigations to other Views etc.>>

Access/Security

Specify any data-level security between the different user groups. Specify any other security privileges between the user groups i.e. read access vs read and write access

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