I've made some progress on coding tagzar - I'm using ASP.NET 2.0, but mostly rolling my own data layer as I really really hate what MS has come up with. I scribbled out some structure and relationship thoughts at House Coffee at lunch, and laid out a basic design with some usescases. I created the DB and the basic classes this evening.
Two issues I can see are going to be a pain is rating a site inside of a tag (figuring out that actual rating of site vs tag), and then relating tags together.
I believe it's important to track each individual vote by user - so I can revoke a user and have those votes drop off. So I'm going to have to do some kind of average by site, then order the return list by that average. Which SOUNDS easy, but I want (and need) that to happen in the DB. Fun stuff :)
Tag relations will be critical - one big issue will be usability for the sites users. I need to allow people to find and discover tags to search on. I could try to deal with that relationship myself, but I rather track the tags people use on sites. That is, if you used "code programming c#" as three tags on one site, I would know there was (possibly) a relationship between those three terms. The more those terms show up together, the stronger that relationship is.
SO, if a user had drilled down to "c#", and "code" had been used a lot with "c#", I would show code near the selected term "c#" in the return tag cloud.
I think I've got a way to do that - just need to work on it a bit.!
No comments:
Post a Comment