Proposal for FCLA Web OPAC Development

Web OPAC Development Process

1. Prior to STP for the P1LS, there will be no major variations from the screen layouts recommended by the SUL/CC OPAC Task Force and included in the FCLA prototype. NOTE: We’re not yet sure what CCLA will be doing for its initial interface, but FCLA is committed to following the Joint Task Force recommendations for its initial ALEPH Web OPAC. 2. As with WebLUIS, each library will be able to design the header and footer areas of their catalog. Some alteration of elements in the style sheet affecting screen displays (e.g. font color) will also be possible locally. 3. The SUL OPAC Subcommittee will be asked to assist in refinement of the interface by:  Systematically testing searching, navigation, and functionality.  Identifying problematic displays.  Refining text used (e.g. in drop-down menus) and developing examples (content of I-Ball screens, etc.)  Identifying display improvements that may be possible by changes to the style sheet. 4. The SUL OPAC Subcommittee has a listserv (SUSOPAC-L) on which some “business” discussions will occur. 5. A separate listserv (LIBOPAC-L) has been set up to continue the function of WEBLUIS-L in the new ALEPH Web OPAC environment (i.e. for broader dissemination and discussion of ideas). All WEBLUIS-L subscribers (including all PSPC members) will be switched to LIBOPAC-L automatically, and opportunities for others to join this listserv will be advertised throughout the SUL. Comments will be encouraged from all interested staff in the SUL. 6. If issues arise that require decisions…  The feedback from institutions to be most immediately affected will be given priority. So P1LS OPAC Subcommittee members will be expected to participate at a different level this year, and their feedback will be given greater weight.  P2LS and P3LS will then be included at that level as they are closer to migration.  So while feedback will always be solicited broadly, there may be some situations in which decisions may be made only by those institutions that will be most immediately affected. 7. As was the case with WebLUIS, FCLA is committed to having the Web OPAC interface continue to evolve as needed.  For example, as the P1LS gain experience with the Web OPAC after STP, some changes may be deemed necessary to make ASAP.  As P2LS and P3LS each get closer to STP, their added input may result in further changes as well. For example, a new “release” of the FCLA Web OPAC might be timed to accompany STP in the P2LS; and there might be another “release” at the time of STP in the P3LS.  The extent of changes to be made for any “release” may be influenced by the ongoing development of the Community Colleges Web OPAC (and continued discussions with them about the desired consistency of the separate SUL and CC Web OPACS as we move closer toward the eventual Giant Union Catalog (GUC)). Available Ex Libris enhancements may also need to be considered.  Unlike with WebLUIS development, adding functionality to the Web OPAC interface will almost certainly come only as this is developed by Ex Libris. While changes in “presentation” on screens can be considered, adding system functionality is probably not going to be feasible without working through the vendor and/or NAAUG enhancement process.  As was the case with WebLUIS development, FCLA will always need to assess the potential affect of any desired change before agreeing to implement it. It will be important to minimize the customization due to the effort that may be required to modify the Web OPAC infrastructure when Ex Libris introduces new versions of ALEPH in the future.

10/31/2003 (Rich)