Need advice regarding removal of deleted biblio records
Dear all, I'm hoping someone can give me a bit of direction. We have a large number of deleted biblio records (due to a failed MARC records import). We'd like to remove the deleted records from the database as there are somewhat more deleted records (401,000) than active records. Is there a script than can clean up deleted records? I've seen this "Clean up database" script < https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-data...
, but it's not what we're looking for.
If there's no script, can we safely use the MySQL TRUNCATE command on the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and deleteditems tables? This is a non-circulating library, so I don't think the biblionumber would be tied to any other tables. I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60. -- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708
Hi If you do a Marc import through the koha importing tool, you can remove the records through the same process. You just need to check which import process you want to remove and that's it. Regards, Alvaro |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com Le mar. 25 juin 2019 à 15:44, Andy Boze <boze.1@nd.edu> a écrit :
Dear all,
I'm hoping someone can give me a bit of direction. We have a large number of deleted biblio records (due to a failed MARC records import). We'd like to remove the deleted records from the database as there are somewhat more deleted records (401,000) than active records.
Is there a script than can clean up deleted records? I've seen this "Clean up database" script <
https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-data...
, but it's not what we're looking for.
If there's no script, can we safely use the MySQL TRUNCATE command on the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and deleteditems tables? This is a non-circulating library, so I don't think the biblionumber would be tied to any other tables.
I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.
-- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708 _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Actually we did use the import tool. The server (it's running on AWS) choked and we had to restart it. We bumped up its capacity and restarted, and Koha looked like it continued to process the import where it left off. Unfortunately we ended up with lots of duplicate records (with different biblio numbers). We tried reverting the import, but that still left a lot of records to delete. We deleted the records and tried importing from the previously staged records. Doing that, nearly all the records were duplicated. We reverted those imports and deleted duplicate records. Then we uploaded the records again to stage them, rather than reusing the previously staged records. From the newly staged records, the import went smoothly. We had previously imported the same records in our test environment and everything had gone flawlessly. In any case, we've got a huge number of deleted records we'd like to eliminate from the database. Andy On 6/25/19 4:49 PM, Alvaro Cornejo wrote:
Hi
If you do a Marc import through the koha importing tool, you can remove the records through the same process. You just need to check which import process you want to remove and that's it.
Regards,
Alvaro |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com
Le mar. 25 juin 2019 à 15:44, Andy Boze <boze.1@nd.edu> a écrit :
Dear all,
I'm hoping someone can give me a bit of direction. We have a large number of deleted biblio records (due to a failed MARC records import). We'd like to remove the deleted records from the database as there are somewhat more deleted records (401,000) than active records.
Is there a script than can clean up deleted records? I've seen this "Clean up database" script <
https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-data...
, but it's not what we're looking for.
If there's no script, can we safely use the MySQL TRUNCATE command on the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and deleteditems tables? This is a non-circulating library, so I don't think the biblionumber would be tied to any other tables.
I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.
-- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708 _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708
On 2019-06-25 4:43 p.m., Andy Boze wrote:
Dear all,
I'm hoping someone can give me a bit of direction. We have a large number of deleted biblio records (due to a failed MARC records import). We'd like to remove the deleted records from the database as there are somewhat more deleted records (401,000) than active records.
Why not go back to your previous backup? Quick, simple, painless. Best -- Paul
Is there a script than can clean up deleted records? I've seen this "Clean up database" script < https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-data...
, but it's not what we're looking for.
If there's no script, can we safely use the MySQL TRUNCATE command on the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and deleteditems tables? This is a non-circulating library, so I don't think the biblionumber would be tied to any other tables.
I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.
To clarify the "Go back to previous backup" idea... assuming you have a backup that will work, the normal challenge here is circulation transactions that took place since the bad import. This often means running and printing an issues report before restoring, and then manually re-entering the circulation from the impacted period, with correct due dates, etc. If there's a lot of traffic through the library, this can be a real pain, but it shouldn't be a problem at all for a non-circulating library. If you don't have backups, this is the reminder that you should be taking them. Joel Coehoorn Director of Information Technology 402.363.5603 *jcoehoorn@york.edu <jcoehoorn@york.edu>* *Please contact helpdesk@york.edu <helpdesk@york.edu> for technical assistance.* The mission of York College is to transform lives through Christ-centered education and to equip students for lifelong service to God, family, and society On Tue, Jun 25, 2019 at 4:28 PM Paul A <paul.a@navalmarinearchive.com> wrote:
On 2019-06-25 4:43 p.m., Andy Boze wrote:
Dear all,
I'm hoping someone can give me a bit of direction. We have a large number of deleted biblio records (due to a failed MARC records import). We'd like to remove the deleted records from the database as there are somewhat more deleted records (401,000) than active records.
Why not go back to your previous backup? Quick, simple, painless.
Best -- Paul
Is there a script than can clean up deleted records? I've seen this "Clean up database" script <
https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-data...
, but it's not what we're looking for.
If there's no script, can we safely use the MySQL TRUNCATE command on the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and deleteditems tables? This is a non-circulating library, so I don't think the biblionumber would be tied to any other tables.
I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Thanks, Joel. I've been considering that. We do have a backup from immediately before the failed import. There have been some records added by our catalogers since then, but I think I can pretty easily identify them. I was just hoping there'd be an easy way to purge the deleted biblio records. Andy On 6/25/19 5:47 PM, Coehoorn, Joel wrote:
To clarify the "Go back to previous backup" idea... assuming you have a backup that will work, the normal challenge here is circulation transactions that took place since the bad import. This often means running and printing an issues report before restoring, and then manually re-entering the circulation from the impacted period, with correct due dates, etc. If there's a lot of traffic through the library, this can be a real pain, but it shouldn't be a problem at all for a non-circulating library. If you don't have backups, this is the reminder that you should be taking them.
Joel Coehoorn Director of Information Technology 402.363.5603 *jcoehoorn@york.edu <jcoehoorn@york.edu>*
*Please contact helpdesk@york.edu <helpdesk@york.edu> for technical assistance.*
The mission of York College is to transform lives through Christ-centered education and to equip students for lifelong service to God, family, and society
On Tue, Jun 25, 2019 at 4:28 PM Paul A <paul.a@navalmarinearchive.com> wrote:
On 2019-06-25 4:43 p.m., Andy Boze wrote:
Dear all,
I'm hoping someone can give me a bit of direction. We have a large number of deleted biblio records (due to a failed MARC records import). We'd like to remove the deleted records from the database as there are somewhat more deleted records (401,000) than active records.
Why not go back to your previous backup? Quick, simple, painless.
Best -- Paul
Is there a script than can clean up deleted records? I've seen this "Clean up database" script <
https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-data...
, but it's not what we're looking for.
If there's no script, can we safely use the MySQL TRUNCATE command on the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and deleteditems tables? This is a non-circulating library, so I don't think the biblionumber would be tied to any other tables.
I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708
participants (4)
-
Alvaro Cornejo -
Andy Boze -
Coehoorn, Joel -
Paul A