4/25/2005
1. Group process: *We agreed that the SFX subgroup, normally composed of Jennifer, Rich,
Millicent, Graham, and Tracy, will meet irregularly with WAG [Web Advisory
Group, chaired by Nicole] to work on specific current SFX operational
issues, and getting version 3.0 of SFX to do what version 2 does for us
now. (Conceptual and planning aspects of SFX services in light of Verde
will continue to be handled by the SFX-Verde group.) *We briefly reviewed Tracy and Millicent's notes on Barton as an SFX source and agreed to defer discussion to the meeting on 5/2, or, more likely, 5/16. 2. Big Picture Vision Process 3. Planning and Timeline We agreed that we are near the point where it makes sense to reduce our list of implementation options and focus on the details of one scenario. We are currently conceiving of this one scenario in this way:
Notes about this scenario: For Databases, Barton would also be a tool for discovery and known item access, but in this scenario Barton is conceived of as more for known item seeking than for discovery, since making Barton into the kind of discovery tool we want would take too much work to configure, even to work as well as MetaLib does. For Ejournals, There are still three possibilities under consideration: SFX tools, Barton, and Metalib. The ways we might best use Barton and Metalib for ejournals will need more analysis and discussion. Metalib might not necessarily be the main tool for discovering or seeking known items in the universe of journals, but it might play some role. Barton's potential role is yet to be discussed in any depth. An option for discovery we have set aside for now would be to enhance Vera or create another homegrown tool. We felt it would be prohibitively labor-intensive both to develop and maintain so we have not included this idea in the main option we are considering. Next steps: -We will further consider this idea and will discuss relevant usability testing (to help us determine the viability of the scenario we are outlining and the value of some features we could stand to lose) at the next meeting. |
|||||||||||||||
|
|