Skip to content

Rhaptos Software Development

Personal tools
You are here: Home » Development » Planned Projects

Planned Projects

Document Actions
Quick list of potential development projects, in no particular order or probability of implementation. Basically, a to-do list. Note that the categories are rather arbitrary, and essentially just to clean the list up.

Uncategorized/New

none


Quick Tasks


  • Rework browse pages that make one catalog call per author/keyword/language
  • Demo del.icio.us implementation of lenses
  • Firefox search box plugin
  • Hide columns UI
  • Connexions blurb on content pages
  • In ModuleView, make attributes/metadata URL-accessible (probably just with docstring)
    • Possibly related: for REST API provide a way to tell explicitly between modules and collections
  • Metadata enhancements
    • for exported content: license, point to cnx.org
      • possible clarification of "attribution" to include URL
    • whatever cbearden was working on
  • Do endorsements really exist? How are they used (jcc)
  • Simple group enhancements
    • Invites, email
  • Evaluate options for Smart Folders
  • Rhaptos mailing list
  • External service integration for inserting images, etc
    • Flickr, Wikimedia Commons, et al
  • Replace multiple getStyles with style registry
  • Rationalize macro structure of content_template/collection_view/content_info, esp with regards to custom header
  • Store list of contents in ModuleView (so we don't touch CVS to find out if something doens't exist)
    • Try to get module view down to one checkout (maybe associate CVS tempdir with module view?)
  • Allow DnD functionality in Course Composer, both panes. (Currently disabled.)


Upcoming


  • [done-ish] IMS export of courses
  • Assign global IDs at creation time
    • preview of course with unpublished modules
  • Replace CVS as repository for scalability (probably SVN) if necessary


On Publish


  • Invent some sort of criteria-based system for plugging in tasks to happen on publish
  • Ask for translations for content-view elements
  • Log copy somewhere for content recovery


Holes


  • Export on published courses/modules
  • Add retirement ability to content (like deletion, but historical versions still available)
  • Course Imports
    • IMS
    • text
    • CSV/XLS
    • zip
  • Translation/translated/derivation/etc notifications
  • Group roles with "sharing tab" for reviewers and such
  • Contextual help (possibly incl. popups) - see markh
  • Resurrect previous summer work on diffs



Strategic


  • Roles refactoring for genericness
    • universal ordering
    • ad-hoc roles
  • Push more products out to public (Repository, Collection?)
    • More significant standalone rhaptos distribution
  • Etna usability improvements: http://rhaptos.org/ui/editorReview/ETNA%20Heuristic%20Review
  • WYSIWYG online editor as EIP alternative (Kupu? other XML editor?)
  • WYSIWYG math editor, possibly with external help
    • Etna integration desirable, so Javascript base is nice
    • Jumpstart open source project around it?
  • Lenses/User lists
    • restricted view
  • Author communication
    • Periodic author newsletters
    • Online change alerts
      • Even to prompt to fill in profile (if blank)
  • User portal (myCNX)
  • Organizational portals with branding and selection of content (lenses)
    • User supplied styles and possibly HTML to insert in header
  • print to OO.o/Word instead of LaTeX for end-user polishing (Qoop support)
  • multiple names for collections / genericize course to collection
    • multiple types of collections with different behavior


Nice to Have


  • Online LaTeX import (working)
  • workgroup tab forums (previous attempt abandoned)
  • Viewable/Editable export
  • Portlet-clipboard-based cut/copy/paste
  • Browse by... unification (ideally one application instead of many pages)
    • possibly using Smart Folders or Smart Folder-like functionality; possibly AJAX-ish for speed
    • might even be able to replace Search and Browse with "Find"
  • Per-instance XSLT/XML. (cbearden request)
  • other del.icio.us integrations (search, related, etc)
  • Smart Folder use somehow
  • Distributed translation engine (a la Clickworkers, captcha defeating, categorization games)


Infrastructure


  • RhaptosModuleEditor modernization (AT based)
    • workflow modernization (DCWorkflow instead of ad-hoc)
  • Dev infrastructure
    • Bugtracker
    • Proposal/specification-based development
      • Comment ability
    • Wiki/blog improvements
  • Move to PAS, with CAS auth for SSO capabilities
  • Upgrade rhaptos.org to Plone 2.1/2.5/3.0
    • Other infrastructure upgrade (underlying software)
  • OAI support's IMSMD is totally separate from the IMS export's metadata. Regularize, if reasonable.
  • [done?] Smarter links (don't assume modules will always have the same URL)
  • Hunt down and kill bad TAL (on-errors, existence tests that call things, etc)
  • Diff-based skins (done; seems impractical)
    • Upgrade CNX to Plone 2.1/5
  • Consider making Module Version Folder contain solid objects as canonical, using CVS for backup


Long Range


  • Distributed repositories


Philosophical


  • Choosable ids for modules
  • Support XHTML and/or Word native
    • possibly internal JIT CNXML translation
    • supports easy round-trip
  • Allow more data types to be first-class citizens, or something similar
    • segues, introductions, etc
    • start with images, audio/visual, other forms
    • simple integration into modules, and/or used directly in course construction
Created by jccooper
Last modified 2008-01-09 14:46