webteam:user_stories:2011
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
webteam:user_stories:2011 [2011/01/31 18:36] – created - Recreated the page for proper url namespace as suggested. aatre | webteam:user_stories:2011 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | This page is for final refinement of the User Stories | + | ====== Criteria |
- | Evergreen Website | + | This page is for final refinement of the User Stories |
- | User stories are simple descriptions of features, written in plain English, that help us effectively plan a new website. | + | When planning a new website, it's important to make sure that we consider 1) all of the various groups of users that will be using the new website, as well as 2) all of the various tasks that each group of users will need to perform upon the site. We develop the website' |
- | User stories | + | This document contains user stories |
- | User stories can also be related to content on the website, such as specific documents, materials, multimedia, or pages. | + | ====== Defining our User Groups ======= |
- | This document contains user stories collected from the Evergreen | + | " |
- | ===== Functionality-related Requirements ===== | + | " |
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | " | ||
+ | |||
+ | ====== Functionality-related Requirements ====== | ||
+ | |||
+ | User stories can be related to website functionality, | ||
==== A. All Users ==== | ==== A. All Users ==== | ||
Line 27: | Line 57: | ||
5. Website users can add resources, including file attachments and/or third-party URLs, to an online resource directory available to other users. | 5. Website users can add resources, including file attachments and/or third-party URLs, to an online resource directory available to other users. | ||
- | ==== B. Evergreen Administrators | + | ==== B. Evergreen Administrators ==== |
1. Administrators can participate in an online forum to ask questions and share best practices with other Administrators. | 1. Administrators can participate in an online forum to ask questions and share best practices with other Administrators. | ||
Line 35: | Line 65: | ||
3. Administrators on the website can easily reach the Bug Reporting feature on Launchpad. | 3. Administrators on the website can easily reach the Bug Reporting feature on Launchpad. | ||
- | ==== C. Evergreen Developers | + | ==== C. Evergreen Developers, Documentors, and Consultants ==== |
1. Documentors and Developers can maintain the official project documentation in a repository apart from the community EG resource/ | 1. Documentors and Developers can maintain the official project documentation in a repository apart from the community EG resource/ | ||
Line 42: | Line 71: | ||
2. Developers and Consultants can participate in the Administrator " | 2. Developers and Consultants can participate in the Administrator " | ||
- | ==== D. Governance users are members of the Evergreen Governance Committee. | + | ==== D. Governance users ==== |
1. Governance users can easily add content to the website as needed. | 1. Governance users can easily add content to the website as needed. | ||
Line 48: | Line 77: | ||
2. Governance users can easily generate a report of website users that have completed the user or organizational profiles mentioned above. | 2. Governance users can easily generate a report of website users that have completed the user or organizational profiles mentioned above. | ||
- | ==== E. Webmasters | + | ==== E. Webmasters ==== |
1. Webmasters can easily manage and update the website, including the ability to delegate permissions to other users. | 1. Webmasters can easily manage and update the website, including the ability to delegate permissions to other users. | ||
Line 54: | Line 83: | ||
2. Webmasters can easily identify and purge outdated content. | 2. Webmasters can easily identify and purge outdated content. | ||
- | === Content-related Requirements === | + | ====== Content-related Requirements |
- | ==== A. User groups for the purpose of creating | + | User stories can also be related to content on the website, such as specific |
- | " | + | ==== A. Content requirements applicable to all users. ==== |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | " | + | |
- | + | ||
- | ==== B. Content requirements applicable to all users. ==== | + | |
1. Users can find updated information on connecting with EG community via IRC, mailing lists, and other formats. | 1. Users can find updated information on connecting with EG community via IRC, mailing lists, and other formats. | ||
Line 88: | Line 95: | ||
3. Users can browse or search a categorized collection of Evergreen-related resources. | 3. Users can browse or search a categorized collection of Evergreen-related resources. | ||
- | ==== C. Content requirements applicable to Potential users. ==== | + | ==== B. Content requirements applicable to Potential users. ==== |
1. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community. | 1. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community. | ||
Line 108: | Line 115: | ||
9. Users can search for individuals in the EG Community based on certain criteria. | 9. Users can search for individuals in the EG Community based on certain criteria. | ||
- | ==== D. Content requirements applicable to Migration users. ==== | + | ==== C. Content requirements applicable to Migration users. ==== |
1. User can access (browse/ | 1. User can access (browse/ | ||
Line 114: | Line 121: | ||
2. Users encountering problems during migration are encouraged to join and participate in the general mailing list for assistance. | 2. Users encountering problems during migration are encouraged to join and participate in the general mailing list for assistance. | ||
- | ==== E. Content requirements applicable to Consultant users. ==== | + | ==== D. Content requirements applicable to Consultant users. ==== |
1. Users can view a list of potential Evergreen related service providers and request that her organization be added to the list. | 1. Users can view a list of potential Evergreen related service providers and request that her organization be added to the list. | ||
Line 120: | Line 127: | ||
2. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community. | 2. Users can view a “one-pager” offering a high-level overview of both EG software and the EG community. | ||
- | ==== F. Content requirements applicable to Extender and Install users. ==== | + | ==== E. Content requirements applicable to Extender and Install users. ==== |
1. Users can find information on Evergreen software repositories and how to use them. | 1. Users can find information on Evergreen software repositories and how to use them. | ||
Line 132: | Line 139: | ||
5. Users are easily directed to on-site and off-site information, | 5. Users are easily directed to on-site and off-site information, | ||
- | ==== G. Content requirements applicable to Skeptic users. ==== | + | ==== F. Content requirements applicable to Skeptic users. ==== |
1. Users can find out why open source is a good idea. | 1. Users can find out why open source is a good idea. | ||
Line 142: | Line 149: | ||
4. Users can view curated case studies of successful Evergreen migration and implementation projects. | 4. Users can view curated case studies of successful Evergreen migration and implementation projects. | ||
- | ==== H. Content requirements applicable to Standalone users. ==== | + | ==== G. Content requirements applicable to Standalone users. ==== |
1. Users can find a page of resources for stand alone Evergreen libraries. | 1. Users can find a page of resources for stand alone Evergreen libraries. | ||
Line 148: | Line 155: | ||
2. Users can find and contact other stand alone libraries that have moved to Evergreen. | 2. Users can find and contact other stand alone libraries that have moved to Evergreen. | ||
- | ==== I. Miscellaneous content requirements ==== | + | ==== H. Miscellaneous content requirements ==== |
1. Developers, Documentors, | 1. Developers, Documentors, | ||
Line 162: | Line 169: | ||
6. Accessibility users can access a high-level overview of project accessibility efforts describing people, organizations, | 6. Accessibility users can access a high-level overview of project accessibility efforts describing people, organizations, | ||
+ | 7. LIS users can access a high-level overview of the Evergreen project organized in a way to help professors and students study it in an LIS or other academic context. | ||
---- | ---- | ||
+ | |||
===== Deprecated Files ===== | ===== Deprecated Files ===== | ||
Line 183: | Line 191: | ||
[[http:// | [[http:// | ||
- | |||
webteam/user_stories/2011.1296516982.txt.gz · Last modified: 2022/02/10 13:34 (external edit)