2025-04-24 Metadata Management Meeting notes
- Raegan Wiechert
- Katie Rahman
- Jennifer Eustis
Meeting URL: Join our Cloud HD Video Meeting . The meeting password can be found here.
Date
Apr 24, 2025
Note taker
Katie Rahman
Recordings
Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on AWS from 2022 onwards: https://recordings.openlibraryfoundation.org/folio/metadata-management-sig/
Discussion items
Item | Presenter | Notes |
|---|---|---|
Announcements | ~2,500 Non-ECS test cases for Sunflower still need to be completed (see #folio-general announcement from earlier today) WOLFcon 2025 - submissions deadline is April 25, tomorrow. Felix mentioned that he has not submitted a WOLFcon session for the MM working meeting (which is usually held annually) because he will not be attending in person. Jennifer said that on the submission form there is an option to present virtually, and there are more people than last year to be in the room for the session. Members expressed interest. Felix offered to submit the form, so members can attend in person or virtually. | |
Should Data Import be its own SIG? |
| This topic first came up when discussing a Product Council initiative to obtain the top five priorities from each SIG and working group. With this project, the Product Council is looking for FOLIO gaps and trends. In addition, they hope to make sure FOLIO is developed holistically and each group is getting the support they need. This is also related to community-driven development. This topic was discussed at last week’s MM meeting where it was pointed out that the Metadata Management SIG covers many apps and functionality, and it is very complex. Because of the scope of metadata topics, there are some concerns that apps like Data Import will not get the attention they deserve. During this discussion, it was brought up whether the Data Import app would have more support if it had its own SIG. It was discussed a year ago as well, but, at the time, MM decided it should remain a working group. This was also discussed at the Data Import Working Group meeting yesterday. They did not reach a decision regarding Data Import having its own SIG. However, the possibility of Data Import being a working group for the Cross App SIG was mentioned. Several members discussed the possibility of Data Import being its own SIG. Katie mentioned that it is the app her institution has had the most issues with. Problems include imports getting stuck, unclear error messages, and problems with overlaying records. Also, Katie pointed out that development has focused on scripts to fix issues rather than looking into what caused the problem in the first place. Christie said that this has been an ongoing issue for a long time and asked about the SIG creation process. Her personal preference would be Data Import having its own SIG or exploring options to align with the Cross App SIG. Laura brought up that Data Import has not gotten the attention it deserves, and Data Import remaining a working group under MM may be contributing to the problem. Having its own SIG may give this app the prominence it deserves. Christie mentioned that she would be an initial convener if Data Import became a SIG, and Jennifer offered help. There was also discussion regarding if Data Import has its own SIG or if it is under the App Integration (Cross App) SIG, what would it mean for MM. Some MM members do not attend the Data Import Working Group and rely on Data Import reports during MM meetings. Christie mentioned that it would be good to continue to do reports or have a liaison. Raegan said that there will still be Data Import reports, and she will continue to invite Ryan to discuss flower releases. Jennifer brought up that only about a dozen people attend Data Import meetings (usually the same group of people) and the possibility that Data Import being its own SIG may increase participation. Raegan suggested approaching other SIGs, such as Acquisitions, to see if members would attend meetings more often if Data Import was its own SIG. Charlotte asked whether it would be helpful to include product owners in this discussion. Jennifer also mentioned that Folijet is split between Data Import and Inventory. Regarding Data Import development, Vivian mentioned that the focus has been reacting to issues (creating fixes) instead of proactively trying to solve what is causing the issue. Jennifer will reach out to the Acquisitions SIG, Data Import Working Group, and Cross App SIG and report back to MM. |
SIG Priorities (PC Pilot) |
| The Product Council is asking SIGS to provide five features for prioritization. The project pilot page can be found here: Product Council pilot page The MM SIG still needs to add their priorities. There was some discussion regarding whether we can include JIRAs with a status of “Draft”. Charlotte mentioned that is it is important that we include fully written up JIRA tickets (JIRAs with a status of “Open” rather than “Draft”). |
|
|
|
|
|
|
Product Council updates | Charlotte Whitt | 2025-04-24 Product Council Agenda and Meeting Notes Announcements: House keeping for the PC, and WOLFcon planning (sessions to be submitted) Eureka early adopters updates: GBV is up and running. TAMU is real close: The UI is build. The BE is almost build. The permissions, and password creation is semi-working, but not as it should. TAMU has set it up, and should be a repeatable process. Community priorities: DRAFT Community Priorities PC will review the status of the listed prioritized features has all the underlying jira stories written up. |
BELA (Bulk Edit and Lists App) | Jennifer Eustis | No meeting this week. |
Data Import Working Group | Jennifer Eustis | 2025-04-23 Data Import Subgroup Meeting Notes The group discussed:
|
Chat
00:03:59 Lynne Fors: I'll be there too!
00:04:15 Lynne Fors: We can set up a table
00:04:33 Jennifer Eustis: Reacted to "We can set up a tabl..."
00:04:45 Lynne Fors: Replying to "We can set up a tabl..."
I'm there all 3 days.
00:05:01 Vivian Gould (she/her): Replying to "We can set up a tabl..."
I'll be there all 3 days also.
00:05:50 Lynne Fors: Reacted to "I'll be there all 3 ..."
00:08:08 Laura Daniels: I will almost certainly be there in person
00:08:24 Christie Thomas (she/her): I will probably be there. We can submit and figure it out later.
00:08:34 Lynne Fors: Reacted to "I will probably be t..."•
00:08:36 Felix Hemme: Reacted to "I will probably be t..."
00:09:16 Katie Rahman: I will be there for sure.
00:11:04 Jennifer Eustis: Community Priorities Dashboard Development
00:14:21 Christie Thomas (she/her): Do you recall the rationale for that decision?
00:18:11 Raegan Wiechert: The overlay problem is supposed to be fixed in Ramsons
00:18:19 Jennifer Eustis: Reacted to "The overlay problem ..." with
00:18:30 Alissa Hafele: We are seeing both of these issues as well.
00:19:51 Katie Rahman: Reacted to "The overlay problem ..."
00:23:51 Laura Daniels: it flies under the radar causing challenges across FOLIO!
00:24:03 Christie Thomas (she/her): Reacted to "it flies under the r..."
00:24:58 Alissa Hafele: Reacted to "it flies under the r..."
00:25:04 Vivian Gould (she/her): Are Cross-App and App Interaction the same thing?
00:25:14 Laura Daniels: Replying to "Are Cross-App and Ap..."
Yes
00:25:18 Christie Thomas (she/her): If lack of a convener is the problem, I will volunteer to be the initial convener.
00:25:24 Vivian Gould (she/her): Reacted to "Yes"
00:25:28 Laura Daniels: Replying to "Are Cross-App and Ap..."
we started saying cross app because AI is confusing these days
00:25:34 Christie Thomas (she/her): I do think it is worth meeting with App Interaction to see if that makes sense.
00:25:37 Vivian Gould (she/her): Reacted to "we started saying cr..."
00:25:41 Laura Daniels: Reacted to "I do think it is wor..."
00:25:49 Lynne Fors: Reacted to "I do think it is wor..."
00:25:58 Lynne Fors: Reacted to "it flies under the r..."
00:26:22 Laura Daniels: Reacted to "If lack of a convene..."
00:26:27 Felix Hemme: Reacted to "If lack of a convene..."
00:26:41 Katie Rahman: Reacted to "If lack of a convene..."
00:27:44 Lynne Fors: Maybe there needs to be a reporting out like we currently do in the MM agenda
00:27:52 Jennifer Eustis: Reacted to "Maybe there needs to..."
00:27:54 Alissa Hafele: Reacted to "Maybe there needs to..."
00:28:12 Jennifer Eustis: Reacted to "I do think it is wor..."
00:28:22 Laura Daniels: Reacted to "Maybe there needs to..."
00:29:30 Jennifer Eustis: Similar to what we do with BELA with the updates
00:29:34 Christie Thomas (she/her): Reacted to "Similar to what we d..."¯
00:29:40 Lynne Fors: Reacted to "Similar to what we d..."
00:29:57 Christie Thomas (she/her): I have another meeting, so I need to log off. Thanks you for leading this discussion Jennifer.
00:30:04 Jennifer Eustis: Reacted to "I have another meeti..."
00:34:04 Laura Daniels: there are no good meeting times!!!
00:34:12 Vivian Gould (she/her): Reacted to "there are no good me..."
00:35:03 Laura Daniels: totally agree that having more people attend those meetings would be beneficial
00:36:15 Katie Rahman: I plan to start attending.
00:36:21 Vivian Gould (she/her): Replying to "totally agree that h..."
Will make the effort.
00:36:29 Laura Daniels: we need new complainers 🤓
00:36:50 Vivian Gould (she/her): Replying to "we need new complain..."
I'm very good at complaining.
00:36:53 Lynne Fors: We need to do something to address the systemic issues in Data Import
00:36:58 Laura Daniels: Reacted to "I'm very good at com..."
00:37:09 Laura Daniels: Replying to "we need new complain..."
that's a valuable skill
00:37:17 Laura Daniels: Reacted to "We need to do someth..."
00:37:23 Jennifer Eustis: Reacted to "We need to do someth..."
00:37:35 Katie Rahman: Reacted to "I'm very good at com..."
00:37:56 Lynne Fors: Replying to "We need to do someth..."
It's obvious what we have been doing is just not working for the community as a whole.
00:38:10 Laura Daniels: Reacted to "It's obvious what we..."
00:40:46 Katie Rahman: Exactly.
00:40:54 Laura Daniels: Reacted to "Exactly."
00:41:10 Laura Daniels: Hear, hear Vivian
00:41:21 Charlotte Whitt: Reacted to "Hear, hear Vivian"
00:42:01 Charlotte Whitt: Data Import probably should have been refactored - quite some time ago
00:42:12 Vivian Gould (she/her): Reacted to "Data Import probably..."
00:42:13 Whitney Christopher: Reacted to "Data Import probably..."
00:42:21 Alissa Hafele: Reacted to "Hear, hear Vivian"
00:42:22 Whitney Christopher: Reacted to "It's obvious what we..."
00:42:30 Charlotte Whitt: The UI might be the same. But the BE work probably could be re-written
00:42:34 Laura Daniels: Reacted to "Data Import probably..."
00:42:37 Lynne Fors: Reacted to "Data Import probably..."
00:43:45 Charlotte Whitt: + 100 Jennifer. Ryan is really working hard
00:43:57 Laura Daniels: Reacted to "+ 100 Jennifer. Ryan..."
00:44:22 Lynne Fors: The Dream!
00:44:29 Felix Hemme: There have been at least 2 great documents created that lists issues with DI. We have discussed them in the SIG. Do we know what has been worked on from that documents?
00:45:47 Jennifer Eustis: Replying to "There have been at l..."
I keep a record of what is released for each flower
00:45:58 Felix Hemme: Reacted to "I keep a record of w..."
00:48:15 Charlotte Whitt: Reacted to "I keep a record of w..."
00:48:35 Vivian Gould (she/her): I create documentation and training videos for our members. I am happy to share those with any and all.
00:48:37 Whitney Christopher: Replying to "There have been at l..."
Has there been or should there be an attempt to cross reference to help demonstrate how DI has kinda been left behind in development? Would that be useful?
00:48:54 Whitney Christopher: Reacted to "I create documentati..."
00:49:10 Jennifer Eustis: Replying to "There have been at l..."
I don't think anyone has done this.
00:49:25 Lynne Fors: Agenda again: 2025-04-24 Metadata Management Meeting notes
00:49:44 Laura Daniels: yes, much easier to read now
00:50:02 Whitney Christopher: Replying to "There have been at l..."
Maybe we can discuss this in Slack, if it's something we're interested in.
00:50:32 Laura Daniels: I would love for us to put something in this table as it will help PC come up with a better process for supporting us
00:51:15 Laura Daniels: ...and will help us think about how we want to approach prioritization in future
00:51:23 Jennifer Eustis: Reacted to "...and will help us ..."
00:52:03 Felix Hemme: This is the list of not scheduled MM work sorted by number of votes: https://folio-org.atlassian.net/jira/dashboards/10302?maximized=15172
00:52:12 Felix Hemme: It does include DI and other areas as well.
00:52:42 Lynne Fors: The topic tracker could be helpful. Metadata Management Implementers Topics
00:52:55 Felix Hemme: But we could pick the top 5 MM priorities from that list. Or come up with a broader scope that is not formalized in tickets, e.g. "stabalize DI" etc.
00:53:33 Laura Daniels: top 5 with status open?
00:53:34 Lynne Fors: I think that if we put in the
Multiple Graphical Representations (2 jiras) should count as one priority and not two.
00:53:45 Laura Daniels: Reacted to "I think that if we p..."
00:53:48 Felix Hemme: But it is not up to us (the SIG) to change a ticket from Draft to Open.
00:53:54 Felix Hemme: That is PO responsibility.
00:53:59 Felix Hemme: Reacted to "I think that if we p..."
00:54:44 Laura Daniels: Felix makes a good point -- we can write up the feature/stories ourselves but we can't change the status
00:55:35 Lynne Fors: Inventory Hierarchical Navigation Structure (UI/UX refactor) is a big one that we should probably put on as it will take a long time to get done (but we aren't able to vote for the ticket at all) UXPROD-491: Result list. Long term solution. Implement Refined UX-design for Inventory - hierarchical navigation structure (Instance, Holdings, Item)Draft
00:55:46 Jennifer Eustis: Reacted to "Inventory Hierarchic..."
00:55:52 Felix Hemme: Reacted to "Inventory Hierarchic..."
00:57:07 Laura Daniels: @Lynne Fors this is an example of why I think we need to think holistically about a process for prioritization that will work for us as a SIG