Milestone 0.2 Feature Release

Based on feedback generated from the Pilot Release, new features and workflow will be incorporated into a Feature Release.

Requirements

1. User feedback will be collected and summarized based on the Pilot Release.
2. 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.
3. An application framework will be developed around the basic map interface from the Pilot Release.
   1. 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.
   2. 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.
4. Users will be able to come to the website, register themselves, and start a new almanac or join an existing almanac.
5. 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).
6. Search results will be made available in several alternate formats (in addition to listing on the page or rendering on the map).
   1. Search results will be available as KML (for viewing in Google Earth).
   2. Search results will be available as an RSS feed with locations in GeoRSS (for syndication or use in other applications).
7. Users of desktop GIS will be able to download contributed stories (without full text for document type) in shapefile format.
8. Users will be able to print story search results (as a PDF file).
   1. By default search results will be printed with title, description, author, and date.
   2. 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.