2024-10-31 Metadata Management Meeting notes

Announcements

Bugfest is getting ready to start. See here for a timeline, instructions, and a link to the kick-off presentation recording.

MM Prioritization Process

@Jennifer Eustis @Charlotte Whitt

The Product Council is (or will soon be) asking that the SIGs implement a prioritization process - https://folio-org.atlassian.net/wiki/spaces/PC/pages/4885190/Prioritization

(From Raegan- Please note that this meeting is just to start us thinking about the process and we will not be discussing priorities at this time.)

Backstory: It has been about a year, Acq SIG wanted transparency about issues discussed, being worked on, closed, etc. 

Prioritizing Acq SIG Topics

They want people to set up an account in Atlassian to vote on issues with labels “acq-sig-topics”

They can then create a topic tracker --this helps track functionality and related tickets. 

This was presented to PC as a way to highlight how a SIG might rank functionality and determine any gaps in functionality.  This has been very successful for the ACQ sig. 

Data Import and BELA also have a topic tracker—transparency in what has been discussed (BULK edit doesn’t have voting but PO’s do a prioritization process for each release).

Data Import Implementers Topic Tracker

Bulk Edit Resource Management Implementation Topics

MM has a similar spreadsheet in MM SIG parking lot 

Want to make sure SIGS have support they need to make their priorities a reality. 

We need to determine how we want to set priorities/development trajectory for MM.

Laura: One challenge: we don’t necessarily have a clear set of Apps for which we have authority.  We need to define the scope of what MM should prioritize because there is so much that could be MM but also areas that could impact other SIGs areas of concern.  What do we want to be in scope for MM prioritization?

Charlotte: the PC did an overview of all the apps and how they are associated with all the different sigs. We can start with that list to see if it is accurate.  We could also define scope practically, for example if data import is working on prioritizing certain things, we have memebes on that group already.

Amanda in chat: we could also work with Cross-App Interaction SIG

Nancy: We should look at our priorities as a group instead of worrying about stepping on other peoples toes.  Curious about how the voting works in the Acquisitions group?  Answer from Jennifer: in JIRA, in right hand corner you can watch an issue and you can also vote for an issue under the actions menu.  Giving a thumbs up just means you think the issue is important. 

Lynn: Likes the voting function, allows you to track your own activity (you can create dashboards in your own JIRA account).  Most people aren’t interacting this way because they don’t have an account set up so we need to create community buy in to create accounts and interact this way. 

Jennifer; This is something to bring back to PC—to encourage people to have an account with Confluence to use this feature. Creating your own dashboards can be really helpful for individuals to track what they are watching. 

Charlotte: We could create a dashboard for MM SIG to help present to PC our priorities. If you could add comments on any given feature, you can add how many times the group has discussed it.

Jennifer: We already have two boards “Metadata Management Road Map”  https://folio-org.atlassian.net/jira/dashboards/10302

And the bug tracker https://folio-org.atlassian.net/jira/dashboards/10220

Raegan: Who do we need to contact to discuss user level settings?  It seems like everyone across the board is bringing up user level settings but nobody is taking responsibility for them. 

Jennifer: This is a question for the PC, but also once you have an issue that has been around for so many years, has so many votes, has been discussed so many times, then you can illustrate how much people want something and that is helpful to present to the PC.

Charlotte: We could have this as a topic for all of our remaining meetings for 2024 to work on this process together.  We can make a stronger case if we can determine features that really are more of a priority to us.

Jenn Colt: The hope is that PC members can create a users group who can edit these dashboards to get them properly handed off.

Jennifer: it is work to maintain these dashboards so we would also have to consider how we want to manage that (should we have a group of volunteers, so it isn’t just the co-chairs dealing with it).

Lynne: suggestion to add labels/tags to the JIRA issues to make it easier to find them (most people don’t have the permissions to add these)

Charlotte: maybe “MM-SIG_priority”

Sara: How does it work with Dashboards that are organized by Flowers, when a feature or Jira is shifted to a future flower after some period? ANSWER from Charlotte: Yes, Sara, we probably need to enhance the MM Road Map dash board. We want to keep an eye on all work (even that which isn’t addressed by a particular flower release).  Just like Acquisition sig lists features being voted for but not scheduled for development yet. 

Jennifer: We need to take a larger role in pointing things out, for example we may want to add to announcements when a feature has been bumped from one release to another

How to create an account: Go to Welcome the FOLIO Wiki page: https://folio-org.atlassian.net/wiki/spaces/COMMUNITY/overview?mode=global

And follow directions there

Charlotte: Just chatted with Peter, and there is no limit on how many FOLIO members who can sign up for a Jira account

Raegan: We need to do some preliminary work on figuring out our dashboards before we can start prioritizing together

Lynne: Maybe we start with tagging JIRA issues with MM-Sig so we can find them

Charlotte: as a start we can make a list of features where label is missing and then someone with permissions can add them

Jennifer: Devoting ten minutes each meeting to discussing this process is a good place to start

PC updates

@Charlotte Whitt

2024-10-31 Product Council Meeting Notes

Call for Bugfest testers: Yogesh Kumar pointed out that setting up the Bugfest enivironment require a lot of configuration. The Ramsons Bugfest test will run over three weeks (11/11-11/29). See more on Ramsons (R2 2024) Testing. The testing effort for Ramsons is doubled in size compared with Quesnelia due to the architectural changes introducing Eureka. Yogesh and his QA testers in average do 20 test rail tickets a day. List of testers who have signed up for Bugfest test at previous Bugfest tests.

New claiming functionality for Sunflower: Joe Reimers presented the idea for a new app for Claiming (Acquisition). Currently is this functionality part of the Receiving app, but the receiving app does not support claiming as separate workflow. The new work will be done by the Thunderjet team. Feature: UXPROD-4274. UX-mock up:

Open

BELA (Bulk Edit and Lists App)

Jennifer Eustis

No meeting.

Data Import Working Group

Jennifer Eustis

2024-10-30 Data Import Subgroup meeting

We discussed the documentation needs for Data Import. These are being tracked in this spreadsheet.

quickMARC Subgroup update

Raegan Wiechert

No meeting