Skip to end of banner
Go to start of banner

2024-1-24 Data Import Subgroup meeting

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

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: Ryan Taylor Jennifer Eustis Ellis Butler Robert Pleshar Corrie Hutchinson (Unlicensed) Taylor Smith Lynne Fors Aaron Neslin Yael Hod Christie Thomas Aaron Neslin 

Notetaker: Jennifer Eustis, Corrie Hutchinson, Christie Thomas

Links:

Agenda: 

TopicWhoMeeting NotesRelated JiraDecisions and Actions

Documentation: The group has identified a need for new, enhanced, or reorganized documentation around Data Import.

  • In a previous session, we agreed that completing a functionality audit spreadsheet would be a good first step
All

In lab session on 1/18/2024, we created a wiki page, Data Import Topic Tracker, with guidelines on how to contribute and a spreadsheet to track issues. This is based on the work done in the Acquisitions SIG. An archive area was also created where we could archive outdated pages such as the Data Import Implementers and Feature Discussion Topics.

The idea was to put down issues whether they were linked to a Jira issue or not. Some of the important information that we wanted to track was if there was a linked Jira and in particular when the issue was discussed in the working group and the decision(s) made in regard to that issue.

The spreadsheet is still being developed. Before we add more issues, the group in lab wanted to know:

  • Do we adopt this page and spreadsheet? If yes, do we have volunteers to populate it?
  • To make sure this page is maintained, the group suggested that the working group look at it once a month to see what is outstanding or new. Is this a practice we want to adopt?
n/a
  • Get volunteers to create a spreadsheet and start brainstorming - DONE
De-duplication: Continue conversation from previous session to clarify what we expect from de-duplication of field values when a record is loaded into FOLIO via Data Import.All
MODDATAIMP-879: Data Import removes duplicate 856s in SRS
  • Clarify current behavior of field value de-duplication.
  • Define desired behavior of field value de-duplication (if different).
  • Christie Thomas will create some dummy data to illustrate deduping 856s.





Upcoming meetings/agenda topics:


Chat:

  • No labels