Appendix C: Complete List of User Stories
In the list below, each user story is noted as either a content-related or functionality-related requirement. However, some stories, due to their nature, require a specific piece of website functionality along with custom content specific to one or more user groups.
1. ALL USERS
a. Website users can browse through all of the website content, organized by categories. (function)
b. Website users can use a search field to search all of the content on the website. (function)
c. Website users can sign up to get email notifications about certain news items in the Evergreen community. (function)
d. Website users can complete an optional profile describing themselves, their organization, and their organization's use of Evergreen. This will allow website users to find and contact other users with similar background, experience, geographical area, or other shared information. (function)
e. Website users can add resources, including file attachments and/or third-party URLs, to an online resource directory available to other users. (function)
f. Users can find updated information on connecting with EG community via IRC, mailing lists, and other formats. (content)
g. Users can learn about news and developments in the EG community. (content)
2. ADMINISTRATORS
a. Administrators can participate in an online forum to ask questions and share best practices with other Administrators. (function)
b. Administrators can participate in a special online forum (called "the feature percolator") where possible new Evergreen features are brainstormed and discussed before optionally being submitted to the official Launchpad system. (function)
c. Administrators on the website can easily reach the Bug Reporting feature on Launchpad. (function)
3. DEVELOPERS
a. Developers can maintain the official project documentation in a repository apart from the community EG resource/contribution library. (function)
b. Developers can participate in the Administrator "feature percolator" discussion forum mentioned above as well as view the forums in detail. (function)
4. DOCUMENTERS
a. Documentors can maintain the official project documentation in a repository apart from the community EG resource/contribution library. (function)
5. CONSULTANTS
a. Consultants can participate in the Administrator "feature percolator" discussion forum mentioned above as well as view the forums in detail. (function)
6. GOVERNANCE
a. Governance users can easily add content to the website as needed. (function)
b. Governance users can easily generate a report of website users that have completed the user or organizational profiles mentioned above. (function)
7. WEBMASTERS
a. Webmasters can easily manage and update the website, including the ability to delegate permissions to other users. (function)
b. Webmasters can easily identify and purge outdated content. (function)
8. POTENTIALS
a. Potentials can view a "one-pager" offering a high-level overview of both EG software and the EG community. (content)
b. Potentials can view contextual background information on Open Source Software. (content)
c. Potentials are directed to visit a "Considering Evergreen?" web page which offers a guided introduction to EG resources, created by EG community experts. This page presents links to decision-making information in a logical order, aimed at the potential implementer. (content)
d. Potentials can browse or search a categorized collection of resources aimed at potential implementers. (content)
e. Potentials can submit a question via webform which is emailed to EG community members/mentors for answering. (function)
f. Potentials are directed to a third-party demo "sandbox" implementation of Evergreen. (content)
g. Potentials can search for an EG Service Provider based on certain criteria. (functionality/content)
h. Potentials can search for existing EG libraries based on certain criteria. (functionality/content)
i. Potentials can search for individuals in the EG Community based on certain criteria. (functionality/content)
9. SKEPTICS
a. Skeptics can view content created to persuade them why open source is a good idea. (content)
b. Skeptics can view content intended to teach about the differences between Evergreen and Koha. (content)
c. Skeptics can access a list of existing Evergreen users that have volunteered to be contacted to discuss their satisfaction with Evergreen. (function)
d. Skeptics can view curated case studies of successful Evergreen migration and implementation projects. (content)
10. MIGRATION
a. Migration-users can access (browse/search) a hierarchically-categorized collection of resources aimed at libraries performing a migration. (content)
b. Migration-users seeking help for problems encountered during migration are encouraged to join and participate in the general mailing list for assistance. (content)
11. STANDALONE
a. Standalone users can access a page of curated resources specifically tailored for standalone Evergreen libraries, with a focus on issues specific to that group. (content)
2. Standalone users can find and contact other standalone libraries that have adopted Evergreen. (functionality)
12. EXTENDERS and 13. INSTALLERS (total overlap of requirements)
a. Users can find information on Evergreen software repositories and how to use them. (content)
b. Users can download test marc, copy, and user data. (content)
c. Users are easily directed to on-site and off-site (Launchpad) discussion, specs, or documentation describing features. (content)
d. Users are easily directed to DIG-maintained information on how to build, rebuild, and update Evergreen. (content)
e. Users are easily directed to on-site and off-site information, discussion, and examples of ways to configure Evergreen. (content)
14. TRANSLATORS
a. Translators can access a high-level overview of project translation efforts describing people, organizations, teams, and processes involved. (content)
15. ACCESSIBILITY
a. Accessibility users can access a high-level overview of project accessibility efforts describing people, organizations, teams, and processes involved.