2023-06-01 Product Council Meeting notes
Background documents:
ARLEF Data Import Report, 2023-04-12
EBSCO's Report to the ARLEF Report, 2023-04-24
Report on Data Import, by Corrie Hutchison, 2023-05-05
EBSCO's Update on Data Import Troubleshooting, 2023-05-23
Data Import (notes written up by Felix Hemme )
Goal: Make DI a reliable and stable tool for libraries.
- Product management slide:
- P1+P2 defects will be backported to Nolana and Orchid. Folijet is working on them right now.
- Currently no Jira Dashboard to follow the development, but there should be one. Once it has been created, Khalilah will share the board.
- Processing of large jobs still in design phase. Idea:
- Split large jobs into smaller jobs
- Run each small job
- After a completed job run, check for the smallest job in the queue and run this one next
- What is the definition of a large job/load? Testing is done with record sets of 50k and 100k. 100k seems realistic, but 5,000 is not large by MM definition.
- Tod Olson: So "large" is a function of both record set size and complexity of import profile?
- Need a way to schedule large loads for off hours
- Question around how non-EBSCO hosted libraries are supported
- How are bugs prioritized? This should be transparent and Khalilah mentions this page: /wiki/spaces/DQA/pages/2657909
- Chicago mentions that they can't wait for this work, as they are live for 1.5 years and need a working system. How is the process let people know when to expect what type of functionality?
- Complete work that's listed on the previous slide
- Miro board: (https://miro.com/app/board/uXjVMJdEzKg=/?share_link_id=33208799709)
- Question about accountability; our group has been pointing out issues for years
- Omit Poppy release in Spring 2023 and move it to Nov. 2023 in order to have time to work on DI. Not decided yet.
- Owen: This is a big decision to make so late in the release cycle and after the (extended) feature freeze for Poppy.
- Who will make the final call and when? There shall be a vote in PC
MM SIG discussion of PC Data Import meeting
- Recurring themes - concern about transparency, e.g. no Jira board; lack of trust in app; concern about short term vs. long term plan (see miro board) - we need some of these things now.
- Per Charlotte: The PC agenda has links to several documents, which were rework from ARLEF, and Corrie Hutchinson has gathered feed back from implementing libraries, and matched this with status on jiras.
- Suggestion to delay Poppy release came as surprise and would be very late decision. Unique scenario, but still concerns around it. Another option is the critical service patch path.
- Reminder: Data Import is used outside of app for e.g. single record import/overlay etc. Need to keep reminding because critical for daily operations, not just bulk data loading.