New Build Under Construction
The latest iBorrow build on January 19 finally got it right. It fixed some long standing problems and introduced some nice new features. SirsiDynix is already working on and testing the next installment. We’ll probably see it on Wednesday, February 21, so mark your calendars. (In pencil)
If I can get a complete list of the new features prior to the download, I’ll put them out. Here’s some initial information.
1. The ‘patron friendly’ messages that missed the bus last time will appear in the My Account part of the portals. We may still need to offer suggestions for improvement, but the idea is that the patron will actually be able to correctly interpret the statuses there.
2. If a patron has an iBorrow identity, and if you do a proxy request for that patron, the request you do will link up with his record and show up in the My Account list of active requests.
3. In Receive Loan, the default active ‘blank’ will be “Local Barcode”, which—as you ALL know—is the one you use whether you are using the barcode that came on the borrowed item or a barcode of your own. (Give me a call, if this sounds like something that just came out of the Twilight Zone.)
4. You will be able to use a ‘different ISBN’ when you fill loans. I’m waiting for more detail on this one, but here’s how I think it will work. Pay attention; this can be tricky.
· We and our patrons think of their active requests in terms of titles. They want “The World Is Flat” or “Ice Age”. But URSA/iBorrow thinks of them in terms of their ISBN’s. When you said you wanted “The World Is Flat”, did you mean 0374292884, or did you mean 0374292795?
· If the patron originally clicked on Request Item next to the bib record with the first ISBN (Hardcover), and you try to fill it with the second ISBN (Paperback), iBorrow will get cranky and uncooperative, even though both ISBN’s are in the same Bib record.
· With the new build, you will have a ‘graceful’ way to pat iBorrow on its little head and say, “It’s all right. I know what I’m doing.” And get on with filling the request.
5. The new OCLC bugs will be fixed.
As I learn more, I’ll pass it along.