Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODQM-127 |
---|
|
- Natascha will talk us through this bug and we can discuss possible workarounds as long as an institution is live on a release prior to Kiwi
- bug is fixed for Kiwi
- Chicago is looking for what they can do until they have Kiwi
- Natascha demos the issue in Folio Inventory
- when editing the SRS record and entering an invalid field, the inventory instance is not updated
- sometimes this may even be just a typo
- corrupt SRS records can be updated after correcting the error outside the systems
- question: Can this bug fix be back ported to Juniper
- answer: no, it cannot be backported
- the SRS record does not seem to validate
- workaround: after editing SRS record, wait a few minutes and try to edit again
- Adam Cottle: experienced a similar issue with data import
- Jenn in chat: One thing that can help reset things with DI is to make sure you remove the 999 when you are trying to reset a record
- A-M: it is important that when updating (not creating a record) that users do not accidentally use a create profile, but an update profile
- Jenn will add a paragraph to the Tipps and Tricks section
- Adam in chat: For reference: for
SQL [null]; ERROR: insert or update on table "raw_records_lb" violates foreign key constraint "fk_raw_records_records" Detail: Key (id)=(92a43de3-277b-41f9-b10f-6c3302e917d3) is not present in table "records_lb". - Felix: is there a way to find the corrupt records?
- Christie: could have a query that identifies where your current SRS is out of sync with your Inventory record → this may not be very effocient
- another not validated idea: search current or active SRS records that do not have a "999" tag → would indicate that the SRS record was corrupt
- A-M in chat: Charlotte - re: your question about identical 999s - I don't think that will be an issue, but I'll add it as a question in the draft Jira I mentioned
- A-M in chat: Here's the Jira that addresses the error that Adam/Skidmore described:
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODSOURMAN-660 |
---|
|
- Jenn in chat: We have talked about trying to make a report that would shows relationships between instances and SRS records that don’t look right (ie two actual SRS records
- ID has done soem analysis of the issue; it is not possible to backport the bugfix
- Jacquie in chat: Can we expect that this bug will definitely be addressed in Morning Glory?
- Felix in chat: @Jackie the quickMARC bug is fixed with Kiwi
- Laura in chat: there are issues with any system/tool: at least with FOLIO our reports of problems are taken seriously!
- Jenn in chat: They are in different fields in LDP so it should still work ok to compare
- a relationship report might help
- A-M in chat: I'll start a draft Jira for a script that would identify relationship problems between SRS and corresponding Inventory records. Then maybe we can fill in details at an upcoming DI subgroup meeting
Chat:
Von Christie Thomas (she/her) an alle 05:51 PM
The Inventory instance is not updated.
Von Laura Daniels an alle 05:51 PM
does it not get updated at all? or is it just slow right now? (we usually have to refresh to see updates)
Von Khalilah Gambrell an alle 05:51 PM
Due to the error the change never flows to Inventory instance record.
Von Charlotte Whitt an alle 05:52 PM
Then there should not be a green success toast
Von Jenn Colt an alle 05:52 PM
Oh no!
Von Ann-Marie Breaux an alle 05:52 PM
I think that's why there was a bugfix, Charlotte
Von Laura Daniels an alle 05:53 PM
big ouch
Von Charlotte Whitt an alle 05:53 PM
Can this bug fix be back ported to Juniper
I do affect all libraries
It … :-)
Von Jenn Colt an alle 05:59 PM
One thing that can help reset things with DI is to make sure you remove the 999 when you are trying to reset a record
Von Jennifer Eustis (she/her) an alle 05:59 PM
We talked about the marc modification issues in Data Import lab last week. Christie - did you create that jira?
Von Adam Cottle an alle 06:02 PM
For
SQL [null]; ERROR: insert or update on table "raw_records_lb" violates foreign key constraint "fk_raw_records_records" Detail: Key (id)=(92a43de3-277b-41f9-b10f-6c3302e917d3) is not present in table "records_lb".
Von Ann-Marie Breaux an alle 06:05 PM
Here's the Jira that addresses the error that Adam/Skidmore described:
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODSOURMAN-660 |
---|
|
Von Jenn Colt an alle 06:06 PM
We have talked about trying to make a report that would shows relationships between instances and SRS records that don’t look right (ie two actual SRS records
Von Christie Thomas (she/her) an alle 06:07 PM
that is a good idea, Jenn.
Von Jacquie Samples an alle 06:09 PM
Can we expect that this bug will
Von Felix Hemme (ZBW) an alle 06:09 PM
@Jackie the quickMARC bug is fixed with Kiwi
Sorry -- Jacquie
Von Charlotte Whitt an alle 06:09 PM
Will the identical 999 ff $i and $s make it impossible to do that comparison across Inventory, instances and SRS?
Von Ann-Marie Breaux an alle 06:24 PM
Charlotte - re: your question about identical 999s - I don't think that will be an issue, but I'll add it as a question in the draft Jira I mentioned
Von Laura Daniels an alle 06:10 PM
there are issues with any system/tool: at least with FOLIO our reports of problems are taken seriously!
Von Jenn Colt an alle 06:11 PM
They are in different fields in LDP so it should still work ok to compare
Von Jennifer Eustis (she/her) an alle 06:11 PM
It would be great to have alternatives ways to do this beyond the LDP as not everyone has access to that tool
Von Jenn Colt an alle 06:11 PM
Started the list for recovering from errors here if others have things to add: Miscellaneous Tips for Data Import
Von Ann-Marie Breaux an alle 06:13 PM
Jenn - that relationship report sounds like a great idea. Slowly but surely, we are building up scripts to check for these types of problems, or bits of cleanup - that can be run on an ad hoc basis.
Von Ann-Marie Breaux an alle 06:14 PM
I'll start a draft Jira for a script that would identify relationship problems between SRS and corresponding Inventory records. Then maybe we can fill in details at an upcoming DI subgroup meeting