| |
jailbird
Registered: Dec 2001
Posts: 1578 |
Tags (yet again)
It is still unbeknownst to me why tags weren't implemented yet, or why are some so stubbornly against it. This portal is almost completely based on IMDb, and tags are one of the most useful features on that site.
Just a few of the useful features it would bring:
- finding demos containing an effect, record, theme...
- finding musics with a specific style, instrument, musical technique...
- finding images with a certain motive, character, technique, color-sceme...
- finding a specific usage of a tool/utility
- finding a magazine with an article about XY
- etc. etc...
It wouldn't take more than an hour to implement: another textbox on the "add comments" page with the Tags label (separated with commas) -> parsing the field and popping it out on the profile-page (as links, so if I'd click on a tag, I'd be redirected to a search-results page with a list of all those products where the same or similar tag was present).
Of course it wouldn't work right away, populating would certainly take some time. Just as everything else on this site.
Any thoughts? And in case of another instant rejection, I'd definitely love to get a bit more reasonable answer than the usual "I don't think we need it. Oh, and look here's my middle finger too. thxbai"
|
|
... 64 posts hidden. Click here to view all posts....
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11359 |
as said, i can see it working (only) this way. it must be made sure that tags are only used for the kind of info which isnt really suited for "real" database entries. for example if we had a "koala" tag, it should *not* replace the graphics-type/koala database field - but instead every entry whith this graphics type should be equivalent to every entry tagged as "koala" when it comes to searching/browsing.
at the end its all more a question of how the frontend interface works rather than if it is "tag based" or "classic database", for the most part IMHO. obviously the frontend could also simply silently convert the "koala" tag into "graphics-type/koala" each time a graphics release is tagged "koala" ... (and if i'd be more into php+sql i might have suggested that its time to finally think about csdb v2 again at this point... =P)
|
| |
jailbird
Registered: Dec 2001
Posts: 1578 |
Quoting Gropeazas said, i can see it working (only) this way. it must be made sure that tags are only used for the kind of info which isnt really suited for "real" database entries. for example if we had a "koala" tag, it should *not* replace the graphics-type/koala database field - but instead every entry whith this graphics type should be equivalent to every entry tagged as "koala" when it comes to searching/browsing.
That's exactly how I thought about tags in the first place, so it's more than fine with me. Does this means that after all we settled on a solution which would suit both parties? I can't fucking believe it! :)
Dedicated users for tag-moderation will probably result in more work for Perff, though. So it would be great if he'd also state his opinion on this matter. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11359 |
Quote:Dedicated users for tag-moderation will probably result in more work for Perff, though.
i'd just make that a trusted user feature (and have one or two more of them eventually). |
| |
Conjuror
Registered: Aug 2004
Posts: 168 |
For a user interface implementation, I'd suggest grouping the tags by category and make them push on/off buttons, which are saved at the same time as the entry. They could still look like a text tag 'cloud' with some sort of colour, background or border? to show they are selected. The read-only view showing only those tags selected (obviously)
Maybe still offer a field for new tags which are moderated.
|
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
Some ideas of how it could be done...
Minimal implementation: A textbox for each release where you can enter comma separated tags. The existing tags are listed with a checkbox for deletion. Everyone should be allowed to add and delete, like all other content.
Bonus features:
- Tags separated in categories like gfx, music, effects, other.
- "AJAX" interface with a small textbox for only one tag. When you start typing a list of suggestions appears below, which you can select. This helps getting more tags that are spelled the same way. When you have selected one, or finished typing, a new textbox appears for the next tag.
And tags should of course only be for info that isn't already represented in the DB. |
| |
cba
Registered: Apr 2002
Posts: 935 |
I am very pro TAGS, lets wait till Perff replies and see his thoughts about it. |
| |
Ed
Registered: May 2004
Posts: 173 |
I'm pro tags.
Jailbird pretty much points out the benefits in the first post.
Tags could be used in other purposes of course.
Maybe I should start using delicious a bit more often if nothing happens... |
| |
Perff
Administrator
Posts: 1679 |
Just a note that I'm aware of this thread, and the wish to add tags to CSDb.
I can see there are quite a lot of posts in this thread that I probably should read before commenting on this, so - I'll be back. :) |
| |
Count Zero
Registered: Jan 2003
Posts: 1926 |
I don't completely object tags but wonder as to when clever people will figure it can be used as a substitute for e.g. Subtypes for tools? and being pretty sure that many of such tags will go unchecked...
I suppose at least some basic conventions regarding tag contents should be made.
|
| |
Steppe
Registered: Jan 2002
Posts: 1510 |
Let me raise my hand in favour of tags too. I'm not as active as I used to be these days, but WHEN I'm adding or checking stuff, I make sure stuff is done properly. That includes the future addition of tags, too. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 - Next |
