A few quick comments: * its not clear what column family the super column you're using is in. * it might be useful to include the timestamps in the columns (since they're user-supplied) * given that the colon-delimited api has been removed, it might be easier to explain the data model without such strings * why would you mix different kinds of data in the same column family, rather than having separate column families for each? (users, bookmarks, tags)
-ryan On Wed, Aug 12, 2009 at 4:57 PM, Mark McBride<mark.mcbr...@gmail.com> wrote: > While working on an updated data model wiki page I'm trying to put > together a graphical representation of the data model. I threw this > together based on Curt's goal of modeling delicious. The basic gist > is descriptive data for tags, users, and bookmarks goes in the > Description column family. The relationships between bookmarks, tags > and users goes in the map supercolumn. I'm not sure this is how you > would do it in production (I'm guessing at the very least you'd want > separate supercolumns for bookmarks, tags and users), but it seems to > be simple enough for a new user to digest, and covers all the bases of > the data model (aside from ordering I guess). So two questions > > 1) did I get it right (I'm new to this as well)? > 2) is this a useful representation? > > ---Mark >
