|
|
HOME | About PALNI | PALNI OPAC | Digital Library | Recent News |
|
|
Earlham . Franklin . Goshen . Grace . Hanover . Huntington Manchester . Marian . Oakland City . St Francis . St Josephs St Meinrad . Taylor . Trine . U of Indianapolis . Wabash |
User loginOPAC Quick Search |
UPDATE: Vers. 17.01 Patron ProblemSubmitted by susan on Thu, 06/30/2005 - 9:21am.
BACKGROUND: Around March 1st, we made a copy of the hickory patron database (i.e., a snapshot) of all the existing patrons and transactions on hickory (your production database). It was loaded along with the bibliographic and other data from hickory to the spruce server in preparation for conversion to v.17.01 software. When Ex Libris staff had us start reporting problems with the conversion on spruce, one of the first (and major issues) we reported is the inability on spruce server to view local or global patron information for the converted patron records of your ADMs. For instance, we could not see WCP or UIP records. We requested resolution of this issue and requested a way to test the patron database with the new "user-sharing" feature to see if it was workable for PALNI. Ex Libris staff had difficulty in getting the patron database to that point. They have now figured out the PALNI patron problem we were pointing out in v.17.01 on spruce server. EX LIBRIS REPORT: Ex Libris staff tested their proposed fix to the problem with patron records for 2 ADMs yesterday. I will be looking at the solution this morning to see if it indeed fixes the problem. Here is what Ex Libris staff said about the problem: "When we were running the [spruce v17.01] batch job to fix The z353 records, by way of explanation, are a component of what allows consortial user-sharing to work in the v17.01 software. ACTION PLAN FOR TODAY, 6/30: After checking the results of Ex Libris work from yesterday, if I find their patron database solution did work on the 2 ADMs they ran through the fix process, I will run the program on all the other ADMs on spruce v.17.01. Any new spruce patron records you may have created as you started testing circulation from Friday forward may be wiped out by the fix process. After I announce that the process is complete, you can create some new "play" patrons if you wish or use existing patron records for testing. We appreciate your patience as this problem is being resolved. I will let you know as quickly as possible when I get the fix in place for everyone, and what you should expect to see afterward on spruce for v.17.01. Hopefully, this will get one more major roadblock cleared for your August 8 switch to v.17.01 on hickory! Regards, Susan susan's blog | printer friendly version | 157 reads
( categories: Aleph News and Information | Circulation )
|