https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34788 --- Comment #49 from Matt Blenkinsop <matt.blenkinsop@ptfs-europe.com> --- Thanks for looking at this!
Blockers: When uploading the file you get the blue box about the import - you cannot dismiss this, it might be better as a modal? Even if I click back to 'Titles' the blue box remains - I have to go to packages and back to titles
Fixed
I forced a smaller packet size for testing: - my $max_allowed_packet = C4::Context->dbh->selectrow_array(q{SELECT @@max_allowed_packet}); + my $max_allowed_packet = 10384; This did create a bunch of smaller jobs, however, I found that biblios were not created even if I checked the box once the job was chunked.
Fixed
QA tool complaints
Fixed
Other notes: When editing a title, I can add it to two packages, however, if I try to import a duplicate into another package it is simply ignored. I don't know if this is a blocker or not.
This is a good catch, I've fixed this so you can now have the same title in multiple packages
When adding biblios for the titles, there is an ES update for each title added. It would be nice to batch these
I've added skip_record_index in here now and am indexing at the end of the job
It would be nice see the package that was selected, and to have a way to get from the job results back to the package that the titles were imported into.
There's now a link on the report page
If you import a list and forget to check 'Create biblios' there is no way to update the files - it would be nice to be able to reimport the duplicates and update - I assume this is future enhancement. These patches do what they set out to - but they imply the need for more batch tools in this area to edit and update the titles
I agree, I think there should be some follow-ups to this for batch editing
The routines for fixing Ebsco files, or fixing 'coverage_notes' smell a bit, but make sense for practical purposes - is there any sense Ebsco would fix their issue?
We've not approached them about it, probably worth asking the question so we can get rid of that method at some point -- You are receiving this mail because: You are watching all bug changes.