Technical Specifications
========================

Paul's Priorities for Friday 3/28 demo

 1. differentiated tags for Diseases and Conditions, Signs and
    Symptoms, Medications
 2. suggested case template plus references
 3. pattern matching for picking out terms in the narrative to suggest
    metadata
 4. advanced search

Maureen and Rupa's Priorities for Friday 3/28 demo

 1. case content for site
 2. commenting content for site
 3. metadata for cases

Ideas:

  * "Powered by UMHS Enabling Technologies" to allay support fears.
  * Import content from different sites to show them what's possible.

User Functions:

  * Add and edit (non-collaborative) - FRIDAY finished case is static
    WYSIWYG, WANT FOR FRIDAY live-blogged case is a blog page
  * Publish and update case studies (non-collaborative; templates)
  * BUILT IN Comment on cases (anonymous or identified, forum format)
  * Report as inappropriate (subject identifiable)
  * Classify cases (use pre-defined classification, e.g. MeSH)
  * Tag cases (folksonomy, recommend existing tags in case)
  * Automatically suggest tags based on content
  * Predictively suggest tags from taxonomy while tagging
  * Page Templates
  * Export pages (PDF, PPT, etc.)
  * Import pages (? PPT)
  * Find similarly tagged cases
  * Attach in line video and audio to cases
  * Rate comments
  * Rate cases
  * Rate users (? indirect from comments/cases) - compile reputation
    score from case contribution rating quality, page views, amount of
    discourse
  * Search for cases (faceted and/or free-text)
  * Edit/update user profile

System Functions:

  * Authenticate users
  * Maintain user profiles (identities)
  * Maintain user reputations (# and/or ranking of cases or comments?)
  * Maintain user roles
  * Ensure consent or de-identification of cases
  * Authorize users to publish cases (credentialing w/Cactus)
  * Present custom UIs based on roles

Content Management Systems (CMSs):
Drupal
Ektron

Blogging:
http://www.opensourceblog.com/