webteam:webplan:2011
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
webteam:webplan:2011 [2011/03/18 15:40] – created aatre | webteam:webplan:2011 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | I. Executive Summary | + | ===== 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. | 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. | ||
Line 11: | Line 14: | ||
This document is the result of several months of strategic planning, requirements analysis, and community discussion. | This document is the result of several months of strategic planning, requirements analysis, and community discussion. | ||
+ | [[webteam: | ||
- | II. History of Web Planning Process | + | [[webteam: |
- | + | ||
- | The Evergreen Web Planning Team began work in late summer 2010. The Team is composed of self-selected members of the Evergreen Communications Committee along with other interested members of the greater community, and was led by an external facilitator familiar with open source software communities and online collaboration platforms. | + | |
- | + | ||
- | From the beginning of the web planning process, Web Planning Team members were committed to transparency and inclusiveness. | + | |
- | + | ||
- | As noted below, the Web Planning Team utilized a planning technique borrowed from the agile software development community called "user stories." | + | |
- | + | ||
- | Although the initial - and primary - focus of the Web Planning Team was to consider a major website/ | + | |
- | + | ||
- | + | ||
- | III. Strategic Goals of Evergreen Web Presence | + | |
- | + | ||
- | (@@@TODO analysis and expansion of goals and requirements) | + | |
- | + | ||
- | Instead of diving into technical minutiae or discussions about specific software, the Team began with a high-level strategic planning exercise. | + | |
- | + | ||
- | Several high-level strategic goals were approved. | + | |
- | + | ||
- | A. Strategic Goal #1: Provide an easy-to-use, | + | |
- | + | ||
- | 1. Requirement: | + | |
- | + | ||
- | 2. Requirement: | + | |
- | + | ||
- | 3. Requirement: | + | |
- | + | ||
- | 4. Requirement: | + | |
- | + | ||
- | B. Strategic Goal #2: Support growth of a healthy developer community | + | |
- | + | ||
- | 1. Requirement: | + | |
- | + | ||
- | 2. Requirement: | + | |
- | + | ||
- | 3. Requirement: | + | |
- | + | ||
- | 4. Requirement: | + | |
- | + | ||
- | C. Strategic Goal #3: Facilitate development of multi-faceted support network for Evergreen users. | + | |
- | + | ||
- | 1. Requirement: | + | |
- | + | ||
- | 2. Requirement: | + | |
- | + | ||
- | 3. Requirement: | + | |
- | + | ||
- | D. Strategic Goal #4: Help encourage widespread adoption of Evergreen by the library community worldwide. | + | |
- | + | ||
- | 1. Requirement: | + | |
- | + | ||
- | 2. Requirement: | + | |
- | + | ||
- | + | ||
- | IV. The Evergreen Online Community | + | |
- | + | ||
- | A. Existing Community Properties: Websites and More | + | |
- | + | ||
- | The Evergreen community as a whole operates as a virtual community with the exception of occasional face-to-face meetings at conferences, | + | |
- | + | ||
- | 1. Website/ | + | |
- | + | ||
- | The current community website serves as a home for the Evergreen software itself as well as many of the project' | + | |
- | + | ||
- | Evergreen-ils.org (and its current mirror, open-ils.org) provide: | + | |
- | + | ||
- | a. Download and implementation information | + | |
- | b. Links to off-site demonstrations and development resources | + | |
- | c. Information about connecting with the Evergreen developer community | + | |
- | d. Developers' | + | |
- | e. Links to non-development-related project efforts such as the Governance Committee, Communications Committee, and Documentation Interest Group. | + | |
- | + | ||
- | 2. Website/ | + | |
- | + | ||
- | The primary collaboration platform for the Evergreen development community is a Launchpad instance. | + | |
- | + | ||
- | (@@@TODO Where do official docs live? DIG meeting space?) | + | |
- | + | ||
- | 3. Website/ | + | |
- | + | ||
- | Like many " | + | |
- | + | ||
- | 4. Website/ | + | |
- | + | ||
- | RSCEL, the Resource Sharing Cooperative of Evergreen Libraries, is a collaboration of various libraries and consortia using the Evergreen ILS. The RSCEL site offers resources for existing Evergreen users as well as information for potential users that are considering a migration to Evergreen for their library. | + | |
- | + | ||
- | a. Evergreen feature index and software comparison matrix | + | |
- | b. Evergreen feature request/ | + | |
- | c. KCLS Requirement Prioritization Application (beta) | + | |
- | d. Evergreen organization/ | + | |
- | e. Ability to be notified of new Evergreen-related content | + | |
- | f. Links to off-site demonstrations and development resources | + | |
- | + | ||
- | The RSCEL website is built using Drupal and maintained by The Galecia Group on behalf of the Evergreen community. | + | |
- | + | ||
- | 5. Email lists/ | + | |
- | + | ||
- | Georgia Public Library Services provides an email list server for use by the Evergreen community and various teams within the community. | + | |
- | + | ||
- | 6. IRC/ | + | |
- | + | ||
- | Many Evergreen developers and other community members are active in the Evergreen chat room on the Freenode Internet Relay Chat (IRC) service. | + | |
- | + | ||
- | B. Composition / Audience Analysis | + | |
- | + | ||
- | (@@@TODO: get stats, figures, run webalizer analysis for EG-ILS, get stats from RSCEL) | + | |
- | + | ||
- | (@@@TODO: get estimates from rest of Web Team) | + | |
- | + | ||
- | C. Defining User Groups, Roles, and User Stories | + | |
- | + | ||
- | User stories are simple descriptions of features, written in plain English, that help website developers effectively plan a new website with the website users in mind. Since different groups of website users have different requirements, | + | |
- | + | ||
- | Immediately after finalizing the strategic requirements listed above, the Web Planning Team began an analysis of Evergreen community members. | + | |
- | + | ||
- | The following criteria were used when discussing community groups and roles: | + | |
- | + | ||
- | (@@@TODO: paste in these!) | + | |
- | + | ||
- | The following groups of Evergreen community members were finalized by the Web Team in January 2011: | + | |
- | + | ||
- | 1. " | + | |
- | + | ||
- | 2. " | + | |
- | + | ||
- | 3. " | + | |
- | + | ||
- | 4. " | + | |
- | + | ||
- | 5. " | + | |
- | + | ||
- | 6. " | + | |
- | + | ||
- | 7. " | + | |
- | + | ||
- | 8. " | + | |
- | + | ||
- | 9. " | + | |
- | + | ||
- | 10. " | + | |
- | + | ||
- | 11. " | + | |
- | + | ||
- | 12. " | + | |
- | + | ||
- | 13. " | + | |
- | + | ||
- | 14. " | + | |
- | + | ||
- | D. Functionality-related Requirements vs. Content-related Requirements | + | |
- | + | ||
- | For each group of website users identified, the Web Team wrote multiple requirements in the form of user stories. | + | |
- | + | ||
- | User stories can be related to website functionality, | + | |
- | + | ||
- | User stories can also be related to content on the website, such as specific documents, materials, multimedia, or pages. For instance, having a special page on the website explaining the benefits of Evergreen to people who don't currently use it is an example of a content-related user story. | + | |
- | + | ||
- | In the list below, each user story is noted as either a content-related or functionality-related requirement. | + | |
- | + | ||
- | 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, | + | |
- | + | ||
- | 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" | + | |
- | + | ||
- | 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/ | + | |
- | + | ||
- | b. Developers can participate in the Administrator " | + | |
- | + | ||
- | 4. DOCUMENTORS | + | |
- | + | ||
- | a. Documentors can maintain the official project documentation in a repository apart from the community EG resource/ | + | |
- | + | ||
- | 5. CONSULTANTS | + | |
- | + | ||
- | a. Consultants can participate in the Administrator " | + | |
- | + | ||
- | 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 " | + | |
- | + | ||
- | b. Potentials can view contextual background information on Open Source Software. (content) | + | |
- | + | ||
- | c. Potentials are directed to visit a " | + | |
- | + | ||
- | 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/ | + | |
- | + | ||
- | 6. Potentials are directed to a third-party demo " | + | |
- | + | ||
- | 7. Potentials can search for an EG Service Provider based on certain criteria. (functionality/ | + | |
- | + | ||
- | 8. Potentials can search for existing EG libraries based on certain criteria. (functionality/ | + | |
- | + | ||
- | 9. Potentials can search for individuals in the EG Community based on certain criteria. (functionality/ | + | |
- | + | ||
- | + | ||
- | 9. SKEPTICS | + | |
- | + | ||
- | + | ||
- | 10. MIGRATION | + | |
- | + | ||
- | 11. STANDALONE | + | |
- | + | ||
- | 12. EXTENDERS | + | |
- | + | ||
- | 13. INSTALL | + | |
- | + | ||
- | 14. TRANSLATORS | + | |
- | + | ||
- | 15. ACCESSIBILITY | + | |
- | V. Recommendations | + | [[webteam: |
- | 1. People & Process | + | [[webteam: |
- | Marketing / Outreach / Awareness Committee | + | [[webteam: |
- | Publication schedules | + | [[webteam: |
- | 2. Technical | + | {{: |
+ | [[webteam: | ||
- | VI. | ||
- | |||
webteam/webplan/2011.1300477236.txt.gz · Last modified: 2022/02/10 13:34 (external edit)