Identifying Ideal Processes in Evergreen

For the past month, we've been meeting with library staff to discuss the best way to complete tasks in the new system. Each working group has had representation from library staff in each of the three participating networks as well as network staff. Most groups started off with an in-person meeting, although there is one group that has been doing all of there work online. They are all continuing their work online so that we can quickly move forward with identifying development needs for Evergreen.

These working groups have been developing use cases, a method often used in systems development to describe a system’s behavior and how it should respond to requests from a user. Why are we starting with an exploration of processes? Many of our current processes are driven by the systems we are using. In some cases, the process may just be a workaround to get the system to do what we want it to do. We don't just want to replicate those workarounds when we consider development for Evergreen. We want to consider the most efficient way to complete a particular task in the system.

When your library goes live with Evergreen, it won't necessarily be following the processes that have been developed by these working groups. Instead, we will look at these processes and compare them to the way Evergreen completes tasks. This gap analysis should highlight different areas where our libraries would benefit from further development.

As the groups have been developing the use cases, I have been posting them to the Use Case Group Workspace on the MassLNC site. We have also been discussing the processes in the MassLNC forums. Feel free to look around to see how this work has been developing.