Agenda:

• Broader Primo beta testing plan.
• Plan for Primo User Interface development for beta test.
• What to call Primo for beta test.
• Current status of initial configuration of our instance of Primo.

Notes:

• Jody began the meeting with an update on the February and March work plans for the Primo beta test from Ex Libris. He discussed how changes to the time line require some adjustments to our internal beta test plans. He will continue working with Ex Libris to minimize the impact on our plans.
• After a good deal of discussion, the group decided that two new project teams should be developed for the beta test:
  • One team would work with focus groups of end users. This team would develop test scenarios modeled after UMN's usability studies and recruit end users for the focus groups. They would also be able to explain to focus groups that the service is still being developed and, for example, might not include a full load of data at the time of the tests. This team could begin work early in March, even though we will not have all our data in Primo by this time. Jody agreed to develop the charge for this project team.
  • A second team would do "comparison testing." This team would compare the results of searches in Acorn to searches with Primo's "acorn" scope, for example. It should also compare results of searches in the "remote" (meta-searching) tab of Primo with the native interfaces of individual databases. This team may need to wait until after we have a full load of our data in Primo to begin work, at least for the comparison with Acorn. Flo agreed to develop the charge for this team.
• Development of the UI: again, after considerable discussion, the group decided that we should do minimal development of the UI for the beta test. The preference is to remove as much of the distracting information (information that is included on other production library sites, e.g., "library news") from the interface as possible, so users could focus on testing the search, discovery, and delivery capabilities of Primo. The DLSC asked Suellen to begin work, with input and help from the Heard web site management group, on the UI configuration to accomplish this.
• Naming Primo for the beta test: we are not ready to develop a permanent name for this service. The committee decided that the temporary name should NOT be "Primo." Rather, it should be a name that is obviously temporary (e.g., "Project X"). The committee members will provide suggestions by the next meeting.
• Jody reported on the current status of the initial configuration of Primo. He also reported that we have established a discussion board in the OAK Primo course that will be used to report problems during the beta test.
• Roberta agreed to talk with Syndetics about the potential for a trial use of their service for the beta test.