2020-08-06 Metadata Management Meeting notes

Texas A&M Fameflower test cases

Test input form

John Ballestro from TAMU shared their 'impressively robust' approach to testing. Have done two rounds of internal testing - for Edelweiss and Fameflower. Will start Goldenrod testing in September. In the TAMU model, multiple individuals took on cases so there is confirmation when something fails. Librarians and staff participated - from all units in the library.

New Resource Access convener: Jana Freitag. 

Reminder to view & comment on the Entities App Vision Statement

(We will discuss this at a future MM meeting)

Comments can be made in the document itself and will inform the future MM SIG discussion about the document.

Spheres for documentation work: Technical Infrastructure | Process | Content

Technical infrastructure - wiki not sufficient because organization not intuitive for those not heavily involved in the community. Possible tools: GitHub, Site generators (Hugo, Jeckyll, VuePress), CMS (Netlify, Forestry)

Process - documentation needs to be a part of the development process. Needs to be a part of the definition of done. 

Content - how will the contents be structured: ToC / navigation, contribution guidelines? 

Phase 1 : Demo environment, Test Git, draft ToC, Google Season of Docs candidates

Phase 2: Marketing, production environment, Pick an app to start with, Google Season of Docs projects

Phase 3: Core set of Go-Live apps, installation instructions, Google Season of Docs projects

Contributions by community members - need to develop a process to allow community members to  contribute documentation. Should not have to have knowledge of the system to be able to contribute to the documentation. There are options for this. 

Definition of done - Training for POs on the tools or an interface that does not require the POs to be familiar with the tools. End-user documentation first and developer documentation later. 

This documentation will be a part of a release so the right people need to have the right tools to do this. Who are the people and how many need to be a part of this activity for each app? 

Small group will be convened to work on the demonstration site - Table of Contents will be the first thing. it will be a group that can be reached out to as needed for feedback. Questions may also be about how to manage versions, etc. Would be nice to have representation from all of the SIGs, but not necessary. 

Q3 priorities: expanding mapping profiles, providing error logs, export by cql query. 

Mapping profile: Q2 - export must include instance and be in MARC, can export 7 holdings data elements and 5 item data elements in 9xx fields of bib record. Q3 - can export instance, holdings, and/or item records. Will be able to export 23 elements from instance records and additional fields from holdings and items. 

Error logs - Q2 - can report failed or successful; display number of errors, and logs for only the 25 most recent jobs. Q3 - Failed, completed, and completes with errors. Will be able to view the error logs, and display all previous export jobs. 

At some point will have the ability to delete completed jobs. Right now only 25 show but there will be a link to click and see All jobs. 

CQL query trigger: Q2 - can only be triggered by list of unique identifiers. Q3 - can trigger by CQL query. 

DATA EXPORT TIMELINE:

Q1 - Export SRS records

Q2 - Export instances from Inventory or SRS with a default mapping profile with holdings and item data in 9xx format. 

Q3 - See note above.

Q4 - EXPORT MFHD (from Inventory holdings and items data); Export in text delimited file; schedule export jobs. At the end of Q3 can export holdings that are associated with an instance (selected by instance identifiers). At the end of Q4 will be able to select holdings by holdings identifiers. 

Inventory data mapping preferences on export (spreadsheet) -https://docs.google.com/spreadsheets/d/1XvHmToGQwhzmMNlQ5-l1QTEDyUtDpdn_/edit#gid=2009797227

Add ideas here

https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit

VZG

Stanford

Index Data