dotLRN: Left to Finish Core

Last update: $Date: 2002/02/28 18:40:13 $

Here's what we need to do to finish core:

Portal

• Implement portlet locking capability.
• Implement cloning stuff.
• Clean up UI on configuration page (change backlink)
• add roles and permissions (admin create|delete)(from dotlrn_community API)
• code review (Wednesday, 11/21, 2pm).
• change theme data model to map to pages.
• Refactor some functionality as part of base portal package.
• add acs-service-contract support.
• update all portlets for datasource.new, user_editable_p, shadeable_p, hideable_p, sc, new procs
• Adjust buttons on portlets as a function of capabilities
• Remove render-element.tcl ::get_pretty_name other render cleanup

dotLRN Core

• Review exactly what the roles are
• Write up permissions procs!
• Move administration to community-specific pages! Duh!
• Allow for addition of users who haven't registered yet? Check that.
• Automatically redirect single-community guests to the right location.
• Fix registration/deregistration bugs!
• Get clubs working
• !! Figure out Relational Segments !!

Operations

• prepare staging server:
  • AOLserver 3.3ad13
  • Oracle 8.1.7
  • drivers
• review existing SloanSpace site

calendar

• make group calendar work!
• each user has *ONE* personal calendar, and has access to each community calendar.
• calendar works as multi-package view in portlet.

• part of this involves figuring out multiple values for single parameters (instance_id in particular).
• every user has only ONE personal calendar
• every community has only ONE community calendar
• when a user views a community-specific page, he/she only sees that community's event.
• on personal calendar, they see everything

bboard

• test a bit more
• improve the portlet and make it NOT dependent on dotLRN
• allow parameter editing for displaying certain information in portlet

File Storage

• Clean up UI big time
• Clean up portlet to display the right stuff
• Make sure permissions are inherited correctly from parent folder and such
• Make sure permissions are correct on public folder.

FAQ

• Clean up portlet UI (display list of FAQs)

News

• make news multi-instance capable.