...
- 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 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.
...
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/Almaby 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
...
on
...
- Scanned (Y/N)
- Date of scan
- Date not scanned
- In Alma Metadata a Google Scanned Active item (Y/N)
- Metadata available (Y/N) flag for items scanned
...
What business problems should be addressed? What benefits should the project bring?
...
Solution Scope/Deliverables
Specify list of expected deliverables to be included as part of solution. Ex:
...
Requirements (Repeat for each Deliverable)
...
- Barcode Look-up Dashboard
- 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. 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
- Google scanning statistics Dashboard
- Items sent in the past month, year (calendar and fiscal), range of years or all years.
- Percentage available in full text
- Number of Opted out, claimed
- Number with overall error percentage above a certain number
- Change to viewability of item analysis
- Identify items where viewability has changed 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?
- Analysis of serial items scanned and not scanned
- 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.
Provide any mock up or design screenshots
...
User Group | Business Need | Skill Set | User Story |
|
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
...
Data Sources and Backend Architecture
...