Mission
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.
Roster
- 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
Update: 07-08-09
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.
AGENDA FOR 1ST HOLDS WORKING GROUP MEETING
11.11.08 & 11.12.08 — 10am-12p
- Establish mission
- Go over how Holds actually works (new information from Equinox)
ACTION ITEMS BEFORE NEXT MEETING
- Disseminate information
- Confirm process
FUTURE ACTION ITEMS
- Consensus on how Holds actually works
- Chart how Holds should work
- Develop list of prioritized requirements
- Categorize requirements:
- Process
- Policy
- Software development
- Ask Equinox for timeline for development
Holds Working Group Meetings 11.11.08 & 11.12.08
ROSTER OF ATTENDEES
George Tuttle, Laurie Eubanks, Shae Tetterton, Julie Walker, Jason Etheridge, Mary Hardy, Nel Baierl
AGENDA
Establish mission
Go over how Holds actually works (new information from Equinox)
ACTION ITEMS BEFORE NEXT MEETING
- Emily – put out notes , archived chat and updated docs on pines site for use by working group. Schedule next meeting.
- All – review mission statement and post edits, suggestions to forums:http://forums.georgialibraries.org/
- PINES library folks: vet these meeting materials with directors.. Are allocation expectations reasonable and realistic?
- All – look over the How Holds Works diagram and vet with colleagues. See Testing Checklist Below. Verify findings on forums board.
FUTURE ACTION ITEMS
- Consensus on how Holds actually works
- Chart how Holds should work
- Develop list of prioritized requirements
- Categorize requirements:
- Process
- Policy
- Software development
- Ask Equinox for timeline for development
POSSIBLE MISSION FOR GROUP:
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.
Meeting Notes
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.
