https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41780
--- Comment #21 from Ayoub Glizi-Vicioso <[email protected]> --- (In reply to Katrin Fischer from comment #15) > I am wondering if we actually "want" to fix this. The preferred_name being > NULL in the database is a data issue and should not occur. If it does occur, > we probably will want to find the source of the issue and fix that. I understand that this is primarily a data issue and that resolving it at the source would be the preferred approach. However, in practice, Koha is often integrated with external scripts maintained by a third party, which may bypass its internal logic responsible for properly populating preferred_name, resulting in NULL or empty values. Correcting these third-party scripts can be complicated, making immediate source fixes challenging. While fixing the source is important, the staff interface must also remain robust. Failing to display a patron’s name due to incomplete data negatively impacts the staff experience. As an intern, I wanted to propose a safe and practical solution: implementing a simple fallback to firstname in the template to make the UI more resilient. I have also added optional database-level safeguards that enforce the same logic as Koha, ensuring consistent data even when external processes bypass Koha’s internal mechanisms. These safeguards can be installed or removed at any time if external scripts are later updated to follow Koha’s conventions. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
