CAPRA Proposal for Future Development

aka "CAPRA v2.0"

Mission Statement

The primary direction for CAPRA from v1.0 into the future is to extend the foundation of the 1.0 spatial data viewer and map composer with the incorporation of user oriented and collaborative features. The broader audience may includes World Bank employees and those working on projects either funded by or in collaboration with the World Bank. The system will address both the problem of duplication of effort and increasing transparency with regard to geospatial data. In short, it should facilitate the ability of those involved with the World Bank to use maps to tell stories.

Components / Capabilities

Requested by the client:

see:  Annotated Version of ToR section for V2

  1. User Profiles
  2. Uploading Data
  3. Intelligent metadata collection
  4. User statistics
  5. Collaborative features
  6. Full search functionality
  7. Editing and Manipulating Data

Implied/Require to implement client requests:

  1. Authentication
  2. Authorization: granular capabilities/security system
  3. Interface for logical browsing of the site
    • GeoNode Homepage
    • Browse
      • Users
      • Data
      • Maps
      • Styles
    • (future) Projects/Groups
  4. Basic Notification system
  5. Syndication

Users and Collaboration

Registration/Login

  • registration form
    • spam protection/email verification
  • lost password handling
  • login form
    • when authorization required (w/ appropriate redirect)
  • visual indicator of authentication status
  • Admin interface for managing registrations and accounts

Nice to have:

  • Just in time registration (important to closely consider workflow and interaction w/ spam protection)

Profiles

  • Name
  • Location
  • Picture/Gravatar
  • Organization
  • Language preference
  • Personal Statement
  • (future) Projects/Groups/World Bank profile information
  • Easy access to personal statistics and contributions
    • Maps (either created or collaborated on)
    • Data uploaded
    • Comments/Ratings

Nice to have:

  • Private/Public profile exposure

Data Upload

  • Prompt for registration or login
  • Required but facilitated metadata entry
    • automatic metadata population where possible
    • auto suggest metadata
  • Styling

Open questions:

  • What formats accepted? what restrictions?
  • Where is data uploaded?
    • Context of a map
    • Context of a personal data area attached to the profile (i.e., My Data?)
    • In project areas?

User Statistics

  • Where/when should these appear?
  • Use cases

Some possible statistics

  • Last login
  • Layer downloads
  • Map hits (in Map composer, in widget export)
  • Map export (as file)
  • Metadata contributions by user (to encourage users to add metadata)
  • user participation in collaborative features (see below)

Collaborative Features

Additional crowd sourced metadata.

Possible targets: maps, styles, layers

  • tags/keywords (what is the distinction here) (implies a browsing or search mechanisms for tags)
  • ratings (functional implications: sorting of search results, sorting of other lists)
  • score: a number representing some combination of completeness, usage, rating and other possible quantitative qualities of an item.
  • comments: (threaded?) (audience?)

Security

Security model must accommodate the access control on CRUD for the follow items:

  • Layers
  • Styles
  • Maps
  • Comments
  • Ratings
  • Tags

For the following agents:

  • Anonymous
  • Authenticated users
  • Admin
  • Owners
  • (eventually) Groups
  • (Other roles?)

Tight integration between searching and download. Client has also requested a map panel that will adjust with or provide search parameters.

(what powers text search? Lucene?)

"geography, theme or keyword"

  • simple text search
  • simple extents search
  • parameterized search
  • results filtering
    • by tag
    • by user/project
    • by item
  • filter builder

Output:

  • previews?
  • icon for different available download types
  • Batch download (ala shopping cart)

Editing and Processing

see ToR. Client has declared most of this beyond next step, but we should spec ideas anyway.

Reference

20090722 wireframes:

drafting EtherPads: