Allen, I was thinking of using the entryattribute table, what do you think? I don't think that we want another table for every little feature. At first I was thinking of something simple, like a "text" field a la del.icio.us as another + in the settings section of the post that can be edited by the user anytime. Maybe then using the Tag render plugin for just rendering the tags and also making sure that Lucene indexes the tags as well. I don't think we need to worry about the big content or technorati style dashboards yet, but at least start collecting the data.
I do have a problem with the entryattribute table in general because it's very limiting. For example, it's really cumbersome if I want to store both the tag and the date it was inserted on. Even worse, if I had another piece of metadata about that tagging to insert. It works for MediaCast right now because you only have attributes about the entry and not about the actualy entry metadata. I had mentioned to Dave on IRC that since my day job is on Semantic Web stuff, maybe making that table a more RDF-friendly table would be really cool for Roller. What does everyone think? Who else is using the entryattribute table besides MediaCast? Elias On 9/14/05, Allen Gilliland <[EMAIL PROTECTED]> wrote: > Elias, > > I had actually began working on tag support and prototyped it back in > July, but I didn't get much feedback/support on it so I focused on some > other things instead. I still have some code that works if that would help. > > http://www.rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_WeblogTags > > It looks like I had also started a very simple design doc which you are > welcome to elaborate on. To be honest I don't think adding tag support > takes much code, but it will require a significant amount of design > because it will require a lot of dynamic content on concievably large > sets of data. > > I'm definitely looking forward to what you come up with, this would be a > great addition to Roller. > > -- Allen > > > Elias Torres wrote: > > >I have updated my patch to now work with DB2. Everything seems to be > >working beautifully. > > > >http://torrez.us/2005/08/23/roller/patches/db2_derby.hibernate3.patch > > > >Regards, > > > >Elias > > > >PS> Now onto tagging. > > > >Heads up. I would like to add tagging to Roller, possibly using the > >metadata table. I'll try to draft something up on the wiki. > > > >On 9/13/05, Elias Torres <[EMAIL PROTECTED]> wrote: > > > > > >>Hi Everyone, > >> > >>After getting the nice upgrade to Hibernate 3 by Dave, I started > >>working on testing Derby support first, then DB2. I only found a > >>couple of issues with Derby so far, everything seems to run fine. > >> > >>Here's my patch: > >>http://torrez.us/2005/08/23/roller/patches/derby_hibernate3.patch > >> > >>Basically, > >> > >>There was a getInt() that doesn't seem to work on strings for Derby, > >>so I did this: > >>- dbversion = rs.getInt(1); > >>+ dbversion = Integer.parseInt(rs.getString(1)); > >> > >>The next one was a query in HibernateRefererManagerImpl.java which is > >>not performed via Hibernate and there was a "limit" keyword which is > >>not supported by Derby. I first tried the HSQL version, but Derby > >>doesn't support TOP either. I added a check on the loop for max > >>results, somebody please verify that this is ok. Thanks. > >> > >>Elias > >> > >>PS> Now onto DB2. > >> > >> > >> >
