Thank you, Paul!
Although we are committed to going with Evergreen (signed, sealed, and in the process of delivery—go live May 28), we are still doing the “wait a minute… circ modifier is what again??” dance. There is excellent training documentation available, for which I am most grateful to the rest of the community. As we work our way through the migration, we’re currently trying to figure out the hierarchy of user permissions and how those work. At best, I am looking back and forth between the Pines demo (which is a few versions behind) and our test box permissions (which were kinda/sorta delivered but aren’t making sense). Without some definition on how those are developed, setting up our staff users has been a challenge. By the time the conference comes around, I’m sure I’ll have a lengthy list of things I’d have liked to have known how to do… I am looking forward to the documentation sessions. Preparing for migration and migration processes from the staff users’ perspectives are my key interests. Looking forward to continuing this conversation, Catherine. -- Catherine Buck Morgan Director, Division of Innovation, Technology & Library Services South Carolina State Library POB 11469, 1500 Senate Street, Columbia, SC 29211 Phone: 803-734-8651 | Fax: 803-734-4757 [email protected] <mailto:[email protected]> www.statelibrary.sc.gov <http://www.statelibrary.sc.gov> The South Carolina State Library is a national model for innovation, collaboration, leadership and effectiveness. It is the keystone in South Carolina’s intellectual landscape. From: [email protected] [mailto:[email protected]] On Behalf Of Paul Weiss Sent: Saturday, May 02, 2009 10:24 PM To: doc list Subject: [OPEN-ILS-DOCUMENTATION] Evergreen documentation issues Fellow documenteers - I'm with Sage Library System, a multi-type consortium of 70 mostly small libraries in eastern Oregon. Sage is in the process of testing out Evergreen with the hopes of implementing next year. In trying to do profiling for our test migration, I scoured the Evergreen and Equinox websites, but wasn't able to find basic information about data, rules, and other settings, which I assumed would be there, and which I believe I need in order to plan a successful migration to Evergreen. I looked through existing documentation, which seems mostly to be either deeply technical, or procedural/how-to. Equinox staff have been quite willing to answer my questions via phone, which I appreciate. Although transmitting information verbally gets me information I need to know, it seems really inefficient. So last month I called Karen Schneider, who I had seen was getting involved in documentation efforts, and we discussed Evergreen documentation needs. After talking with her, I am quite excited about doing documentation prioritizing and planning at the upcoming Evergreen conference. At Karen's suggestion, I've written up some of my experiences with and thoughts about Evergreen documentation to help us all move forward: see the attachment. Certainly much of the document is not new, but I wanted to get it all down together, in an organized fashion. I know that a lot of open-source projects suffer similarly, but we're library folk—we can do better! Although tempting, it is unfair to expect solely Equinox or GPLS to improve the Evergreen documentation situation (although I certainly hope they will continue to be major contributors); it is a problem that all of us in the Evergreen community need to come together to resolve. Hope to see many of you in Athens later this month! Paul Paul J. Weiss Project Coordinator Sage Library System [email protected]
_______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
