May as well report this now so that the wikiHow staff can be immediately swamped with yet another task right after the meetup.
There’s approximately 61 articles listed in the Copyedit Greenhouse on the dashboard, and I’ve verified this by checking Category:Copyedit. But when I go into the Copyedit Greenhouse, it briefly gives me the spinning circle and then returns “[No articles found]” even though there’s a good 60 articles in the category, not counting the Test Copyedit article. I can still sort of cheat the whole Greenhouse system by just going to Category:Copyedit and copyediting the articles from there, but this should probably be fixed, especially since newer members of wikiHow will just get “[No articles found]” and may not know about the actual category for articles needing copyediting!
1 Like
Anna
2
Hah- keeping us on our toes, Alex
So usually when there’s a mismatch like that for something like the Greenhouses, it comes down to skips. For example, when I open up the Copyedit Greenhouse right now, I’m getting articles okay- I just looked at about 8 of them in a row (and there were still more left for me). But if you’ve skipped any in the past, the system saves that info so you don’t see the same article again. Is it possible you’ve skipped 60 or so over the last few weeks/months, here and there? That might explain it, unless everyone is seeing an empty queue (I’m not right now). But if that is it and you’ve decided you want to go back to any of them, the category view is definitely good for that, like you said!
Isn’t that my job?Ah, okay, that makes sense. I don’t think I’ve skipped as many as 60 though - and I know I’ve seen several that I’ve previously skipped pop back up in the Greenhouse many times. Is that the system’s way of yelling at me, “EDIT THIS ARTICLE ALREADY!”?
1 Like
Anna
4
Yaaa I’m sure it’s not perfect even within its intended behavior. I think if a tag is removed and then readded, it may count it freshly, so you’d potentially see some go around again then. In the past some of our skip records were based on cookies, too, so then it’d be browser dependent as well… But I don’t think that’s the case here. I’m not positive on that but that’s my fuzzy recollection from when an engineer looked at a similar report in the past (that it’s recorded in the database, not browser cookies, for this tool). I’ll do some more testing and playing around in the queue during the week, though, to make sure it keeps serving up more articles as more get tagged, and I’ll talk to an engineer if it’s looking fishy! Thanks for the heads-up.
1 Like
