3,699
edits
ClassificationSystem DEV: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
m (→Requirements) |
mNo edit summary |
||
| Line 19: | Line 19: | ||
* Groups | * Groups | ||
* Verification Layer | * Verification Layer | ||
* Weight (only applicable for anime and only 3 levels) | * Weight (only applicable for some tags for anime and only 3 levels (some, important/highly visible, everywhere/main)) | ||
* Group Restriction from certain Systems (no char tags on anime level -> for example death of anime tag tsundere) | * Group Restriction from certain Systems (no char tags on anime level -> for example death of anime tag tsundere) | ||
:* to compensate for this character tags could be displayed based on character data | :* to compensate for this character tags could be displayed based on character data | ||
| Line 34: | Line 34: | ||
There would be no predefined data pool like for categories, but unverified ones would not be displayed. Making it flexible, extensive and still hardened against trolling. | There would be no predefined data pool like for categories, but unverified ones would not be displayed. Making it flexible, extensive and still hardened against trolling. | ||
===Data Input=== | |||
Data input would be realized analog to character tag addition. To set weight one could allow the following format from the edit box: | Data input would be realized analog to character tag addition. To set weight one could allow the following format from the edit box: | ||
| Line 40: | Line 41: | ||
<tt>etc.</tt><br /> | <tt>etc.</tt><br /> | ||
Alternatively or additionally there could be a massedit page build displaying the already set ones with radio buttons next to them. This should lessen the impact of dupes | Alternatively or additionally there could be a massedit page build displaying the already set ones with radio buttons next to them. This should lessen the impact of dupes | ||
===Data Presentation=== | |||
Creator and Character Tags should remain their current presentation forms, because it has proven to be successful. | |||
For Anime we could have multiple forms. Currently we make use of tag clouds. This makes sense for when things can be weighted and displayed that way. Though there are lots of tags which are valid and just simple yes/no choices. Weighting and displaying these as cloud makes no sense. A group based listing might be more sensible here. | |||
group 1: | |||
:tag 1 (<number of usage>) | |||
:tag 2 (<number of usage>) | |||
:tag 3 (<number of usage>) | |||
:tag 4 (<number of usage>) | |||
group 2: | |||
:tag 5 (<number of usage>) | |||
etc. | |||
These could be displayed in multiple columns. | |||
Character Tags on the anime page could be displayed like this as well. | |||
Open question here is if clouds should be ditched alltogether or if a mixed display is wanted. | |||
==Import Scenarios== | ==Import Scenarios== | ||
| Line 54: | Line 76: | ||
:* use votes to build a weight and flag them as imported so mods/user can manually approve of it | :* use votes to build a weight and flag them as imported so mods/user can manually approve of it | ||
:* import to a default value | :* import to a default value | ||
* certain tags/groups might even not get a weight at all. there are various meta tags that can't really be weighted, but are valid to keep around like "uncensored version available" | |||
===Char tags=== | ===Char tags=== | ||
| Line 65: | Line 88: | ||
===Open Questions=== | ===Open Questions=== | ||
* | * Are biased and subjective tags are really needed (for anime)? | ||
:* | :* If yes do we need a different presentation? | ||
* | * Is there a need for certain tags in an approved group for a certain entity to not be available or the other way around | ||
:* | :* Are there tags that would be grouped differently for different entities?/do we need groups per entity? | ||
* How do we display the content on the anime page? Clouds? Listings? Mixed depending on type? | |||
[[Category:Development]] | [[Category:Development]] | ||