2023-12-13 Data Import Subgroup meeting
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:
Links:
- Poppy import planning dashboard
- Poppy timeline
- Quesnelia import planning dashboard (still being defined)
- Quesnelia timeline
- Folijet Current Development Board
- Folijet (Data import) Bug Dashboard
Agenda:
- Circle back on UXPROD-2742: MARC-MARC matching enhancements: Narrowing multiple matches & Bug work
- Can anyone provide use cases with example files & jobs for multiple match scenarios?
- What are the most common number fields expected to be used in MARC-MARC matching?
- UIDATIMP-1521: Not able to use system generated Match profiles
- Discuss: Does it make sense to the group to make Single Record Import Default profiles accessible to Duplicate & use with Job profiles, but NOT allow access to Edit or Delete?
- MODSOURMAN-1094: The number of created invoices is displayed when all invoices have errors with invoice lines
- Discuss: Is it still preferred for the top of an invoice job log to show total number of Invoices or should it instead display the total number of Invoice Lines?
- Circle back on UXPROD-2742: MARC-MARC matching enhancements: Narrowing multiple matches & Bug work
Upcoming meetings/agenda topics:
Chat
Ann-Marie to Everyone 1:07 PM
Sorry to be late!
Lynne Fors to Everyone 1:09 PM
MARC-MARC match on OCLC number then submatch on Statistical code
Christie Thomas (she/her) to Everyone 1:10 PM
marc to marc match on 035, submatch on holdings type or holdings URL and then update srs + update holdings
Christie Thomas (she/her) to Everyone 1:12 PM
marc fields are any 0xx field, 001, or 9xx field, 856$u for common fields used in the marc record.
Jennifer Eustis to Everyone 1:14 PM
MODINV-882
wiljanen to Everyone 1:14 PM
matching ISBN if there is no $q but has a :$c and the ISBN interprets the colon as being part of the ISBN and therefore considers the ISBN as being invalid
Jennifer Eustis to Everyone 1:23 PM
There could be a match to 035 \\$z for cancelled OCLC no
Jennifer Eustis to Everyone 1:33 PM
Thanks Ann-Marie
Ann-Marie to Everyone 1:37 PM
Exactly Raegan - this is something that we should have revisited this decision when we added fxn of using additional ISRI profiles
scolglaz to Everyone 1:38 PM
That makes sense to me!
Autumn Faulkner (she/her) to Everyone 1:38 PM
yep!
Autumn Faulkner (she/her) to Everyone 1:39 PM
I have been able to duplicate the action and use it for other profiles
scolglaz to Everyone 1:39 PM
I just wish all the System Field mapping profiles were named the same
Autumn Faulkner (she/her) to Everyone 1:40 PM
you have to duplicate the action
the default one won't appear
but the duplicate will
it would be handy to not have to do the duplicate dance lol
Lynne Fors to Everyone 1:41 PM
Did the issue of having to have multiple copies of action profiles if you are reusing the same actions get fixed? It's really frustrating to have so much bloat in our profiles. We should be able to reuse the action profile multiple times within a job
Ann-Marie to Everyone 1:42 PM
Lynne - that has changed - you can use the same action/match in the same job profile now. I believe in Orchid, there are a few restrictions you will run into, but in Poppy, all should be clean. That's something we definitely worked on
Lynne Fors to Everyone 1:42 PM
I'm still using the old multiples that were the workaround in MG/Nolana.
Lynne Fors 1:44 PM
in my Orchid environment. I'll wait for our Poppy test environment/upgrade to see if I can get rid of all those duplicates
Jennifer Eustis to Everyone 1:43 PM
+1
scolglaz to Everyone 1:45 PM
But aren't there 3 invoices?
Ah, I could only see 3 different #s
Lynne Fors to Everyone 1:47 PM
Add a column for Invoice lines In the summary between Invoice and Error?
scolglaz to Everyone 1:47 PM
+1
Christie Thomas (she/her) to Everyone 1:49 PM
Off topic for invoices, but I tested the srs match with an instance update and an srs update and that results in no errors, but no action taken in Poppy. https://bugfest-poppy.int.aws.folio.org/data-import/job-summary/ef429675-546c-4ae7-9e84-b71956118f37 Should I open a new Jira about this or add it to the marc to marc matching Jira?
Jennifer Eustis to Everyone 1:52 PM
+1 to Sara about seeing invoices
scolglaz to Everyone 1:52 PM
+1 Invoice Lines have should get their own column!
Ann-Marie to Everyone 1:53 PM
Christie - I think add a new Jira bug (and we'll link to the MARC-MARC matching feature). For your MARC update action, were you trying to override field protections? If so, that would be in line with the WOLFcon discussion where field protections work with MARC-Instance matches, but field protection overrides (which are MARC Updates) do NOT work with MARC-Instance matches.
Christie Thomas (she/her) to Everyone 1:54 PM
The srs update profile did include a field protection, which is really the only reason we use marc updates here since the field updates are not working.
Ann-Marie to Everyone 1:55 PM
And Christie - if you can add in your Jira a link to your job profile and the import log from Poppy Bugfest, that would be great
Christie Thomas (she/her) to Everyone 1:55 PM
I will do that.
Jennifer Eustis to Everyone 2:00 PM
Happy retirement !!
Christie Thomas (she/her) to Everyone 2:00 PM
Happy holidays and you deserve a break!
wiljanen to You 2:00 PM
Thank you so much for everything. Good luck much fun and safe travels!
Raegan Wiechert to Everyone 2:00 PM
🥳
scolglaz to Everyone 2:01 PM
Yes, have many adventures in retirement!
Lynne Fors to Everyone 2:01 PM
Happy Hannukah! Merry Christmas! Happy Holidays!
Yael to Everyone 2:01 PM
Thanks for everything Anne Marie and Happy holidays everyone
Robert Pleshar to Everyone 2:02 PM
Happy retirement Ann-Marie!