https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42532 --- Comment #7 from David Cook <dcook@prosentient.com.au> --- (In reply to Caroline Cyr La Rose from comment #6)
(In reply to David Cook from comment #5)
What's your target use case for it?
We want to dedup titles on isbn, issn and 024$a without going through the index. We figured the easiest way would be to have all three values in the db rather than having to extractvalue the crap out of biblio_metadata.
Ah right. Yeah, I can understand that. And using biblioitems.ean beats adding a new column like biblioitems.standard_identifier. I'd have to double-check how biblioitems.ean gets used, but I wonder if biblioitems.ean needs a rebrand... interesting. I reckon... let's check to see where biblioitems.ean gets used. Maybe a rename is in order... I do have a customisation that adds "Identifier-standard: 024$a" to the duplicate check when saving records, so your use case does make sense. Just want to make sure we're not abusing the "ean" field... -- You are receiving this mail because: You are watching all bug changes.