2025-11-12 Data Import SIG Meeting Notes
Recordings are posted Here (2022+) and Here (pre-2022) Slack channel for Q&A, discussion between meetings
Requirements details Here Additional discussion topics in Subgroup parking lot
Attendees: @Jennifer Eustis @Robert Pleshar @Christie Thomas @Katie Rahman @Yael Hod @Sara Colglazier @Kim Wiljanen
Notetaker: @Whitney Christopher , @Autumn Faulkner , @Yael Hod , @Robert Pleshar
Links:
Agenda:
| Item | Notes |
Announcements |
|
|
|
| CT: Will be working on a draft survey for assessing broad requirements for Edifact data imports. JE will assist. |
|
|
|
Discussion (New Topic or Jira Issue) |
|
|
New Topic | Continuing the discussion of our process for requesting new topics: In field mapping profile allow option to add if not a duplicate. (review new topic with a discussion on our process for requesting a new topic) Ideas: Create summary for community to review new topic how to handle creation of Jira ticket do we create a decision log or do we create a Jira story (see examples) | JE: How to handle new requests - Put elements from decision log into Jira story. Found it difficult to create story - not sure what project to put it in. KR: Likes idea of decision log first. CT: partial to managing in wiki at least during feedback process RP: Do we know what works best for Ryan or developers? JE: Not sure if creating Jira is jumping the gun. Maybe create it in wiki and review with Ryan in housekeeping section of meeting. CT: Agree, make sure we build consensus before creating a story. Wiki creation is more forgiving than creating a Jira story. JE: Embedded hierarchy in left panel of wiki is easy to navigate. RP: Less work to do it in wiki and not creating potential duplicate / overlaps. JE: Can add more information to wiki as well. Decision: create decision log, review any new / unreviewed requests as part of housekeeping section of meeting. |
| Check the Status of an Existing Issue | JE: Can check dashboard, post to lab slack channel with practical problems, data-import sig slack channel for theoretical issues. CT: We could provide more detail / guidance for this page. How do we know we have checked where we should have checked? What is roadmap to confident searching? Should we find and flag existing Data Import issues to help make this easier? JE: If someone else creates a ticket which relates to Data Import we want to add our tags to those as well. KR: Access has a subgroup to look at old Jiras and clean them up, possible idea for DI. JE: Maybe we can have a subgroup work on how to find an existing issue and how to categorize them? JE: Work on this as a group - get some examples of things to look for. |
|
|
|
Housekeeping |
|
|
|
| CT: Do we want to return to Edifact next week or wait for survey results? |
| Get Link to Jira from Discussion on 2025-10-15 | Log UI Enhancements:
|
| Actions/Decisions Needed | To do Add add if not duplicate |
Roadmap Discussion (At same time of a new release) |
|
|
MVP Discussion (at the same time of a new release) |
|
|