Establish a baseline on how Holds actually operated in the existing version of Evergreen. Discern the difference between process, policy and software solutions.
Document optimal Holds functionality within a future Evergreen release and develop a list of requirements.
Become the Holds testing group, through which all new Holds development would be filtered.
Mary Hardy -- Conyers/Rockdale
George Tuttle -- Piedmont Regional
Susan Cooley -- Rome/Floyd County
Jennifer Durham -- Statesboro Regional
Laurie Eubanks -- West Georgia Regional
Dusty Gres -- Ohoopee Regional
Marsha Christy --Houston County
Mark Cole -- Satilla Regional
Shae Tetterton -- Equinox
Jason Etheridge -- Equinox
Chris Sharp -- PINES
Emily Almond -- PINES Team Lead
Holds Working Group meeting at end of July to put forth a specific recommendation as to how the Holds logic within Evergreen should change to benefit PINES patrons.
Since the group first formed, we were able to
discern quickly that there was a break between understanding of software and
following of process.
In December of 08, we removed the cap on the Holds pull list and implemented a Holds Amnesty, during which libraries would have a chance to catch up.
The results were as follows:
December 2008
- 4500 Unfilled Holds
January 2009
- 890 Unfilled Holds
March 2009 -
20 Unfilled Holds
...
Since March, we've been able to rule out process and workflows and concentrate on how the Holds module actually works and start to formulate a recommendation for how we would actually like it to work. (See updated diagrams below.)
In the next meeting, the working group will finalize a recommendation to be approved by the Executive Committee for a change to the internal logic of the Evergreen holds module.
11.11.08 & 11.12.08 -- 10am-12p
ACTION ITEMS BEFORE NEXT MEETING
FUTURE ACTION ITEMS
| Attachment | Size |
|---|---|
| how holds works updated 050509.pdf | 34.91 KB |
| how holds works updated 070709.pdf | 57.72 KB |