| |
Oswald
Registered: Apr 2002
Posts: 5094 |
New release type
Just a random idea, how about having a "release group" release type, whose role would be to group together releases which are related on a basis that is not possible to express with the current rules. (fex. same coder, same group etc) For example this would make it possible to link together, and view in a timeline dycp record demos, or demos that are response to each other (hcl&crossbows kefrens bar demos pop in mind), war demos against a certain group, etc. |
|
... 11 posts hidden. Click here to view all posts....
|
| |
Mace
Registered: May 2002
Posts: 1799 |
Very nice idea, Oswald, but I see problems with implementing it. Or rather, with using it.
What could happen, imho, is that you make a 'set' called "coolest filled vector demos" and I make a set called "hottest filled vector demos".
See where I'm going...?
How on Earth can we keep track of this?
How can we prevend this from exploding into the wildest collections of releases? |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
I dont like the idea of having strict rules, or predefined tags. Be it the 'tag' method, or another solution, I'd prefer having freedom in defining such 'collections'. Ofcourse rubbish should be deleted, but I wouldnt like to see rules like "collecting this kind of stuff is forbidden". How about restricting the number of 'tags' per user, and unlimited number to moderators/admins?
Bounding such 'collections'/'tags' to users is an extension of this idea which I like, but in this case browsing these shouldnt be strictly connected to user profiles.
a dropdown/multiselector in the release-edit page would work. or in case of many tags a search function like when selecting a profile. |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
Mace, I had to think a lot on this, though one, I came up with this:
- strictly connect collections/tags to users, each user can only edit his stuff, and it should be obvious that a collection/tag represents the choices of a certain person
|
| |
Mace
Registered: May 2002
Posts: 1799 |
Perhaps it could be organised a bit like a forum thread.
Someone can 'open' a collection with a certain title and set this collection to 'open' or 'closed'.
'Open' means everybody can attach releases to the collection, 'closed' means only the original starter can attach releases. |
| |
Perff
Administrator
Posts: 1679 |
I like most of the ideas here. :)
Just a question. Would it make sense to attach tags to other than releases? Perhaps even the same set of tags, or should it be strictly type-based tags?
Also the idea about private tags would solve the problem about ones favorite demos etc.
So my first thought is that when creating a new tag you need the following info:
- Tag name
- Private or Public tag.
- Type of tag. Can it be attached to releases only, or what?
Edit: We still need to avoid the situation where we get a lot of different tags that are basically the same as Mace mentioned |
| |
Mace
Registered: May 2002
Posts: 1799 |
Perff, nice thinking... Indeed, why only tag releases?
I might be interested in tagging my favourite coders... |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
- Tag name
- Private or Public tag.
- Type of tag. (restricted to some relesetype, or unrestricted)
some rules, from the top of my head:
- tag properties should only be changeable by creator / mods
- a new tag should be reviewed by mods, and only allow if a similar _public_ does not exist / makes enough sense. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11384 |
Quote:else we will soon have so many tags that it makes no sense.
isn't that the whole idea of that web2.0 tagging BS ? |
| |
A3
Registered: Dec 2005
Posts: 362 |
Speaking of relase types how about these 3 release types that are rare but do exist:
demo collection
intro collection and
game collection. |
| |
null
Account closed
Registered: Jun 2006
Posts: 645 |
and I still can't vote scout as best fullscreen musician D:
------------------------------------
http://zomgwtfbbq.info |
| Previous - 1 | 2 | 3 - Next |
