Danbooru

[Prototype] User Report Ver 6.1

Posted under General

Jarlath said:

I personally consider tagme on a post with more than 10 tags an error in tagging, especially since 90% of what it covers can be handled by various request tags. For posts with less than 10 tags, tagme is just lazy as hell and is something I think should be weighted at a -10 for tagging report purposes, if not more. I've seen users throw tagme into a post to skip tagging them in a few occasions.

Well, I already give those users a neutral feedback. I kinda like this tag and feel "responsible" for the correct usage of it :3.

@provence @kuuderes_shadow

Sorry, I forgot to include it in the tables update... the removes column disregards the following tag removals: tagme, commentary, check_commentary, translated, check_translation, partially_translated, check_my_note, check_pixiv_source, *_request. I'll update the version notes with that info now.

As I mentioned, the reason why the removes column is kept separate from the tag errors, is because I saw a certain amount of subjective changes such as hair color changes for instance. But there were also a lot of genuine errors, for example the wrong character tag, or tagging headband when it was actually a hairband.

As for Jarlath's recommendation, I can include the adding of tagme to posts with 10 or less tags as a Tag Error, or I could make them a separate column (although the table is quite wide as it already is... :)

Edit:

Also, Tag Errors are currently mutually exclusive from the other tag categories, whereas Removes are not. So in forum #118765, kuuderes_shadow correctly subtracted the Removes category, but incorrectly subtracted the Tag Errors.

For that, I can go either way. I can leave it as it is, I can make it so that both are included in the other tag categories, or I can make them both mutually exclusive from the other tag categories.

Thoughts?

Also, after thinking about it for a bit, Tagme Errors would probably be better as a separate column, since otherwise it'd be mixing with and polluting the Tag Errors column, as it would be impossible to tell which one actually caused the error just from the data.

Updated

I decided to create a new forum post since the last one was busy as is... :p

kuuderes_shadow said:

It might be interesting to have a top (and bottom) tags/upload list for everyone - if possible with errors and removes subtracted from the list. For obvious reasons there would need to be a threshold for the number of uploads to stop both lists being flooded with people with 1 or 2 uploads. 100 is more than enough for this. 50 would probably be fine, too.

The one issue with this is that the number of uploads should factor into the weight of the rating.

Example:

User A uploads 500 posts with only 10 total tags per upload
User B uploads 10 posts with only 10 total tags per upload

They are both equal when you reduce them to a per upload metric, but one is clearly more damaging and causing more work for other tag gardeners. How do you represent that as a legitimate and quantifiable metric? I'm asking because I don't know... (Math was only my minor, and not my major...)

Don't know what you exactly, but if someone really has 500 uploads and has very few tags added, the existing tables are sufficient. You of course has to look what they upload. I nearly never get over a gentag of 15 when I upload Pokémon fanart for example. So yeah, numbers and systems are good, but one should never forget that in order to work with these tables, you have to do work manually, too.

The only difference to the rankings made by not subtracting the errors is that DeusExCalamitus becomes 0.05 tags per post 'better' than RazingK, rather than 0.06 'worse'. Not worth reposting over that.

As for the second post - I can think of various ways of doing it, but honestly, I don't think it's justified as:
- Most of the methods would involve an arbitrary method for selecting how much influence the tag count has on the figure, and would create very different results depending on what method was chosen. In some cases, you'd end up with a figure that doesn't make any sense to the casual observer as well.
- Someone who consistently uploads 10 posts a month with 10 tags per upload is just as much in need of improving their tagging as someone who does 500 posts a month with 10 tags each.
- So long as the requirements for inclusion are high enough for margins of error to be immaterial, a decent method shouldn't have an overly large impact on the figures anyway.

Just including the number of uploads on the table would be sufficient for anyone who deems that to be important.

New version... you can check the version info in the first post, but basically, I added correlation between wiki page changes made through the artist interface. This added an extra column to the artist table. For the wiki pages table, it disregards any changes made through the artist interface. This updated the numbers and rankings for both tables.

Also, I hadn't planned on creating a new forum post (like this) with every change to the first post, but I guess I could...

What table did you update? They are all from yesterday or two days (at least in CET^^), but I guess the artist table changed then^^?

Artist and Wiki Page tables were updated.

Artist table with a new column "Wiki" on edits to the wiki through artist interface.

Wiki Page table without edits through artist interface.

I'm kinda scratching my head why I have an average score of -3 in the comment section. Well, I get that my comments won't get much score (and they also shouldn't in my eyes xD), but is there a quick way to find which comments were downvoted so drastically. Probably because I argued and discussed a lot on flagged posts and defended the flag :>.

Provence said:

I'm kinda scratching my head why I have an average score of -3 in the comment section. Well, I get that my comments won't get much score (and they also shouldn't in my eyes xD), but is there a quick way to find which comments were downvoted so drastically. Probably because I argued and discussed a lot on flagged posts and defended the flag :>.

Probably not. But here they are anyway:

RaisingK said:

Probably not. But here they are anyway:

So it's most often harmles like asking things which is apparantly not well received^^. Well, I guess I'll stop that then if I should have a question about a character or if I disagree with something.

RaisingK said:

Probably not. But here they are anyway:

Did you code that on the fly, or did you just have that handy...? :)

BrokenEagle98 said:

Did you code that on the fly, or did you just have that handy...? :)

Well about that: Would that be possible to implement?
I mean for example:

Provence said:

Well about that: Would that be possible to implement?
I mean for example:

Are you asking to have two columns added to the comments table, namely the number of positive comments and negative comments? Everything else you need is already there...

Average score = cumulative score/ total comments
Deleted comments is already a column

Updated

BrokenEagle98 said:

Are you asking me to add two columns to the comments table, namely the number of positive comments and negative comments? Everything else you need is already there...

Yes. That was more or less a final version. So the comment section would look like this then:
Rank Username Total Updates Positive Negative Cumulative_Score Average_Score Deletes Bumps

By positive and negative the total amount of neg/pos comments.

Ok... I'll probably leave average score out though, since that's just basically one column divided by the other....

@BrokenEagle98: Not RaisingK, but I use jq for stuff like this. Makes quick and dirty JSON processing a snap:

If other people want to play with this:

sort_by(.score) | map({url: "http://danbooru.me/posts/\(.post_id)", score, body})

  • Percentage of comments that are negative:
(map(select(.score < 0)) | length) / length

  • Cumulative score:
[.[] | .score] | add

  • Average comment score:
[.[] | .score] | add / length

Updated