Feedback Wanted: BARD load & Service Queues

We have a question we'd love your feedback on!

Right now, when you load your BARD statistics, the Has-Had records are added for titles that your patrons downloaded and back-dated to when the download actually occurred. At this time, if the patron has a request for a Title that they later downloaded, the request is removed so the patron doesn't get what will essentially be a duplicate title.

Should something similar happen with Service Queues? Our current thinking is, if a patron downloaded any title after it was placed on their Service Queue (by any means--request, book search, series, subject, etc, etc), it should be removed.

(Of course, if a title is duplicated between when the patron downloads it and when the BARD stats are loaded, there isn't anything we can do to catch that.)

Does that sound good, or not quite right? Does this need to extend to Duplication Orders? Would you want the ability to toggle this on or off for your library? Should we make any exceptions, such as series?

Please let us know--we want to hear from you!!

I believe that the practice of removing the pending request should continue.

Yes, duplicate requests should be removed.

Sounding pretty positive so far!

Please remember, though, there'll be times when a title has already been duplicated by the time you load the BARD statistics for the previous month. There may also be times when a patron downloads a book from one of their series, leaving a "gap" in the series on their next cartridge.

With cases like that in mind, are we still all thumbs-up and green lights? Any objections out there?

Well, yes, but most patrons are fine with the explanation that our automated system is working properly. By and large, people get that clerical issues are still a thing in the age of the interwebs

I'm going to chime in with a quick word, from my tiny internal windowless bad plumbing office,
I think something downloaded from BARD should be removed from the Service Queue, in order to prevent them from ending up accidentally in an order as things are pulled at the time of creating the next order. We also consider that some patrons may be insistent on getting a book a second time in recent succession, but this probably isn't a thing that happens very often.
In our case, now that we've been doing duplication on demand for over a year and have had a chance to "stress test" the system it would great to extend this ability to have items that could be flagged and removed from upcoming orders also. To have the ability to "manipulate" an order would be powerful. It is understood that this requires some changes to programming, but it's an idea worth floating for future development.

Katy, has this feature been incorporated into KLAS yet?

This has not yet been implemented--thank you for bringing it back up on our radar!

One more wrinkle for you all to weigh in on as we get this slotted into the development calendar: what about series books? If the patron downloaded #2 from BARD, but has #1, #2, #3 in the service queue -- what should we do?

We aren't sure yet if it would be easy for us to catch these situations and make an exception to leave downloaded titles in place to avoid creating gaps in a series... but we want to be patron friendly if we can, so let us how you would want us to approach this, or if there's anything else you want us to keep in mind.

Yes, I agree that if a patron downloads a book that is on their SQ, it should be deleted from the SQ once it's downloaded. I do not think an exception should be made for series -- still delete the downloaded title. For Dup Order lists too.

Thx!