2013/8/20 David Narvaez <[email protected]> > On Tue, Aug 20, 2013 at 4:48 AM, Lodewijk <[email protected]> > wrote: > >> > -what happens to photos not rated in cases there are too many photos > and > >> > not > >> > enough reviewers? Are they just left behind? > >> > >> Haven't thought of that. In my small head all photos have to be > reviewed. > > > > > > Would this be solved if you start at a random point in the review list > > rather than always at the beginning? Then every jury member would start > > somewhere else, and the odds of images having zero reviews is minimized. > > If we agree that all photos must be reviewed before advancing to the > next round, then there are several ways to guarantee all photos are > reviewed. The question is whether we want to enforce all photos to be > reviewed or not. > > >> > -is "rate as you go" a possibility, or would you have to wait until > the > >> > end > >> > of the contest? > >> > >> Good question. The tool is not really designed for that, but could be > >> extended to support this. I'd like to hear other opininos about this. > > > > > > I think if you allow feeding multiple txt files through the contest > (taking > > out doublures) that might work? > > What would the source of the txt file be? A list of new uploads? If > so, then we could add a feature where the tool updates itself with > newly added items in a category every day. >
Sounds even better - my suggestion was just trying to make your life easier :) But this option should definitely be optional and possible to turn off after a while - I suspect most countries will not start judging before the end of the month, and we don't want pollution of the category trickle through into the jury tool. > > >> > -presentation, could you include a box where the local designer (who > >> > selects > >> > the various options) explains how they work, i.e. what are the > mechanics > >> > for > >> > a photo to get to the next round. > >> > >> That's doable, and shouldn't be too hard. I would only need help with > >> the wording (see the other thread about design). > > > > > > I think if you just present this as an option, you could have this as an > > empty text box in the configuration, and let the configurer worry about > the > > wording (and language). > > Ok. > > > A question of my own: what happens if an image gets renamed/deleted. Will > > the tool be able to handle that? > > Haven't thought of that, good point. This is somewhat related to the > rate-as-you-go mode discussed above, so let me think about these and > I'll write back with a plan (or no plan ;)) > Also important when you get the images you display directly from commons (or do you download everything) and to keep the links working. A possible way of dealing with it, is keeping an eye on move- and deletion logs (which are public) and processing that. Not sure how that would work automatically, but the data is there. > > David E. Narvaez > > _______________________________________________ > Wiki Loves Monuments mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments > http://www.wikilovesmonuments.org >
_______________________________________________ Wiki Loves Monuments mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments http://www.wikilovesmonuments.org
