MVP Discussion (at the same time of a new release)
upon can stagnate. She emphasized the need to tie these discussions
into the broader conversation about MVPs.
oVG also raised concerns about tracking topics that are discussed
but don’t result in JIRA issues.
oVG suggested adding links and brief synopses to the Data Import
SIG documentation to indicate discussion outcomes, as well as to
indicate whether the topics were being reviewed.
never prioritized or documented properly. She gave examples like the
inability to update instance holdings and items in reverse order, which
causes workflow issues.
slotted into the “big picture” of MVP planning, so they don’t get lost.
oCT proposed that the group should not have to dig through old
topic lists to remember what was requested but not
implemented.
in scope for the MVP and how to promote such features into JIRA.
1.The group decides the issue is already supported in FOLIO.
2.The group agrees it requires an enhancement and should be
added to JIRA.
discussions, which could be refined later.
existing JIRA stories could be expanded into full features if needed.
JE walked through the process of logging new ideas not found in JIRA
using the implementer spreadsheet.
JK recommended including the contributor’s institution in the
spreadsheet in case follow-up was necessary.
Documentation and Establishing Processes
CT emphasized the importance of formalizing the Data Import SIG’s
processes and creating documentation that reflects current practices.
CT renamed the bug reporting page from "Data Import Filing a bug" to
"Data Import Reporting a bug" based on a suggestion, and also to
better reflect the group's goals.
CT encouraged feedback on the new wiki pages via Data Import SIG
meetings or Slack.
JE added that comments can be made directly on wiki pages by
logged-in users.
Collaborating and Meeting with Acquisition SIG
YH asked about a follow-up meeting with the Acquisition SIG.
CT proposed scheduling the meeting for November 5 to allow time for
preparation and focus on bugs related to FOLIO acquisitions and data
import.
JE suggested prioritizing order-related issues and giving Acquisition SIG
members at least two weeks’ notice.
Process for Reporting Topics
JE walked through the process of logging new ideas not found in JIRA
using the implementer spreadsheet.
VG raised concerns about tracking topics that are discussed but don’t
result in JIRA issues.
VG suggested adding links and brief synopses to the Data Import SIG
documentation to indicate discussion outcomes, as well as to indicate
whether the topics were being reviewed.
JK recommended including the contributor’s institution in the
spreadsheet in case follow-up was necessary.
Handling Unresolved Topics in the Data Import SIG Topic Tracker
CT discussed the challenge of tracking unresolved but important
topics, using the example of updating instance holdings and items in
reverse order.
CT emphasized the need for a better system to manage feature
backlogs and ensure that topics don’t go unresolved.
VG and JE agreed that discussed items should be documented clearly,
even if they don’t lead to JIRA issues.
Need for Volunteers - Topic Tracker Decisions, Documentation, and
Spreadsheet Updates
KR, VG, and AF volunteered to help with documentation and
spreadsheet updates (ML did as well, but forgot to say so out loud).
They supported the idea of shared responsibilities, suggested creating
guidelines for volunteers, and having working meetings to go through
the Data Import Topic Tracker.
It was suggested that there may be a need for an additional Data
Import SIG recurring meeting to go through the Data Import Topic
Tracker.
oSome participants agreed on having additional meetings, but
indicated that their schedules may not permit them to attend all
meetings.
Data Import SIG Process Documentation
CT and JE acknowledged that the process for turning topics into JIRA
issues is still being developed.
CT proposed using meeting time for collaborative documentation and
process mapping. She also emphasized the need to establish and
clarify responsibilities.
RT outlined options for creating JIRA features, including drafting
skeleton tickets and refining them over time.
Upcoming meetings/agenda topics
The group agreed to use future meetings for both topic discussion and
process refinement.
JE will add a new section called "Housekeeping" will be added to the
agenda to track unfinished discussions, decisions, and agenda items
that the group did not have time to address during previous meetings.
The topic, and agenda item for this week’s meeting - "Infield mapping
profile: allow option to add if not a duplicate" - will be discussed next
week as a real-world example to test the process.
CT agreed to post in relevant Slack channels about the November 5
meeting.
JE to add a "Housekeeping" section to the agenda.
Need for volunteers to help define and document the process for
converting Data Import topics into JIRA issues.
Use next meeting to discuss the infield mapping profile topic and refine
the documentation process.
Housekeeping Items
Next Topic: “Infield mapping profile: allow option to add if not a duplicate.”
Meta-Discussion: Use the topic to explore and document the process of
moving ideas into JIRA.
Housekeeping Section: Will be added to the agenda to track unfinished
discussions and decisions.
Action Items
CT to post in relevant Slack channels about the Nov 5 meeting.
JE to add a “Housekeeping” section to the agenda.
Seek volunteers to help define and document the process for converting
topics into JIRA issues.
Use next meeting to include both topic discussion and process refinement
|