2021-04-15 Metadata Management Meeting notes

Philip Schreur

Reminder that feature prioritization process is due April 30

Dashboard development from ERM team. 

• • Allowing users to see info a glance
  • Reminders of things to do
  • Personalization
  • Extensibility beyond ERM
• All for except 2nd were worked on since reminders can touch on more areas of FOLIO
• Demonstrated 3 "widgets" in dashboard. The widgets are configurable.  The widgets merely collect info that is already there.
• They spoke with ERM group about desires for this dashboard and available widgets.
• Data right now coming from agreements and licenses, but the extensibility they want to include external resources. Ex. RSS Feeds
• See Dashboard Documentation
• See Also Slide Deck
• Release goal for this : Juniper

Bugfest

• 83% issues have been dealt with
• Confident that outstanding issues can be resolved in next few days.

Issue Resolution - Time to resolve? Prioritization. Will be discussing further. 

Juniper Release Schedule - 1 month for development. Considered a foundation release to stabilize features. 

Wolfcon - FOLIO's conference planning

• Opening 5 minute
• Product presentations
• Other presentations on integrations of FOLIO with 

Please claim some Data Import test cases! 

Pointing Features for Kiwi Release

Features to review:

MM Copy of Feature Pointing Worksheet (created by Charlotte - copy of Holly's complete spreadsheet and turned it into an MM copy)

Scaled down copy of feature pointing worksheet (created by Laura - copied Holly's - removed basic elements, tried to keep ones related to MM) Also note the "Inventory Only" tab on this sheet

Christie: At Chicago - Inventory, Data Import, quickMARC and associated apps are where they are focusing. These apps are comparatively underdeveloped. Are there strategic ways we need to think about this. +1 from Lehigh, Duke, 5C via chat to Christie's comment.  Despite Charlotte's continuing efforts, these are behind. Can this be ratified by this point process?

Jason:  Noted the interaction of Inventory with many other apps. It may be more productive to talk about specific points within Inventory

Jacquie: Agreed. Most of Duke's issues are MM related. "Baseline" functionality is not there. We must have the tools we have right now: import data, export, update - 
"Record collision avoidance, data import, data export, development of SRS and quickMARC" The

Jessica (via chat): "Collision detection/prevention is the thing I care about the most. Otherwise we are accidentally wiping out changes, creating new errors, etc."

Ann-Marie (via chat) - "We do have another dev team for Data Import/quickMARC starting now - Khalilah's Spitfire devs. I totally agree with everything that Christie said. A couple key parts that are even more under-developed are hooking up with acquisitions - we don't have importing of MARC data for orders and invoices yet, and that seems like really basic functionality that we still need to get the overall scope of Data Import's data taken care of, and then we keep refining on the rest - logs, error handling, field protection, etc." Also voiced the difficulties with MARCcat situation. Last 3 releases of data import testing have seen large architectural changes behind the scenes, which has taken development time. 

Ann-Marie also noted the Order Import deficit (unless using Michelle Suranofsky's from Lehigh U's Order Import tool)

Christie (via chat): "Right. And then we all have different local capabilities to address these needs. So how do we weigh what we can achieve locally right now for implementation vs what the product needs to be able to do to mature. (Thinking of global edits, for example.)"

Jacquie: Frustrating to have to vote for Industry Standard features and having to convince Capacity Planning. How can we move forward so we can implement? 

Charlotte:  A few years ago we set up the MVP ("minimal viable project") to be ready by summer 2021. That MVP got slimmer as we ran out of time and resources.  Acknowledged that FOLIO does not meet industry standards yet. Feels we have an opportunity with new Community Council and new Roadmap group to have a new plan so we do have a fully functional product. Search issues are being solved efficiently perhaps by Elasticsearch. There are some things to be optimistic about.

Ann-Marie (via chat): "Optimistic locking (collision detection) is another great example, Jessica. I think we're in agreement that it should be developed across many FOLIO apps and record types, but at the moment, most of the POs for the affected apps are waiting to see the proof of concept (for Inventory I think) before we  outline the required work for our apps"

Christie: Chicago's identified features for points. Ability to transfer holdings and items when they are associated with other records. Their workaround is to not do it. This is very important to Chicago.

From Charlotte (via chat) - "Here a document capture the follow up work on Transfer of holdings and item"

Felix Hemme

Theodor Tolstoy