Robert Heller

Did you create a user with Librarian access (see page 2 od the manual under “User Role Setup”. The admin user does not have access to the library’s database, just as the library staff does not have access to the adminstration functions on the dashboard. This is by design. Read the “User Role Setup” section starting at the bottom of page 2 and continuing on the top of page 3.

Are you still having problems?

PS: The type item of the recognized columns list is on page 12 (there are some intervening figures on pages 10 and 11).

I need to have a look at the bulk delete code. Something is not right there. And yes, I guess I need to look at the documentation as well…

The GAN_Server loop is most efficient when the number of merchants / advertisers with at least one compatible ad exceeds the number of ads specified for an ad unit. The GAN_Server loop will loop though the merchants / advertisers just once. If the number of ad requested for the ad unit is greater than the number of merchants / advertisers with compatible ads, it will loop though the merchants / advertisers ad many times as needed to fill the ad unit. Thus if you only have two merchants / advertisers and have an ad unit with 6 ads, it will loop though the merchant / advertiser list 3 times, with two inner loop cycles per outer loop cycle.

Note: if you have merchants / advertisers who don’t have compatible ads (compatible: banner size or banner vs. text) it will still do lookups (possibly multiple lookups) with those merchants / advertisers — this will take time. If you have a 468×60 banner ad unit calling for 4 banners and if you have 10 merchants / advertisers, but only 2 have 468×60 banner ads, the ad server (GAN_Server.php) will loop through all 10 merchants / advertisers twice, that is it will make 20 MySQL lookups, 16 of which will return in empty results. You would either need to reduce the number of ads displayed in this ad unit or get 468×60 banner ads for more of the merchants / advertisers.

It is possible that you have set the number of ads in one or more of your ad units too high (too many ads per unit). You can try reducing the number of ads per ad unit.

I pushed a new version, 3.2.4, of the Web Librarian plugin. This verison includes code to delete holds and checkouts of an item when you delete the item — that is, it prevents orphaned holds and checkouts.

I also added a Collection Database Maint. page that has a button to delete holds and checkouts for deleted items and patrons. You should be able to use this page to clear out your orphaned holds and checkouts.

Somehow you managed to place a hold on an item not in your collection. I think the only way that would be possible is that the hold was placed on an item that was later deleted.

Try creating an item with the problem barcode, even if it is a ‘dummy’ item. Right now, the system does not handle deleting items with holds or checkouts — the hold and checkout records are left dangling.