2016-12-21 Metadata Management Meeting notes

Determine recorder of minutes

Doreen

• We'll rotate this responsibility from meeting to meeting; moving in alphabetical order

• Recorder should share screen and other attendees can assist by viewing minutes and provide feedback

Participating as a member

Doreen

• SIG meetings: frequency; determine agreeable time slot

Recurring meeting time

Doreen

To be sensitive to our variety of time zones, suggesting that we establish a weekly standing meeting with two rotating time slots. For example, based on the Doodle poll, 12:00pm EST on Monday and 11:00am EST on Wednesday yielded the highest results and everyone (with a few exceptions) were able to make one or both slots. So our schedule would rotate from one week to the next:

• Week 1: Monday 12:00pm EST

• Week 2: Wednesday 11:00am EST

Recommendation that it might be best to have a single, regular timeslot to avoid confusion

Liaison to Product Council

@ChewN

• Representatives from all OLE partners, EBSCO, Index Data

• Need to coordinate activities in specifying requirements of FOLIO

• Each SIG has a liaison to PC

• Oversee existing SIGs and development of new SIGs 

• Find and enter links to documents @Doreen Herold

• Mid-January F2F meeting to talk about role of PC at Duke

• Not rewriting codebase of OLE; this is a "brand new animal"

Volunteer for Forum Facilitators

Doreen

Please contact @Doreen Herold if you are interested

Great way to keep in touch with the development of the project

Volunteer for OLE Weekly Report

Doreen

Please contact @Doreen Herold if you are interested

Review of the UX/UI and FM work (the Functional matrix doc https://docs.google.com/spreadsheets/d/1TsL6416PBgltjU6gL6AymHAbzjSUg7TRJWN-NdLtzTI/edit?usp=sharing)

Charlotte, D., Lisa

• Started in the summer of 2016

• went over functional matrix (165 use cases) and rate them

• SIGs were developed from this

• Entries in red were those use cases suggested by the group

• Look for Metadata Management SIG; includes use cases of interest to our SIG

• Comment about how review of FM helped as a starting point

• Presentation by Maike re: requirements catalog would be good to see (conversation about features and functionalities) @Doreen Herold add link

Demo of the Folio prototype  https://pr.to/D7XIAW/

Filip

• Filip is a UX/interaction designer

• Define what libraries need to achieve with the system

• Want system to be efficient and feel good when users use it

• Link to prototype https://share.proto.io/D7XIAW/

• Wants to avoid people creating work-arounds, where users are working outside the system because the system doesn't meet the need

• Email could be best tool for communicating; in beginning slack was being used but didn't seem to work well; also use the discuss site and the wiki

• From Peter:

  • To sign up for a wiki account, use: https://folio-org.atlassian.net/secure/Signup!default.jspa -- wiki.folio.org and issues.folio.org share the same user database.

  • https://discuss.folio.org/t/459

• Suggestion to set up a email list Anne Highsmith

Wrap up:

• Are our action items clear? What are our next steps?

• What did we learn today?

Doreen

• Review prototype and contact Filip

• What is beyond record editing that we need to inform Filip about?

• How to be clear about when our work crosses paths with other SIGs https://discuss.folio.org/t/zap-turbo-recap-resource-management-workshop-boston-nov-29-30-2016/439

• We need to develop the scope of this SIG

• Most developers have been from Index Data but will be changing soon: OLE, GBV/HBZ, Cornell; developers will take info we're gathering under consideration

• Filip does sketches/prototype and then hands off to developers; developers will need more input for their work; SIGs will be consulted along the way

• @Doreen Herold Doodle poll for weekly meetings

• Edit table to add your area of interest and expertise; helps us develop subteams