2025-08-06 Data Import SIG Meeting Notes

Announcements

ALL

Upcoming session with MARC orders demos from Stanford and Michigan State University. (2025-08-20)

Proposed process for managing SIG discussion topics and Jira tracking.

@Christie Thomas

New topic tracker page (in progress): Data Import Requesting a New TopicPreview

CT: Name has been changed to Archived Data Import Topics

CT:What are our operating procedures going forward so that anyone can add a topic and help manage this? Use New Topic Tracker - link to meeting notes, record decisions/next steps, link to JIRAs, comments from discussion will be added. Add label “Data Import SIG needs review” to Jira and it will appear on that dashboard.

YH: Documentation and needs review concept are good ideas. Do not remove from list unless it is resolved.
CT: Do we need to differentiate between topics discussed w/o movement and topics not yet discussed.
RT: We should ensure that when an item is reviewed we should always a comment to the ticket so we know where we were when we pick it back up.
JK: Label as discussed/undiscussed?

Don’t remove “needs reviewed” label until we reach consensus.

Everything should be “reviewed” or “not reviewed”

Cancelled jobs in settings

@Yael Hod

YH: Stopped jobs not appearing in “Jobs using this profile” list when looking in Settings. The job is in the log, but does not appear in the list in settings. Not sure if this is a setting issue or something else.
RT: Making sure it is jobs stopped by user.
JK: This list only shows completed jobs.

CT: Same in our environment (Quesnelia).
RT: Doesn’t recall any changes in later versions which targeted this list, but will double check.
CT/YH: We need to understand why it is like this so we can say what we want to happen.

RT: Agrees with Jira approach, would bring to team and find out if intentional / bug / just not thought of. Then determine where to go from there.
JK: Should there be one central ticket or should each thing be its own ticket? Also, can’t ctrl-left click in logs, but can elsewhere. Is that a separate ticket? Or is it too small?
CT: We should develop norms and processes so we don’t have to ask these questions everytime. If we don’t document the small stuff, it will never get attention. Add small things to the topic tracker and we can decide as a SIG how to approach it. We can prioritize.
VG: How does the process differ for hosted vs self-hosted users? We need to take both into account.

CT: Customer support is different for different hosts. We will need to think about this and return to it.
CT: How do we ensure that if someone finds that something is or isn’t a bug, how do we inform the community?
CT: Maybe topic of SIG Jira filing and other standards/procedures needs to go to Product Council?
RT: Agrees that getting some alignment on this would be good.

AF: Recently elected to Product Council and can bring this to them if desired. This sort of harmonization might bring more input from the community.

JK: Who creates the Jira ticket after the topic tracker of the sig decides it should be one?

CT: Can we create a Jira using the Stanford example and get consensus about it?
RT: Can walk us through what he would do. Best practice is to give steps to duplicate, a brief description of what you are seeing and what you expect to see. Can be very simple.

CT: What are the important values to include? Walk through would be a great activity.

RT: Template:
Something like this:

Overview:
Steps to Reproduce:

1. Log into some FOLIO environment as User X

2. Click this

Expected Results:
Actual Results:
Additional Information:
URL:
Interested parties:
RT gave a short demo.

RT will check to see if there are changes in later versions.

We need to decide if this is expected behavior or if it is a bug? We need to file a JIRA, but what are the useful parameters for it? Is it a bug or a story?

Walk through building a Jira next session (RT)

Review list of issues that need review for next topics

@Christie Thomas