Billing

Return to JavaClient page

How To

When posting an enhancement request, create a title under the appropriate category (General, Circulation, Item Management, etc.)  Then highlight the title and change the format (in toolbar) to heading 3.

Billing How To Paying Bills Billing a User Mark Item Lost Won't save item id Update -- Won't save Item ID

 

Paying Bills

Billing a User

Mark Item Lost

Won't save item id

When a student was paying for a lost book, I was trying to mark the item lost.  I pulled up the students record and clicked on the book id to pull up the book information, but when I went to the screen to mark item lost, it had under current item the last book checked out not the book that I had clicked on to mark lost.  I almost marked the wrong book as lost.  I had to go back and pull up the student record again and write down the bar code number (because of course I didn't have the book there to scan).  Can we make the current item on that screen be the last book we had brought up the record for instead of the last book checked out?  Kristy

Update -- Won't save Item ID

I looked through all properties that should control this, but couldn't find the cause.  The feature of carrying over an item ID works as expected in the C Client using the same login as the JavaClient.  I referred the issue to Sirsi. -- John

Sirsi's response: They are aware of the bug (even though they won't call it a bug).  This will not be fixed until the next release which is scheduled before the end of this year.

By the way, this bug effects not only the Mark Item Lost Wizard, but also any other wizard which is supposed to include current copy.  Normally, in the C Cllent, any item you "touch" (view, click on in a user record, etc.) is made current copy and is carried over to the next wizard.  In JavaClient, you need to actually update the item record in some fashion -- edit, checkout, etc.

I have never been first in line when upgrading to a new release.  The reason for this is justified by Kristy's discovery -- we do not want to commit and then discover all the bugs.  I let other Sirsi users jump in on a new release, then I watch the Sirsi ListServ blow up with complaints.  Within a couple of months, Sirsi provides fixes to bugs.  This generates a new round of complaints, because at times their fixes break other parts of the program.

This definitely precludes any possibility of our rolling JavaClient out to the rest of the libraries this year.