ENGAGE-162: Devise a data model for personal collections and users in Engage

Metadata

Source
ENGAGE-162
Type
Sub-task
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
N/A
Reporter
Colin Clark
Created
2009-10-21T17:49:38.000-0400
Updated
2010-02-08T16:16:04.000-0500
Versions
N/A
Fixed Versions
  1. 0.3b
Component
  1. My Collection

Description

As part of implementing the My Collection feature of Engage, we'll need to work out a reasonable data model for personal collections and users within the system.

Going with the document-oriented JSON approach offered by Couch, I assume that users will be a separate document within the system. For collections, I expect it will probably be as simple as an object which associates a user ID with an array of collection names in the system.

Comments

  • Justin Obara commented 2010-02-05T14:22:05.000-0500

    Bug Parade Engage 0.3

  • Colin Clark commented 2010-02-08T16:15:59.000-0500

    Sveto has implemented this issue in his branch. It still needs to be merged with trunk, which I am doing.