[Bug 42413] New: Invalid metadata is causing a 500 error when editing
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42413 Bug ID: 42413 Summary: Invalid metadata is causing a 500 error when editing Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: enica@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: m.de.rooy@rijksmuseum.nl If you get an invalid metadata/character error in the staff client, you used to be able to fix the error by editing and saving the record. Now, it's throwing a 500 error. The only way to fix it is in the backend. It would be nice if Koha could automatically remove invalid metadata/characters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42413 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |major CC| |cbrannon@cdalibrary.org --- Comment #1 from Christopher Brannon <cbrannon@cdalibrary.org> --- It would be SO GREAT if Koha would get this right. It should not be letting staff save records that can break indexing. This is a HUGE problem right now for us. As much as I want catalogers to look over information carefully, they are human, and we need Koha to address its limitations on the fly rather than us dealing with the aftermath. I think this is a major bug, not minor. It stops Koha indexing from functioning properly, and it creates some chaos in statuses. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42413 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE CC| |dcook@prosentient.com.au Status|NEW |RESOLVED --- Comment #2 from David Cook <dcook@prosentient.com.au> --- (In reply to Christopher Brannon from comment #1)
It would be SO GREAT if Koha would get this right. It should not be letting staff save records that can break indexing. This is a HUGE problem right now for us. As much as I want catalogers to look over information carefully, they are human, and we need Koha to address its limitations on the fly rather than us dealing with the aftermath.
Honestly, a comment on Bugzilla probably won't reach many people. I'd suggest mentioning it on Mattermost. Also, it's often not enough to look over information carefully. If they copy and paste something from a PDF or Word, it can include invalid invisible characters that no amount of visual inspection is going to catch. In fact, that is the most common problem I've noticed in my libraries in the past.
I think this is a major bug, not minor. It stops Koha indexing from functioning properly, and it creates some chaos in statuses.
This is arguably a duplicate of bug 35104 which is marked as major. My libraries are all doing pretty well these days, but yeah it would be good to get this fixed. Bug 35104 needs QA, although a lot of things need QA. The more people complain to vendors the more likely they are to allocate resources I think. (If my clients were complaining about it, it would definitely make it go up my priority list.) Unfortunately, a lot of people had different opinions/needs/wants for how to fix this situation, and it's really made things drag on much longer than they needed to. *** This bug has been marked as a duplicate of bug 35104 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org