Roadmap
-
The Pilot Release milestone will be targeted at 2 or 3 communities to gather feedback on usability and test basic functionality.
Requirements
- The Pilot Release will provide a basic map interface restricted to the geographic extent of the target community.
- Anonymous users will be able to navigate around the map using basic pan/zoom controls and by dragging the map.
- Anonymous users will be able to search for a location by address or placename.
- Anonymous users will be able to search for contributed stories based on category and keywords in the description.
- Story search results will be viewed as a list and rendered on the map.
- By clicking on a story in the results list, the map will recenter on the story location.
- By clicking on a feature representing a contributed story, users will be able to see the story content (photo, video, or text document) in a popup bubble or sidebar.
- Authenticated users (we will supply login credentials to target users) will be able to contribute stories based on the workflow below.
- Authenticated users will be able to comment on previously contributed stories.
- Authenticated users will be able to remove stories that they contributed.
New story workflow
- Users will select from a list of categories that describe their story type.
- Users will click on a tool that lets them draw a point, line, or polygon feature.
- User clicks on map once for point or multiple times to draw a line or polygon (double-click ends drawing of lines and polygons).
- Markers will be displayed for point locations based on category, lines and polygons will be styled according to category.
- After creating a new story location (point, line, or polygon), the user will be presented with a dialog for entering the details of their story (see story schema below).
Story Schema
All stories have a category that characterizes them (list of categories to be provided by Orton). Stories are further classified by media type. Allowed media types will be photos, videos, and text documents. Photos will be hosted at Flickr, videos will be hosted at YouTube, and text documents will be uploaded to the almanac. In addition, authenticated users will be able to comment on stories contributed by others.
Story fields:
- category - fixed vocabulary
- media - media type (text, photo, or video)
- title - text (25 letters or so)
- description - text (25 words or so)
- content - text (link to video and photo, story text for documents)
- author - inferred (from logged in user)
- date - inferred
Comment fields:
- content - text of comment
- author - inferred (from logged in user)
- date - inferred
-
-
Based on feedback generated from the Pilot Release, new features and workflow will be incorporated into a Feature Release.
Requirements
- User feedback will be collected and summarized based on the Pilot Release.
- Orton and TOPP will work together with this feedback to distill it in to a list of new features and workflow modifications. These changes will become additional requirements for the Feature Release.
- An application framework will be developed around the basic map interface from the Pilot Release.
- This application framework will handle user account management, new almanac creation, almanac configuration and will provide the rest of the website around the map interface.
- The entry page for the website will feature stories from newly created or active almanacs. Users will be able to quickly see examples of contributed stories mapped.
- Users will be able to come to the website, register themselves, and start a new almanac or join an existing almanac.
- As the initiator of a new almanac, a user will have the role of "almanator." With the almanator role, a user can perform basic administrative tasks related to an almanac (listed below).
- Search results will be made available in several alternate formats (in addition to listing on the page or rendering on the map).
- Search results will be available as KML (for viewing in Google Earth).
- Search results will be available as an RSS feed with locations in GeoRSS (for syndication or use in other applications).
- Users of desktop GIS will be able to download contributed stories (without full text for document type) in shapefile format.
- Users will be able to print story search results (as a PDF file).
- By default search results will be printed with title, description, author, and date.
- Search results can optionally be printed with content from text documents inline.
Almanator Tasks
A user with the almanator role will be able to carry out the following tasks through an administrative interface.
- Select the geographic extent for the almanac. This will be done by navigating a nationwide (U.S.) map until the extent fits the bounds of their community and saving that extent.
- Select a subset of the category list to be made available through their almanac.
- Customize the look of the new almanac by choosing a layout template, adding a title and description, and uploading a logo (and/or a number of photos depending on the template).
- Remove contributed stories.
- Remove registered users from their almanac.
- Give the almanator role to another registered user.
-
-
Milestone: Meeting: Final preview
Due in 12 days (07/16/08)
-
-
The Stable Release will include all bugfixes and address all issues generated by the Feature Release.
Requirements
- All issues generated since the Feature Release that relate to the requirements of that release will be fixed (or otherwise closed if agreed upon by Orton and TOPP).
- Automated unit and acceptance tests where appropriate will be developed to ensure stability of the code base.
- Manual user tests will be conducted to demonstrate the usability of the almanac.
- Documentation will be produced to guide new users through contributing to the almanac. Additional documentation will be produced to describe the almanator role.
- Production server (or servers) will be set up for hosting the almanac.
-
Note: See
TracRoadmap for help on using
the roadmap.
