It was determined by several groups at the library more communication would be beneficial to dicuss the intracacies of the SUS OPAC enhancement process.

To create the group a discussion group steps had to be taken:

1. The Endeca implementation task force had completed its mission.

They had successfully completed an entire battery of usability tests whose conclusions directly guided the first implentation of the Endeca catalog.

They had led staff through a series of orientations and classes to prepare them for implementation

The task force was dissolved as completed

Future Usability testing has been brought up to the SUS level to garner a greate sense of comraderie between the different institutions, whereas we were working with FSU last time we are now also working with USF. Marilyn, Sara, and Jason currently serve as representatives on this group. The intention of the new team was to streamline the creation of the testing procedures. During the actual testing process supoprt will be recruited from the different areas to be studied.

The next phase of the transistion was the creation of the Endeca Discussion Group.

The first goal of the group is to ensure the communication about the development of any Endeca enhancements to all the necessary groups. Discussions about pertinent topics within those groups can occur and ideas can filter back up to the discussion group.

This is where the next goal of the group occurs which is to facilitate the implemtation of ideas and to inform the SUS-OPAC representatives who are charged with the heavy burden of representing all of UF, and to communicate to the state group our concerns and ideas

To create the group we studied the roster of the groups involved in Endeca enhancement,  and different members were pulled from several groups.

A wiki has been developed to facilitate the maturation of the discussion group to ensure that it stays on track and keeps its mission statement in focus.

A blog is in development with the aim of informing anyone interested about the different changes to Endeca.

Our current schedule is set to maximize our efforts by meeting the day before the state group meets so we can prepare for any topics that UF would like to set forth and to discuss the topics on the agenda to make sure that our reps are clear on what stance to take.

 

A. Communicating problems and their resolutions needs to be standardized.

 

*Please add your part of the puzzle here*

 

Currently the Patrons see 2 ways to report problems

Provide Comments

Report a Problem

 

Tom receives this information and sends Endeca problems to the RNG (is this how it is currently setup?)

 

PRB submitters

Rich

Leilani

Jason

Jimmie

Betsy

PRB reporting mechanism

Rich is going to see if there is a way to make this information more widely accessible

 

B. There should be a way to have informed and organized discussion concerning a wide ranging Endeca topics. This discussion should include issues concerning the Endeca production interface as well as FCLA's ideas for the future as represented on the test server. This could also serve as a mechansm for staff to make suggestions. In addition the local analysis of Endeca problems would benefit greatly from better availability to all staff of systematic and detailed information about how Endeca is intended to behave. Then we could more easily sort reports into categories like failures of the system to function as it should versus features to either accept or complain about. Due to the evolving nature of the system it might be a good idea for this "Endeca manual' to take the form of a secure wiki maintained by FCLA

 

C. There should be a mechanism to notify staff/patrons of changes to the Endeca production interface. To that end experimentation has begun with a blog.http://endecablog.blogspot.com/