http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10421
--- Comment #12 from David Cook <dc...@prosentient.com.au> --- Mohammad Nashbat's comment on the listserv is also interesting: "I’m trying to upload a deletion batch from ebrary to our Koha LMS, this batch changes the records status in the leader tag to “d” delete, which used to delete the bib records using our old library system “Dynix” after indexing. But now in Koha it do change the status but without deleting the bib records even after indexing, am I missing something?" I think at a bare minimum records with a "d" need to be suppressed in the OPAC. However, actual deletions...I'm not sure what I think of this "batch deletion" idea. I haven't done a lot yet with MARC dumps from vendors like EBSCO, but I could see how re-uploading records with a "d" in the leader to do a batch delete might be an idea. While it's only tangentially related to this discussion, I wonder what sorts of best practices people have for maintaining MARC records in Koha that come from electronic service providers (for services like electronic journals and e-books). We have a homecooked solution here that my boss takes care of but I wonder what the optimal way of doing it would be. I'm sure people in a union catalogue situation/those who use OCLC or other interconnected cataloguing tools must also encounter situations where the original record has changed and now they either need to update or delete their existing records. (I know this is a problem I've also encountered in developing the OAI-PMH harvester. It seems like it could be a pervasive issue.) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://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/
