This is an old revision of the document!
DRAFT Evergreen Community Website: Requirements Analysis and Recommendations DRAFT
I. Executive Summary
Evergreen is an open source software application that provides a full spectrum of library management functionality - such as patron administration and circulation management - for libraries and library consortia around the world. Like many successful open source software projects, Evergreen is used, developed, and supported by a large virtual community that includes individuals, nonprofit organizations, and commercial vendors. Evergreen community leaders are currently working to create a formal governance and management structure for the project to ensure that the community continues to grow and collaborate effectively.
The Evergreen Web Planning Team was chartered by the emerging Evergreen Communications Committee to:
1) gather input about the Evergreen community's online/website requirements, and,
2) develop a plan for a flexible, effective, and user-friendly platform that will satisfy the community's growing online/website requirements.
This document is the result of several months of strategic planning, requirements analysis, and community discussion.
II. History of Web Planning Process
III. Strategic Goals of Evergreen Web Presence
IV. The Evergreen Online Community
V. Defining Our Users and Their Requirements
1. People & Process
EG Advocate role - informal vs. formal? Lead, teach, share, foster,
Website Publishing Committee (Process & Policy)
Netiquette policy Recognize volunteers
Marketing / Outreach / Awareness Committee
Promote growth in existing user bases Promote growth in new user bases e.g., EG has low penetration in K12 sector. Outreach committee can embark on focused campaign to reach out to K12 sector and promote EG use, answer questions, etc.
Publication schedules
Encourage widespread participation
- lower and remove barriers whenever possible
- encourage community spirit and intangible incentivization
Accessibility Advocate
Privacy Policy! – the archive change incident
2. Technical
XXX. Appendices
Appendix B: Survey Results (Aggregate)
* See attachment "egwebsite_surveysummary_03172011.pdf"
Appendix C: Complete list of identified user stories
Appendix D: