https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42532
--- Comment #8 from Caroline Cyr La Rose <[email protected]> --- As far as I could tell, the column was added for UNIMARC where the EAN is a separate field (073 https://unimarc.org.ua/ifla/biblio2023/2023n1_0_0_UNIMARC_073_International_Article_Number_73-75.pdf) I did a git grep with biblioitems.ean and these are the only places where it's used C4/Acquisition.pm: biblioitems.ean, C4/Acquisition.pm: $query .= ' AND biblioitems.ean = ?'; C4/Acquisition.pm: COALESCE(biblioitems.ean, deletedbiblioitems.ean) AS ean, C4/Acquisition.pm: $query .= " AND biblioitems.ean = ? "; C4/Acquisition.pm: " (biblioitems.isbn LIKE CONCAT('%', ?, '%') OR biblioitems.ean LIKE CONCAT('%', ?, '%') OR biblioitems.issn LIKE CONCAT('%', ?, '%') ) "; C4/Serials.pm: push @where_strs, "biblioitems.ean LIKE ?"; Koha/EDI.pm: $bib_hash->{'biblioitems.ean'} = $itemid; acqui/addorder.pl: "biblioitems.ean" => $input->param('ean') || '', installer/data/mysql/en/marcflavour/unimarc/mandatory/unimarc_framework_DEFAULT.yml: kohafield: biblioitems.ean installer/data/mysql/updatedatabase.pl: "UPDATE marc_subfield_structure SET kohafield='biblioitems.ean' WHERE tagfield='073' and tagsubfield='a'"); misc/release_notes/release_notes_17_11_00.html:<li><a href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13766";>[13766]</a> Make biblioitems.ean longer and add index</li> misc/release_notes/release_notes_17_11_00.md:- [[13766]](http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13766) Make biblioitems.ean longer and add index The field seems to be used in the acquisitions module (I don't know how), but in MARC21 systems, it will always be empty since it's not mapped to anything. I *think* the use in Acquisitions is for display and searching orders (again, I don't know for sure, I don't read perl). So for MARC21 orders of DVDs for example, we could display and search for the CUP number if it were stored in biblioitems.ean. I would refrain from doing a complete overhaul of biblioitems just for this. I think this is self contained and doesn't need any other change. There are already plans to merge biblio and biblioitems that have been doing the rounds for years and years and asking for an overhaul of biblioitems to me is just another way of putting any change in limbo forever. -- 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/
