Log In

SRG as Resource

Added by Jim Eng, last edited by Jim Eng on Nov 15, 2007 (view change)

User Interface Decisions

Viewing SRG's
- Advantages of being treated as Sakai "resources"
  - UI's for browsing, copying, moving, deleting and linking already exist (we save on development effort)
  - UI's for browsing, copying, moving, deleting and linking already familiar to users
  - "View" of a resource relatively easy to implement
- Disadvantages of being treated as Sakai "resources"
  - SRG may get lost in large collection of other resources
  - Adding functionality to return results to other Sakai entities may be more complex
Authoring SRG's
- Advantages of being treated as Sakai "resources"
  - Might seem odd to have SRG's in resources tool but no way to create them in resources tool
- Disadvantages of being treated as Sakai "resources"
  - Not obvious that you would use resources tool to create SRG
  - Authoring large or complex resources not well-supported in resources tool

Data Persistence Decisions

Storage of SRG contents
- Advantages of storing SRG contents as resource file body
  - No need for separate store for structured or unstructured data
- Disadvantages of storing SRG contents as resource file body
  - Updating stale data within an SRG (links, search targets, etc) requires extra effort
Storage of config data for authoring