How did the test of the new build go?
Right now, you’re probably asking yourself, “How did the test of that new iBorrow build go this weekend?” To sum it up in a few words, “Half a fix is better than none.” (Which sounds like something a drug addict would say.)
The OCLC connection seems to be fixed, and the aging problem seems not to be. That’s a pretty wishy-washy assessment, so here’s some more detail.
Matt and I have both been able to push requests to OCLC, get the “Pending response from ISO lender” message, and see them move from Mediated Borrowing to Receive Loan a few minutes later. That’s a good thing.
That worked whether Mediation was turned ON or OFF for OCLC. However, I have not yet been able to devise a reliable test to see if a request will go to OCLC unmediated, if it is not fillable locally. Still working on that.
“Aging” fails to work, in that we found requests in Fill Loan and Mediate Loan both Saturday and Sunday that—based on their “Process By” date–should have moved on to the next lender in the string. So, any Aging fix in the new build did not affect requests that had been placed before the new build was loaded. It is possible that it will work correctly with requests that are placed after the download. I think Tuesday is the soonest we could know that.
The other good news is that nothing new seems to have been broken. We got no weird, inexplicable error requests in any of our testing.
But there’s a catch to that one, too. You will almost certainly have trouble loading the new build. You will get Java load errors. You will be annoyed. You will probably say words your mother would disapprove of.
To reduce that aggravation, I have posted “The Fix” below. So far, it has worked every time. If it fails for you, or if you need help with it, give me a call. Matt is on vacation this week.
If we learn new things about the build this week, I will send a follow up to his message. And, as always, the information will be here on Beth’s Blog.
THE FIX
Correctly loading the new build is a two step process: clearing your web browser’s cache, and deleting old Java files. Let’s take them one at a time.
Web Browser
Open your web browser and choose Tools, then Internet Options.
Delete your Browsing History (also called Temporary Internet Files) and delete your cookies.
Java
1. Find the Java icon in your control panel. If you are using Windows XP, the path should be:
Start—Control Panel—Java
If you have some other flavor of Windows, it may be Start—Settings—Control Panel—Java
2. Right click once on the Java icon, then click on Open
3. Click on the tab at the top called General. (This will probably be the default)
4. Find the area near the bottom of the Java Control Panel that says Temporary Internet Files.
5. Within that area, find the Delete Files… button and click it once.
6. In the Delete Temporary Files window that pops us, make sure there is a check mark in all three boxes.
7. Click OK
8. Click OK to close the Java Control Panel
9. Close Control Panel by clicking the X in the upper right hand corner.
10. Launch your web browser (if it is not still open) and go to http://iborrow.asp.dynix.com/dynix
11. It should say Welcome to the URSA Information Portal.
12. Find the blue link that says URSA Information Administration Client and click on it.
13. Make sure the “I agree” radio button is marked with a dot, then click on the I Agree button in the bottom center of the screen. You may have to use the blue vertical scroll bar on the right to bring the I Agree button into view.
14. Java will start loading the new build. The small window should be labeled Java Web Start, and it should say SirsiDynix Client in the center.
15 At the end, you should get a new window that says “The application’s digital signature has been verified. Do you want to run the application?” There should also be a green check in the “Always trust content from this publisher” box. Click on the Run button.
16. The next window will ask whether you want to create desktop and start menu shortcuts. Click on Yes.
17 Log in and go. Close your browser or click on the Home button.
If this doesn’t work, call 813-622-8252 ext 223.
–Al Carlson