Location: Member Products : I-Share : opac : WebVoyage Developers' Responsibilities
I-Share Library WebVoyage Developers' Responsibilities
WORKING DRAFT

April 22, 2003; revised March 2, 2007.

Members of the CARLI community who receive authorization to edit I-Share WebVoyage configuration files must agree to the following:

  • I am responsible for testing that my modified WebVoyage files work as expected with my production database.

  • I will respect the WebVoyage “staging” process.

  • I will stay informed about and adhere to the consortium's WebVoyage Customization Guidelines to the best of my ability. If I discover my library’s customization desires are in conflict with the current Guidelines I will negotiate with the I-Share Users' Group's OPAC Team to learn whether the Guidelines can be changed or what other options I might have to accomplish my library’s service goals.

  • I will remain on the CARLI WebVoyage Developers email distribution list (wvdev@carli.illinois. edu) for at least as long as I am actively engaged in WebVoyage customization work, and will use this list to communicate with the I-Share Users' Group's OPAC Team regarding general customization plans at my institution.

  • I will remember that the WebVoyage Developers email distribution list is also available to me to post questions, comments, or suggestions to the OPAC Team and other WebVoyage developers in the CARLI consortium.

  • Files in the development area will be backed up by CARLI Office staff once a week. Additional back-ups of files under revision are my responsibility. I may at any time ask the CARLI Office for a “fresh” copy of the I-Share local default WebVoyage, in its entirety; or for a restored copy of my institution’s WebVoyage as it currently exists on the production servers, in its entirety. CARLI Data Services staff will try to refresh or restore WebVoyage development files within two working days.

  • I will not edit WebVoyage files in a Windows text editor, or any text editor that is incapable of saving files with Unix-appropriate line feeds and carriage returns.

  • I understand that I am responsible for maintaining local documentation on my institution's variations from the I-Share local default WebVoyage.

  • I have a choice regarding modest changes to my files when the CARLI Office rolls out a new version of the I-Share default WebVoyage: I can accept a new version of the I-Share default WebVoyage in my development area and can re-make, on my own, the local changes that need to be re-made; or, I can document for CARLI Office staff what institution-specific changes I want the CARLI Office to make in my institution’s instance of WebVoyage, in as timely a fashion as they can manage.

  • I understand that if I make extensive changes to my files that I will be responsible for re-making those changes each time the CARLI Office rolls out a new version of the I-Share default WebVoyage. CARLI Data Services staff will be able to supply me with a text file listing the differences between my files and the new I-Share default.

  • I am responsible for testing my modified WebVoyage against interim upgrades or patches to the Ex Libris software (which do not require the wholesale re-editing of WebVoyage configuration files). I understand that I will generally have one workweek in which to do this testing. I understand that if my modified WebVoyage files produce a problem in the upgraded environment that is not replicable in the I-Share default WebVoyage that I can choose to live with the problem or to accept the I-Share default WebVoyage.

  • I am responsible for testing my modified WebVoyage with a variety of web browsers.

  • I will not incorporate image or text files into my WebVoyage interface for which I do not have appropriate permissions.

  • I will follow my own institution’s accessibility guidelines for web development, as well as the Section 508 of the Rehabilitation Act, to the extent possible in WebVoyage. (More information about Section 508 of the Rehabilitation Act is available at http://www.access-board.gov/ 508.htm.)

  • In the event that I leave my institution or otherwise cease to be one of the people actively engaged in WebVoyage customization work, I understand that my account will be suspended, but that the files I have edited will not disappear. If my institution’s WebVoyage is highly customized, my institution will need to designate and arrange for the training of a new person to maintain the customizations.

Search



Featured Links

HTML Document Voyager Upgrade

HTML Document Effect of OCLC Number Changes in the I-Share Environment

HTML Document I-Share Resource Sharing Code

HTML Document CARLI Privacy Policy

PDF Document Using OCLC for Batch Loading Records

HTML Document System Documentation

HTML Document Events and News

HTML Document New 2008 I-Share Participating Libraries Resources

HTML Document Information for ILLINET Libraries