2019-07-25 Metadata Management Meeting notes

PC did not meet this week (pre-empted by stakeholders' meeting)

Consistent definition of "Go live" is desirable. 

Does go live mean "deal-breaker" or is a separate "deal-breaker" flag needed? What are we all considering "go-live" to mean?

Jennifer Eustis said at 5-colleges "Go Live" means "deal-breaker". Cornell was not necessarily thinking this way. They were considering work-arounds, if a work-around is available then they were not assigning a "go-live" status. 

Ann Kardos - Commented that this is an opportunity to rethink what they are doing completely.

Patty - "Go-live" was chosen instead of "deal breaker" to convey a concept of a "pioneer spirit". 

Jason - Some institutions are more risk adverse than others. Jason pointed out the concept of the MVP is a different construct than a "Go-live"

Suggestion: The need for clarification should go to Product Council.

Christie Thomas - "Go-live" should be deal-breakers. At Chicago they are trying to be accommodating to contribute, however, even if a workaround is possible, it is not necessarily feasible. We should assume best intentions - everyone is trying their best. 

Sara - The Jira tickets are not as clear as they could be. They are easily interpreted in different ways. The review may need to be done multiple times, possibly looking at issues in a holistic way. Having conversations about the Jiras is an important component.

Charlotte (via chat) - "Presentation of new features, and discuss them in context of existing features, could be a ‘monthly’ topic on the MM-SIG agenda"

Patty - A Jira filter can be made to enable a list of Jiras pertinent to this group to display.

Data Import - Not currently meeting. They developers are working on the back end.

MARCcat - In last meeting a ranking was reviewed. Missing features were reviewed. Ann-Marie noted the desire for MARCcat to be available for testing. Charlotte noted that while everything may not be ready, it may be advantageous to supply the group with something to look at. Charlotte suggested that we may want to consider two steps - 1) having MARCcat, out of context with FOLIO and 2) then, when ready, MARCcat in FOLIO.

Various ways of creating a set of records is needed. 

Laura - Was hoping to get an idea of where we see batch edits happening? Do we see this happening in any given app? What does this look like in the big picture?

• Ann Kardos (via chat) - "i like a helper app"
• Jennifer - envisions a cross app tool
• Sara - Since each app is so different, it may be most appropriate to have a batch edit tool for each app. Create something global that is lightweight, but then modify it for each app as needed.
• Christie - Proposed a centralized batch update app. So many of our processes rarely touch one type of data. Jacquie agreed, also adding that everything should be able to be updated, but limited by permissions. 
• Jessica - Echoed the need for one batch update since the data is interrelated. 
• Jason - Having one app is beneficial for workflow reasons, as well as user management control. There's a connection between the data warehouse and this app. The data warehouse currently scoped is restricted. 

Laura - It sounds like, ideally, we'd have a batch edit app. 

• Christie said a batch edit app is a "go-live" requirement. 
• Ann-Marie - batch import and export is more of a priority ?

Jason - "We 100% need batch delete". Ann-Marie said she'll have to check. 

• Christie - A lot can be taken care of by round-tripping data. We should explore reusing the batch import UI for global updates
• Ann-Marie – Export is parallel to identifying the records for batch. 

Laura - 5 colleges has put a lot of work into coming up with use cases. We can use these use cases to test this notion of beginning with concepts of export when considering batch edits.

Ann-Marie - Magda Zacharskawill be working with export. Export is currently scoped to Inventory. 

Laura - There may be a new subgroup focused on Export, assuming it's acceptable for Magda. In the meantime, if you are interested in working on export - let Laura know.

When ranking bulk export Jira, keep in mind that the ability to round trip data is a potential workaround. 

Sara - Do we have the tools and a basic understanding if it will be possible to round trip data like orders, and invoices - non-inventory specific 

Dennis - anything we cannot bulk edit, we should be able to import/export/overlay those various types of records (orders, invoices, holdings, etc.)

Laura, please look at the use cases and see if this is truly a problem.

Meeting adjourned.

Multiple Graphical Representations

Note: Charlotte has added following feature description (UXPROD) in Jira: 

UXPROD-1646 - Getting issue details... STATUS

Christie expressed hesitation about being too prescriptive about what the JSON should look like. She suggested spending time on the Functional Requirements. Suggestions for additional functional requirements were added to the Google doc: DRAFT - Multiple graphical representations in FOLIO. (Also linked above.) 

The group also would like to make recommendations as to what this should look like in the FOLIO interface. Example systems that work well?

https://wiki.folio.org/pages/viewpage.action?pageId=78336464

x

VZG

Stanford

Index Data