Fred, Ebooks is the classic best case use of the Undo Import feature. Especially in a case like yours were the bibs have no items. You can import the batch (maybe with a note to show when to remove) And when you're ready, you undo the import and those bibs are removed. You should not see any issues in the use-case you describe. Your other option of creating an itemtype of R2 records works as well. You can use a Report to gather the itemnumbers for the R2 items, feed them into the Batch Deletion tool and remove them (and the bib) that way. This way is a bit more work, but works just as well. joy On Fri, Dec 2, 2016 at 7:17 AM, King, Fred <Fred.King@medstar.net> wrote:

Raymund, and others who have used the Undo Import feature,

Since I was about to do pretty much the same thing, could you tell me what little tendrils were left when you did an Undo? I loaded a batch of e-books a while back (ClinicalKey and ClinicalKey nursing), and I was planning to undo that batch and load the latest collection. They're just catalog records with 856 tags pointing to the online book--no item records, checkout history or anything similar. We're using Koha 16.05 with Ubuntu 14.04LTS.

We're also about to offer our users the Rittenhouse R2 collection. This gives our users access to a huge collection of medical books. Any book may be used up to three times without extra charge; once that limit has been reached, we have to decide whether to buy the e-book for our e-book collection.

I'm just starting to think of ways to handle this in Koha; if anyone else has worked with a collection that provides access for x number of uses and then disappears (if we decide not to purchase it) or provides unlimited access (if we do purchase it), I'd love to hear from you.

My current thought is to add all the R2 MARC records as a new item type and put a note in the OPAC Results and OPAC Detail screens that explains what this collection is and how it works. Once the limit has been reached, I could change the item type to R2--added to collection or R2--not added to collection. Has anyone come up with a better way?

Fred King Medical Librarian, MedStar Washington Hospital Center fred.king@medstar.net 202-877-6670 ORCID 0000-0001-5266-0279

I have one of those metabolisms where I can eat whatever I want and my body converts it to energy and stores the excess as fat. --Randall Munroe, xkcd

-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Tomas Cohen Arazi Sent: Friday, December 02, 2016 6:35 AM To: Raymund Delahunty; Koha Subject: Re: [Koha] What is the point of the Undo Import into catalogue feature?

File a bug report for that issue, please.

El vie., 2 de dic. de 2016 1:26 AM, Raymund Delahunty < r.delahunty@arts.ac.uk> escribió:

...

We regularly import large files of MARC records into our Koha (16.05) database which have to be deleted at a later date… sometimes months later, and sometimes maybe 30,000 records. I have been using the Undo import (sort-of “unstage”) as I found this functionality astoundingly useful. It automated a task, reducing a tedious job to a couple of keystrokes.

However I was dismayed to find that after a recent “Undo” of 13,000 records our database was left over 7,000 “phantom records”- they didn’t exist but the indexing had failed to remove all traces of them

We were advised to use the batch record deletion tool, as the Undo feature wasn’t designed to be used in the way I was using it. “… it is meant to unstage records nearer to the point in time of being added”. (And what’s the point of that?) We had to have our database re-indexed to resolve the problem. Is there any point in the Undo feature if the indexer can’t cope? I hate to think what other dross I had left behind in earlier “Undos”!

Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of London Artscom Limited the following also applies: London Artscom Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY _______________________________________________ Koha mailing list https://urldefense.proofpoint. com/v2/url?u=http-3A__koha-2Dcommunity.org&d=DgIGaQ&c= RvBXVp2Kc-itN3g6r3sN0QK_zL4whPpndVxj8-bJ04M&r= vKh6XwOmjyC51IkP1OfsdjQZoWT2vpi6VZl8El8EPRI&m=9HgKeQfspPjCz5_ fso8ju2Ouo2mzHnznf9j5rOOAfQk&s=KvyxbTSUc4SCX2hi2AiZtTSgBBZldj YrL3SEBErtuh8&e= Koha@lists.katipo.co.nz https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. katipo.co.nz_mailman_listinfo_koha&d=DgIGaQ&c=RvBXVp2Kc- itN3g6r3sN0QK_zL4whPpndVxj8-bJ04M&r=vKh6XwOmjyC51IkP1OfsdjQZoWT2vp i6VZl8El8EPRI&m=9HgKeQfspPjCz5_fso8ju2Ouo2mzHnznf9j5rOOAfQk&s=4m_ gZaf5cpKBRqolx7EPLuBTNefqFRRxNtgwcOJMROU&e=

-- Tomás Cohen Arazi Theke Solutions (https://urldefense.proofpoint.com/v2/url?u=https- 3A__theke.io&d=DgIGaQ&c=RvBXVp2Kc-itN3g6r3sN0QK_zL4whPpndVxj8-bJ04M&r= vKh6XwOmjyC51IkP1OfsdjQZoWT2vpi6VZl8El8EPRI&m=9HgKeQfspPjCz5_ fso8ju2Ouo2mzHnznf9j5rOOAfQk&s=tAdbJd2tMzGKv7lCIhP0XF896zMS1g D3dQ47oG6lvh0&e= <https://urldefense.proofpoint.com/v2/url?u=http- 3A__theke.io_&d=DgIGaQ&c=RvBXVp2Kc-itN3g6r3sN0QK_zL4whPpndVxj8-bJ04M&r= vKh6XwOmjyC51IkP1OfsdjQZoWT2vpi6VZl8El8EPRI&m=9HgKeQfspPjCz5_ fso8ju2Ouo2mzHnznf9j5rOOAfQk&s=SwtFOGW1Uc4njHZnhkQvsmguNp4Gxf rbBkaRDxlmxLU&e= >) ✆ +54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha mailing list https://urldefense.proofpoint. com/v2/url?u=http-3A__koha-2Dcommunity.org&d=DgIGaQ&c= RvBXVp2Kc-itN3g6r3sN0QK_zL4whPpndVxj8-bJ04M&r= vKh6XwOmjyC51IkP1OfsdjQZoWT2vpi6VZl8El8EPRI&m=9HgKeQfspPjCz5_ fso8ju2Ouo2mzHnznf9j5rOOAfQk&s=KvyxbTSUc4SCX2hi2AiZtTSgBBZldj YrL3SEBErtuh8&e= Koha@lists.katipo.co.nz https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. katipo.co.nz_mailman_listinfo_koha&d=DgIGaQ&c=RvBXVp2Kc- itN3g6r3sN0QK_zL4whPpndVxj8-bJ04M&r=vKh6XwOmjyC51IkP1OfsdjQZoWT2vp i6VZl8El8EPRI&m=9HgKeQfspPjCz5_fso8ju2Ouo2mzHnznf9j5rOOAfQk&s=4m_ gZaf5cpKBRqolx7EPLuBTNefqFRRxNtgwcOJMROU&e=

---------------------------------------------------------------------- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopaedics, cancer and GI.

IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you.

Help conserve valuable resources - only print this email if necessary.

_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha

-- Joy Nelson Director of Migrations ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

That is exactly the way I have used the feature many times in the past- well, once to correct an incorrectly modified batch a few moments after the data was loaded, when I spotted a second necessary correction I had missed (much to my annoyance), and maybe 2 dozen times to rip out previously loaded (often large) batches of records weeks after they had been loaded, once the data was no longer needed. The problem isn’t that I don’t understand how to use the feature (indeed I love it) but my recent experience suggests it doesn’t work correctly. Maybe 2 months ago I loaded 11,300 records for a patron-driven-acquisitions program. They were records for streaming media supplied by Kanopy. We bought 85 of the titles. I was asked to remove the records for the titles we had not purchased. I expected it to be a simple task- press Undo Import, and pull all the records out, and add the 85 records purchased back in (I had been supplied with a file of our purchases). After the job completed, I searched on Kanopy in both staff side and OPAC and found c.250 results, much to my surprise. (I expected to find zero records.) When I clicked on the MARC 710 I was taken to a list of c.7,200 records via (in effect) the authority record for Kanopy (Firm). I could also navigate to that list on OPAC. However these tendrils were “faulty”. Clicking on the title (for example) in OPAC, took the user to a server error 404- Page not found. (But if they clicked on the 856 they were taken to the Kanopy platform). In staff-side, clicking on the record resulted in an error “Record not found” (well, something similar). Attempting to export the MARC file by biblionumber resulted in an empty export file. (I have supplied my screenshots and notes directly to Fred King, who was asking what rubbish was left after my Undo). In short, my Undo had NOT worked properly. The database had to be re-indexed to get rid of the tendrils. I have another “Undo” scheduled (two files, one of 2,000 records, one of 30,000 records). I am tempted to have one more try, before raising this issue in Bugzilla. I suspect the Undo will not work, and that yet again we will have to have a re-index. And that in future we will have to rely on Batch Record Deletion, rather than the delightful Undo feature. Ray Delahunty University of the Arts London From: Joy Nelson [mailto:joy@bywatersolutions.com] Sent: 02 December 2016 14:53 To: Raymund Delahunty <r.delahunty@arts.ac.uk> Cc: Koha <koha@lists.katipo.co.nz> Subject: Re: [Koha] What is the point of the Undo Import into catalogue feature? Ray- The undo import feature has saved me more than once as I realize immediately after import that I have incorrectly modified the batch of records. Immediately reverting the batch is useful. The other main use for the undo import feature is in ebooks as Fred King talks about in the other thread. Thanks joy On Thu, Dec 1, 2016 at 10:26 PM, Raymund Delahunty <r.delahunty@arts.ac.uk<mailto:r.delahunty@arts.ac.uk>> wrote: We regularly import large files of MARC records into our Koha (16.05) database which have to be deleted at a later date… sometimes months later, and sometimes maybe 30,000 records. I have been using the Undo import (sort-of “unstage”) as I found this functionality astoundingly useful. It automated a task, reducing a tedious job to a couple of keystrokes. However I was dismayed to find that after a recent “Undo” of 13,000 records our database was left over 7,000 “phantom records”- they didn’t exist but the indexing had failed to remove all traces of them We were advised to use the batch record deletion tool, as the Undo feature wasn’t designed to be used in the way I was using it. “… it is meant to unstage records nearer to the point in time of being added”. (And what’s the point of that?) We had to have our database re-indexed to resolve the problem. Is there any point in the Undo feature if the indexer can’t cope? I hate to think what other dross I had left behind in earlier “Undos”! Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of London Artscom Limited the following also applies: London Artscom Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha -- Joy Nelson Director of Migrations ByWater Solutions<http://bywatersolutions.com> Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/> This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of London Artscom Limited the following also applies: London Artscom Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

I ran repeated tests for up to 48 hours or more. I think the indexes were partly updated- 7K out of 13K "remained". I have two files to deal with tomorrow (3K, and 30K small MARC records- bibs and items). I am tempted to try the Undo again to see if it works. I am asking our support company PTFS Europe about any issues there might be with the zebra indexer. If it goes wrong again I'll ask for another index rebuild, and give up on the Undo feature. Ray Delahunty. -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Francois Charbonnier Sent: 05 December 2016 13:14 To: koha@lists.katipo.co.nz Subject: Re: [Koha] What is the point of the Undo Import into catalogue feature? Hi, Have you waited long enough for zebra to re-index your catalogue ? To me, what you are describing is not faulty. Once you reverted an imported batch, it takes time to zebra to remove the records from the indexes. Especially if you work with large files. If you waited long enough and the indexes never got updated, I would say it's faulty, yes. But it you reverted the import and search for records right away, I would say it's just zebra that hasn't been able to reindex everything... François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | Spécialistes en technologies documentaires | www.inLibro.com <http://www.inLibro.com> Le 2016-12-05 à 03:31, Raymund Delahunty a écrit :

That is exactly the way I have used the feature many times in the past- well, once to correct an incorrectly modified batch a few moments after the data was loaded, when I spotted a second necessary correction I had missed (much to my annoyance), and maybe 2 dozen times to rip out previously loaded (often large) batches of records weeks after they had been loaded, once the data was no longer needed.

The problem isn’t that I don’t understand how to use the feature (indeed I love it) but my recent experience suggests it doesn’t work correctly.

Maybe 2 months ago I loaded 11,300 records for a patron-driven-acquisitions program. They were records for streaming media supplied by Kanopy. We bought 85 of the titles. I was asked to remove the records for the titles we had not purchased. I expected it to be a simple task- press Undo Import, and pull all the records out, and add the 85 records purchased back in (I had been supplied with a file of our purchases).

After the job completed, I searched on Kanopy in both staff side and OPAC and found c.250 results, much to my surprise. (I expected to find zero records.) When I clicked on the MARC 710 I was taken to a list of c.7,200 records via (in effect) the authority record for Kanopy (Firm). I could also navigate to that list on OPAC.

However these tendrils were “faulty”. Clicking on the title (for example) in OPAC, took the user to a server error 404- Page not found. (But if they clicked on the 856 they were taken to the Kanopy platform). In staff-side, clicking on the record resulted in an error “Record not found” (well, something similar). Attempting to export the MARC file by biblionumber resulted in an empty export file. (I have supplied my screenshots and notes directly to Fred King, who was asking what rubbish was left after my Undo).

In short, my Undo had NOT worked properly. The database had to be re-indexed to get rid of the tendrils. I have another “Undo” scheduled (two files, one of 2,000 records, one of 30,000 records). I am tempted to have one more try, before raising this issue in Bugzilla. I suspect the Undo will not work, and that yet again we will have to have a re-index. And that in future we will have to rely on Batch Record Deletion, rather than the delightful Undo feature.

Ray Delahunty University of the Arts London

From: Joy Nelson [mailto:joy@bywatersolutions.com] Sent: 02 December 2016 14:53 To: Raymund Delahunty <r.delahunty@arts.ac.uk> Cc: Koha <koha@lists.katipo.co.nz> Subject: Re: [Koha] What is the point of the Undo Import into catalogue feature?

Ray- The undo import feature has saved me more than once as I realize immediately after import that I have incorrectly modified the batch of records. Immediately reverting the batch is useful. The other main use for the undo import feature is in ebooks as Fred King talks about in the other thread. Thanks joy

On Thu, Dec 1, 2016 at 10:26 PM, Raymund Delahunty <r.delahunty@arts.ac.uk<mailto:r.delahunty@arts.ac.uk>> wrote: We regularly import large files of MARC records into our Koha (16.05) database which have to be deleted at a later date… sometimes months later, and sometimes maybe 30,000 records. I have been using the Undo import (sort-of “unstage”) as I found this functionality astoundingly useful. It automated a task, reducing a tedious job to a couple of keystrokes.

However I was dismayed to find that after a recent “Undo” of 13,000 records our database was left over 7,000 “phantom records”- they didn’t exist but the indexing had failed to remove all traces of them

We were advised to use the batch record deletion tool, as the Undo feature wasn’t designed to be used in the way I was using it. “… it is meant to unstage records nearer to the point in time of being added”. (And what’s the point of that?) We had to have our database re-indexed to resolve the problem. Is there any point in the Undo feature if the indexer can’t cope? I hate to think what other dross I had left behind in earlier “Undos”!

Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of London Artscom Limited the following also applies: London Artscom Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha

-- Joy Nelson Director of Migrations ByWater Solutions<http://bywatersolutions.com> Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/> This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of London Artscom Limited the following also applies: London Artscom Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY _______________________________________________ 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 This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of London Artscom Limited the following also applies: London Artscom Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY