Is anyone with DB/Text for Libraries actually using the waiting list function? I'm realizing that you cannot add more than one person to the waitlist for an item at a time, due to the waiting list being a linked field to the borrower textbase. Has anyone come up with another way to do this that allows a useful waiting list to be created? Only one name on the list means I will still have to keep a manual list of all the rest of the people waiting - frustrating!

Inmagic Genie supports multiple Reserves (the equivalent of the DBTfL waiting list function).

Ah yes...sadly I am stuck with what I've got for the time being. Thanks anyway!

Loans does link to Catalog, and Catalog does have a Waiting List field that was used in the old Library Guide before the field was moved to Loans with the implementation of DB/Text for Libraries.

In theory, you could keep the Waiting List in the Catalog record, and still display the field in Loans reports, displays and edit screens.

Or, you could change the Waiting List field in Loans to not be a Link field. (You could give it a validation list to make it easier to paste borrower's names.)

It's been a long time since I looked at DBTfL, so I'm not sure what script/workflow issues this might introduce.

Hi Leanne

I share your frustration with the way the waitlist works. Our problem is not so much that we have multiple people waiting, but rather that there may be several copies of a book and the waitlist only works for one at a time rather than providing the first copy that comes in. I have a possible solution in mind, but haven't had a chance to implement it yet. My idea was to create a waitlist field in the catalogue textbase and have this field show in the returns screen (or anywhere else it is needed). You would then be able to see who wants what for each book returned and then manually remove the name at the top of the list by using "Edit secondary textbase". As I say, I haven't actually done it yet so there may be issues I haven't thought of. Cheers. Raewyn

CDale & Raewyn,

You have both suggested keeping the waiting list in the catalogue textbase...this definitely seems like a plausible idea, and I might try it. I can think of 2 problems though...1) the person checking the book in has to remember to go into the catalogue record and modify the list (or could this be done directly from within the returns screen? I've never tried anything like that - I'm still pretty new to this). and 2) the names being entered in the waiting list field couldn't be taken from the borrowers textbase directly because a link field couldn't be used. I'd either have to just use a free text field or have a validation list which would have to be repopulated regularly as the valid borrower list changes.

But...still worth a try. Thanks both of you for your suggestions! I may play around with this, and would also be interested in hearing how it ends up working for you Raewyn, if you end up trying it.

Leanne