WYLD Office Report for October 18 and November 8, 2005
SirsiDynix merger update
Things are going smoothly. Companies are merged. Actions are being taken to have the help support folks in both using the same metrics for customer satisfaction measurement and more importantly for improvement. Little loss in the developer/programmer community with the merged company so new, improved and corrective software development cycles are being done more quickly and thoroughly.
Access to Client Care site of Sirsi
I encourage all Council members to make regular visits to the Sirsi Client Care customer website. This access is very helpful if you want to see information about the next upgrade, the release notes for that upgrade which include enhancements, corrections, and additions. They are lengthy so you may not wish to print them out until that version has been put into general release. This also includes access to the Getting Ready for Unicorn GL3.0 Multimedia Tour an interactive introduction to the new features of Unicorn GL3.0.
If it is easier I could make a generic shared Board login. It might work for general scanning of information at the Client Care website of Sirsi. But it is better to have your own login because you can receive emails about subject areas of interest such as Consortia issues, Cataloging, Circulation, Unicorn-general and the like. We can talk about this if you wish during our conference call.
To login: http://www.sirsi.com/Solutions/Prodserv/Services/clientcare.html Click on the blue "Login to Client Care" button. If you do not have user id and password or if these no longer work please contact Brian.
Again, if you want a login or need to renew one call or email me. I can also give you a 15 - 30 minute online tour of its key areas any time over the phone.
Upgrade updates:
No date fixed yet for WYLD's GL 3.0 upgrade. TAZ, our test server received the necessary Solaris 10 operating system upgrade and this took longer than expected. I asked Regional Council to help the WYLD Office determine which libraries use the test server for training and practice AND more importantly, how much notice does our Office need to give member institutions about a major change to the test server, TAZ. Results from Nov.8, 2005 conference call: There is some use of TAZ for training and practice but less than thought AND 72 hours was the recommended minimum warning period prior to any MAJOR update of TAZ.
As some of you know, TAZ is finally back up and running. Marc got the Unicorn upgrade (GL 3.0) loaded on Wed., Nov. 23, 2005.
So now: we can look again at the new iBistro interface as requested by Region reps at: http://taz.state.wy.us If you go to TAZ via WorkFlows you will have to upgrade your client. We highly recommend the "C" client (the standard one) for now. We will focus on the Java client in the spring of 2006 and thus don't want to spend much time supporting or training for the Java client until then.
We would love to move to GL 3.0 on WYLD, the production server in the new two months again with a focus on using the "C" client.
I have just received checklists from Sirsi that are used with their Beta Test customers. I think we'll find these helpful as we prepare for the current and future upgrades. We will modify these so they "sync" with WYLD Unicorn functions. I firmly believe these will help all of us test more completely the software on TAZ before moving it on the WYLD production server. There are checklist for each of the following function areas: general, cataloging, circulation, serials, acquisitions, reports, and reserves. As time goes on, we can add other items as we learn and grow. For instance, there is a "general" checklist item for add on products (Self Check stations, print management systems, PC reservation systems, etc) that work either via SIP2 or NCIP interface with the WYLD server.
Bergen County cooperative Library System (BCCLS) (http://www.bccls.org) is a system with 73 libraries in four counties of New Jersey with the major difference between BCCLS and WYLD is that all their members are public libraries. They gave us CD-ROMs with manuals, presentations, and tutorials (brief training videos). Their GL3.0 upgrade took about 8 hours including the pre-upgrade backup; software install; rebuilds; and post-upgrade backup. After the upgrade, we must rebuild the Authority Index and Thesaurus BUT the Authority Thesaurus rebuild takes much less time because Correct Authority Thesauri no longer exists. The training materials will require much editing. Also, they mandated use of the Java client with their libraries and of course, we're focusing on the C client for the time being.
Some key enhancements in GL 3.0
Barcode validation
Unicorn now supports all 100+ formats supported by DRA Classic. The Barcode Verify wizard identifies which validation schemes match your barcodes. For example, with barcode validation the system will be able to make a distinction between item and patron barcodes and will not let the user enter a patron barcode for an item or vice versa. When barcode validation is configured formal validation will be done any time a barcode (patron or item) is typed by hand or via scanning throughout the WorkFlows client.
Ability to Set Expiration and Suspension Dates When Initially Placing Holds
When library users initially place their own holds in the OPAC, they may now specify a date on which the hold expires. They may also enter a range of dates for which to suspend the hold, so that if the item becomes available during the suspension dates, the user will be skipped without losing his place in the hold queue
Full User Birth Date Field
The birth year field has been expanded to include a user's entire birth date. The full birth date is being added to Unicorn to provide libraries with the ability to retain accurate and updated patron records that comply with today's privacy standards. The birth date field will be available for display in the Display User wizard and as a selection option in various user reports. Sirsi will also provide the ability for sites to convert their existing birth date information to the new field
Circulation Notices in Batch Report
A new report has been added to the Unicorn GL3.0 release that will allow libraries to create one notice for holds, bills, and overdues that can be sent by email. This report is very similar to the Circulation Mailer report except that this report allows you to send the notice by email. The report also has some additional output options that are not available in the Circulation Mailer report. For example, you can configure headers for each notice type (bills, holds, overdues) and create a footer.
Call Number, Item, and MARC Holding Maintenance Library Attribute
Three new Library policy attributes will allow restriction of maintenance access to the Unicorn call number, item, and MARC holding records. Currently, the Unicorn Library policy provides display and maintenance attributes for acquisitions, bill, circulation, serials and user records. These attributes allow system administrators to restrict the various display and maintenance activities for these record types to the appropriate staff. Three new attributes - Call Number Maintenance Libraries, Item Maintenance Libraries, and MARC Holdings Maintenance Libraries - will allow Unicorn administrators to restrict add, edit and remove access to these record types. For example, a staff member may be allowed to add and edit an item record for Library A, but not be allowed to add or edit a call number record for Library B.
Spine and Pocket Labels
An improved ability to create spine and pocket labels using Item IDs - a far more practical approach to label making.
The future GL3.1 upgrade
The second upgrade we face for GL 3.1 won't happen soon. It is still being tested and is not in general release. It should be available in several months. It will NOT require dropping the use of the C client.
Meeting of Sirsi Consortia Customers
Dale Collum and I represented the WYLD Network at the second annual meeting of Sirsi (not Dynix) consortia customers late September 2005 in Des Plaines, IL. Over 20 consortia were represented including the huge InfoOhio school network , the Montana Share Catalog, and consortia from Connecticut, Delaware, Illinois, Massachusetts, Michigan, New Jersey, New York, Nova Scotia, Ohio, Wisconsin and Wyoming.
We revised issues and concerns from a document submitted to Sirsi last year. The second day we shared them directly with Sirsi representatives that included their Chief Sales Officer, the National Accounts manager, the VP of Implementation Services, the VP of Technical Product Management, Senior Client Care Account Manager and so on. The consortia group has developed another issues document to be delivered to Sirsi by the beginning of November. Sirsi pledged a detailed response by mid-December of this year. In my opinion it is one of the most important opportunities we have for keeping consortia issues in front of Sirsi senior management.
Sirsi Consortia Enhancements and Voting
I will be busy the next couple of weeks consortia enhancement suggestions on the Consortia Enhancement Forum and turning them into voting opportunities for Sirsi customers. These are available via the Client Care portion of the SirsiDynix website. If you receive Sirsi Consortia emails, you do not need to vote. Our Network gets only one vote as we are one customer of Sirsi. With new WYLD leadership we can look at a process for how this vote can be more inclusive of membership without it being to cumbersome. Some of you may remember Crystal trying to develop such a process. After some consultation I tend to vote close to the deadline so that we can support the leading enhancements that most benefit WYLD interests.
Crystal Reports training
Marc recently completed Crystal Reports training. We bought it with the Fretwell-Downing's VDX/ZPORTAL products. We will now be able to have fuller data sets with more granular scoping for our resource sharing efforts and subsequently better planning and preparation for improved services.
Shaping the Future of the WYLD Network
Lesley and Brian MET with Network President (Dale) and Vice-President (Paul) on November 3 in Rock Springs. Dale has this as a separate item on the Board agenda. It was a meeting to help us get on the same page about major WYLD issues and was very helpful for the planning of WYLD's future.
Minimum System Requirements for WYLD/Unicorn using staff workstations
This WYLD web page was updated at the request of your Network President, Dale Collum. See http://will.state.wy.us/wyld/docs/requirements.html
WYLD Training
Linking and preparation for next upgrades
We believe that emphasis should be on linking and not cataloging. There are far too many linking errors to WYLD records. This is also evident in the 9xx ordering process in Acquisitions. The problem is not with the 9xx ordering or the cataloging functions of Unicorn. It is us humans. With GL 3.0 upgrade there will be a way to control some of this. Bobbi and Trish are preparing a pilot training covering this issue at the next Region 5 meeting on Dec. 13. Council Chair Paul Holland has recommended that this be done with the other five regions. The WYLD Office plans on doing so.
There is an issue that libraries hiring people to do cataloging bear the burden of hiring qualified individuals to do so. It should not be the burden of the WYLD Office. The WYLD training focus will be more in the procedures and intricacies of properly linking and editing of records already in WYLD or being added to WYLD. With the use of the newly revised and accepted database guidelines and the Training Committee's Skills Checklists especially for acquisitions, cataloging and serials at: http://will.state.wy.us/wyld/network/committees/training/training.cfm we have excellent guides in place. Now we need to strive for consistent application of these helps.
One further way to help each other is to make sure all staff doing this kind of linking and editing are subscribed to the "techser" email distribution elist: http://will.state.wy.us/wyld/email/lists.cfm
I would like to recommend that the Training Committee make this the first of the minimum requirements for each of the Skills Checklists. Something like "know how and where to subscribe to the WYLD elists relevant to one's job including All, WYLDNEWS, Regional affiliation, and the subject area(s) covering that person's responsibilities.
Perhaps other dollars can be found to support regional or multi-regional contracts with BCR and the like for more cataloging training.
Director's Station training strategy
We are introducing Director's Station (DS) to directors and their key staff through the use of email and our online interactive web software. Emails will go to the Directors' public email list. If you want key staff involved, make sure they are subscribed to this elist.
With the WebDemo online interactive web software, we can walk trainees through various screens and procedures. This will give an introduction to training in this environment while director and key staff remain at their desk or in a shared learning space like a meeting room with computer, screen and LCD projector. A browser with "Pop-ups allowed" and a phone with a speaker will also be needed.
We believe that a group of 3 - 5 sites at one time should be the target for these sessions. I would like to have our next session with at least Network President (Dale), Network VP (Paul), and Debbie Iverson. All have had a long-time interest in this product. After that we're open to your suggestions on when you or a group of you would like to try the WebDemo training. Both Karen Lange and Susan Simpson who were involved in a pilot training said a mixed group of library types is good (academic and/or public and/or special and/or K12).
We, in this case, mean Marc, Desiree and/or I. All WYLD Office staff has been introduced to DS but Marc and Des have the greatest proficiency in its use.
One other thing I would like to suggest or develop is peer support. This is a different kind of application when compared to all the Sirsi applications we use. The trainees are a special subset of the WYLD user community. Is there a way we can support each other via the directors' elist? A director might like an example shared by another and may wish to work directly with that person in how they did it. In other cases, others will be able to share gems of info that are useful to your Boards, yourself, grant efforts, or other endeavors. Let's challenge ourselves to learn, share and grow in the use of Director's Station.
Commendations to Teton County for their efforts in webcasting MPLA/WLA 2005
I congratulate Teton County's efforts to bring the WLA/MPLA conference to folks in their homes, schools, offices and libraries. It took many months of preparation and effort. A generous anonymous donor and the commitment of TCL leadership went a long way. Volunteers kept the cameras going in proper fashion. There were a couple of sessions lost but most are available over the next 30 days. Take a look: http://tclib.org/mpla/
Roy Tennant's key note on Thursday and Stephen Abram's Millenial Users sessions on Friday afternoon are among the highlights. Due to technical difficulties the Ocober 14 presentations of Abram's Google, Inc. and Wilson's Understanding Portals are not available. I know a lot of folks were disappointed with the missing Google, Inc. presentation. Good news: Mr. Abram made an impact. His PowerPoint of that should be available soon.
Check out the webcasts and give feedback at: http://tclib.org/mpla/contact.html Don't forget to check out the conference blog at: http://mplawla2005.blogspot.com
Stephen Abram is the SirsiDynix, Vice President of Innovation. Two key sites for following his work are at: http://www.sirsi.com/Resources/abram_articles.html and http://stephenslighthouse.sirsi.com
We were very fortunate to have heard such library bellwether folks as Roy and Stephen.