2013 Evergreen Hack-A-Way

The 2013 Evergreen Hack-A-Way is being hosted at Calvin College, Grand Rapids, MI from September 17-19.

Working documents

The following documents reflect notes or working documents written during the Hack-A-Way:

We will adjust as we go along.

Location: Meeter Center Lecture Hall, Hekman Library (HL 325)

9:00am - 12:00pm: Group Discussion
- 9:00am: Welcome and Introductions
- 9:30am: Staff Client, Future Of
  - Continuation of future_of_staff_client special dev meeting (http://evergreen-ils.org/dokuwiki/doku.php?id=dev:meetings:future_of_staff_client)
  - Establish interface design documents / standards / best practices
- 11:00am: Establish Working Groups
12:00pm - 1:00pm: Lunch - Campus Commons
1:00pm - 6:00pm: Working Groups
- 1:00pm: Hacking
- 3:45pm: Break (sponsored by Equinox)
- 4:15pm: Hacking II
6:00pm: Break for evening - Dinner around town, preferably with Working Group

9:00am - 12:00pm: Group Discussion
- 9:00am: Working Group Reports
- 9:45am: Evergreen 2.6
  - Expected/desired features
  - Duties of RM (including evaluation of 2.5 process)
- 10:30am: Other topics ???
12:00pm - 1:00pm: Lunch - Campus Commons
1:00pm - 6:00pm: Working Groups
- 1:00pm: Hacking
- 3:45pm: Break (sponsored by Equinox)
- 4:15pm: Hacking II
6:00pm: Break for evening
6:30pm: Dinner - Prince Conference Center Hickory Room (sponsored by Equinox)

9:00am - 12:00pm: Working Groups - Hacking
12:00pm - 1:00pm: Lunch - Campus Commons
1:00pm - 3:00pm: Group Discussion (early due to early exiters)
- 1:30pm: Working Group Reports
- 2:00pm: Event Evaluation
3:00pm - 6:00pm: Working Groups
- 3:00pm: Hacking II
- 3:45pm: Break (sponsored by Equinox)
- 4:15pm: Hacking III
6:00pm: Event ends

NCIP Responder
Mobile Catalog
Staff Client, Future Of
- Any chance for everyone to sit in a room and talk is good.
- Continuing from future_of_staff_client
- Establish interface design documents / standards
- Git branch: random/collab/berick/web-staff-ui-experiments
Memory leaks in staff client
Revamp MARC export tools with emphasis on speed improvements (possibly doing more in-database?)
Evergreen 2.6
- Role of RM (including evaluation of 2.5 process)
- Expected/desired features
Search - identify and prioritize bottlenecks and behavior quirks
Serials - testing/merging stuff for 2.5 and looking at post 2.5 projects
Write some QA tests