UNIFIED Challenge Admin testground / Discuss

Alesa Dam says:

What does it do?

The script aids in administrating challenges, in the supported Flickr Challenge Groups.
Posted 38 months ago. (permalink)

Alesa Dam says:

Installation

To be able to use the script, you will need to use Mozilla's Firefox web browser, with the Greasemonkey add-on.

The script also runs in Google Chrome, and in Opera (v10.53 and up).

Firefox
Once you have installed Firefox+Greasemonkey, head over to userscripts.org, and click the Install button on the UCheckPlay script's page.

Google Chrome
Head over to the extension's webstore page, and click the Add to Chrome button.

Opera
Download the script from the UCheckPlay script's page, and place it in your scripts directory.


In case you encounter problems, with installing, or with running the script, don't hesitate to Flickr-mail me. In case of errors, you may first try the beta version to see if your issue has already been solved. The beta version can be found at userscripts.org/scripts/show/70286.

Note

Some people did not see any output from the script, after installation. They were able to get the script working by fiddling with their Firefox preferences: enabling third-party cookies did the trick. Note, however, that on both my own systems, one Windows, one Linux, third-party cookies are disabled:



Credits for solving this mystery go to blueeyeddebby , in the discussion Bump feature with Firefox 3.6 on userscripts.org
Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 6 months ago.

Alesa Dam says:

Version number

The script adds it's name and version at the top of the page:



When reporting bugs, please include the version number.
Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 38 months ago.

Alesa Dam says:

Preferences
To open the Preferences dialog, click the link next to UCheckPlayNG Admin preferences::



Photo Information Boxes:

On the challenge page, the challenge configuration box has a checkbox show information boxes which draws the photo information boxes below each photo.
When the option 'smart' photo information boxes is selected, the challenge page will have the photo information boxes available for all non-approved photos on the page.

Awarded medals:

The photo information boxes on both the challenge thread pages and the Pending Items provide a means to easily check previously won medals for a photo.
By default, it shows all medals, including the non-won medals. Check the only show won medals checkbox to change this default. On the photo information box you can always override this default value.

Searching the medals can be time consuming. If it's enough to find one won medal, check the stop at first medal preference. On the photo information box you can always override this default value.

On that photo information box, you can choose what group medals needs to be checked. By default, the script uses the current group. Choose a different group as the default. On the photo information box you can always override this default value.
A different group can be defined for the challenge pages and for the Pending items pages.

Bump:

After bumping, the bumped threads are marked with a green check mark, when successful, or with a red cross, when failed. If the reload after bumping option is set, the page will reload automatically after all selected threads have been successfully bumped.

Update group definitions

The script updates the group definitions every 12 hours.
If, for some reason, you need to force it to update right now, hit the update icon. You'll get a notification when it's done. If it errors out, it will show you the reason why when you hover the mouse over the red cross that will appear next to this option.

Update medal definitions

The script updates its medal definitions once a week.
If, for some reason, you need to force it to update right now, mark the check box and hit update. You'll get a notification when it's done. If it errors out, it will show you the reason why when you hover the mouse over the red cross that will appear next to this option.
Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 13 months ago.

Alesa Dam says:

Challenge configuration box

In a challenge thread, below the challenge announcement (or the opening entry), a box is drawn with the challenge configuration:



Hovering the mouse over any of the elements of the dialog will show a brief explanation.

photos: the number of challengers needed in this challenge
Most challenges require a certain number of participants before voting can start.
Special value: 'n/a' = not applicable; is used for challenges that have a time constraint for entering.
UCheckPlay will show [Filled] once this number is reached.

score: the score needed to call a winner
Most challenges declare a winner once a certain score is reached.
Special value: 'n/a' = not applicable; is used for challenges that have a time constraint for voting.
UCheckPlay will show [Finished] once this number is reached.

voting: the type of voting
The script recognizes 7 types of voting:

HORIZONTAL: voters add a point for their favorite:
. voting starts with 0-0-0-0
. a vote for a photo increments the value for its index in the score
. example:

0-1-2-3
another vote for photo 3 would give:
0-1-3-3

PIC-P-1: voting used in MatchPoint, where voters give a point to a player

Point 3 @ Alesa

PIC-V-n: voters pick their n favorites from the competing photos, displayed vertically
. every vote is worth 1 point
. example:

#2
#4
#12

=> photos 2, 4 and 12 get 1 point each

PIC-H-n: voters pick their n favorites from the competing photos, displayed horizontally
. every vote is worth 1 point
. example:

12-24-3

=> photos 12, 24 and 3 get 1 point each

RATE-PHOTO: voters not only pick their favorites, they also give them points
. typically, a voter indicates which photo gets what points
. 6 points need to be given, to 3 photos
. example:

foto 1: 3 points
foto 2: 2 points
foto 5: 1 point

or

3 puntos #1
2 puntos #2
1 punto #5

. when no points indication is given, and only the photo's numbers, the script awards each vote 2 points
. when no points indication is given, and only the photo's numbers, and if the challenge definition's paramater equalWeights is set to false, the first mentioned photo gets 3 points, the second 2, and the third 1 point (only available from UCP v1.2.x)
. example:

#1
#2
#5

=> with equalWeights set to true, photos 1, 2 and 5 all get 2 points
=> with equalWeights set to false (the default), photo 1 gets 3 points, photo 2 gets 2 points, and photo 5 gets 1 point

VERTICAL: voters add 1 vote for their favorite
. voting starts with an empty list of the photo numbers:

#1 -
#2 -
#3 -
#4 -
# 5 -

. a vote for a photo increments the value for its index in the score
. example:

#1 -
#2 -1
#3 -
#4 -1+2+3
#5 -

another vote for photo 4 would give:

#1 -
#2 -1
#3 -
#4 -1+2+3+4
#5 -

VERTICAL-WEIGHTED: instead of adding 1 vote for their favorite (as in VERTICAL), voters add a weighted score for their 3 favorites; the total is given in brackets
. example:

#1)
#2) 1 (1)
#3) 2+2 (4)
#4) 3 (3)
#5) 3+1 (4)

awarding 1 point to photo 4, 2 points to photo 2, and 3 points to photo 5 would result in

#1)
#2) 1 +2 (3)
#3) 2 +2 (4)
#4) 3 +1 (4)
#5) 3 +1+3 (7)

true: entering this challenge counts toward this limit

MAY VOTE: players in this challenge can vote, but they don't have to; they should never vote on their own photos, though

MUST VOTE: players in this challenge must return to this challenge once it enters the VOTE state; typically they risk not getting their medal if they did not vote; they should never vote on their own photos, though

MAY NOT VOTE: players in this challenge are forbidden to vote in this challenge, not even against their own photo(s)

Special value: 'n/a' = not applicable; used in Chat, Showroom, Info and other non-challenge threads

Alesa Dam says:

Photo Information Box

After clicking the show information boxes in the Challenge Configuration box, an information box is drawn below each competing photo (or it may be available for non-approved entries, when the 'smart' photo information boxes option is set). It provides a means to request information about the photo, without leaving the challenge page:



Any of the info items can be checked with the corresponding button. The check all button runs all test simultaneously.



- date taken (as given by Flickr)
- public: is the photo public?
- edit: can admins/mods add comments or tags?
- views: the number of views
- comments: the number of comments
- favs: the number of persons that call this photo a favorite
- pool: is the photo already in the pool?
- awards in group: awards received in the selected group (special case: --Any--)

The photo information box uses the default values specified in the preferences.

Approve button

The Approve button adds an invisible hint (using the same technique as overrides) to indicate that someone inspected the photo for rule compliance. It contains some checksums to ensure its integrity:
- changing a photo after the approval will issue a warning that the photo has been changed
- copying the approval hint to another challenge, for the same, or another photo, will issue a warning
Both this Admin script and the user's Unified CheckPlay script (v0.9.2c and up) will show 'approved by '.

EXIF button

see EXIF data
Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 38 months ago.

Alesa Dam says:

Bump

At the top of a challenge thread page, there is a button bump this thread, which will put the challenge at the top of the Discuss page.
Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 38 months ago.

Alesa Dam says:

Pending items

The script offers the same Awards check as the photo information box:



It can help Admins/Mods to decide whether the photo is allowed in the group pool or not.
Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 38 months ago.

Alesa Dam says:

Info

The Title column on the Discuss page offers the possibility to get more information from selected challenges:


Use the checkbox in front of a challenge to select it (or use the select all, select open, select vote or unselect all links).

Press the collapse/expand button.

For each selected challenge, the information will be fetched, and some basic checking is performed. The small blue arrow on the right of the challenge name will be highlighted:
. red, if the script finds an error
. yellow, if there is an override defined in the challenge's definitions box

Click the arrow to see the information the script was able to retrieve (click it again to hide the information):

Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 25 months ago.

Alesa Dam says:

EXIF data

A click on the EXIF button on the photo information box opens a transparent window with the EXIF data of the photo:



. the taken date on the photo information box is the one reported by Flickr, and which is easy to change; the dates in the EXIF data are more likely not altered
. for challenges that have specific requirements, only available in the EXIF data, that data is now easily accessible (long exposure challenges, photos with a certain camera type or model, ...)
Originally posted 38 months ago. (permalink)
Alesa Dam edited this topic 38 months ago.

Alesa Dam says:

Bump multiple threads

The Title column on the Discuss page offers the possibility to bump selected challenges:

Use the checkbox in front of a challenge to select it (or use the select all, select open, select vote or unselect all links).

Press the bump button.

In every selected thread, the script will post an empty comment.
contact me if you want a custom bump message for your challenge group

Note:
For non-challenge groups, the script provides an input field where one can provide the message to be used. It can contain any HTML that is allowed on Flickr.

When bumping, the script tries to remove any previously posted bump messages.

If a thread was successfully bumped, it will have a green check mark in front of it.
On failure, it will have a red cross in front of it. When you hover the mouse over the red cross, you will get the reason of the failure.
Most common errors:

. This thread has been closed, so you may not post to it
When a thread is closed, no bump message can be posted.

. Error while deleting bump message
Due to connection errors, the bump message may have been posted, but the script may have been unable to remove previous bump messages.

Note: if you select reload after bumping in the preferences dialog, the page will not reload automatically if one of the bumps failed.
Originally posted 37 months ago. (permalink)
Alesa Dam edited this topic 25 months ago.

Alesa Dam says:

Voided vote

In horizontal types of voting (type HORIZONTAL or PIC-H-n), a vote will be ignored if it contains the word void.
It will also be ignored in score type RATE-PHOTO.

In vertical types of voting (type VERTICAL or PIC-V-n or VERTICAL-WEIGHTED), a vote will be marked as a voided vote when the post contains the word void.
Originally posted 37 months ago. (permalink)
Alesa Dam edited this topic 37 months ago.

Alesa Dam says:

In any type of voting, except PIC-P-n the following word(s) in the post will make the script consider the post as an example post:
. example
. sample vote
. ejemplo

In PIC-P-n, commenting on the entries is encouraged, and people often use phrases like a nice example of, which would make most votes be considered example votes.

When the first voting post contains the normal formatting for a vote, but has no real vote, it will be considered an example vote:
. in HORIZONTAL

0-0-0

#1-
#2-
#3-
#4-

5-5-5

#1-5
#2-5
#3-5
#4-5

Alesa Dam says:

Vote corrections

UNIFIED CheckPlay: Tips, Tricks and Work-arounds - vote corrections
Originally posted 37 months ago. (permalink)
Alesa Dam edited this topic 17 months ago.

Alesa Dam says:

Photo recognition

Although not really part of the Admin script, this paragraph fits better in this thread.

The tests performed on img tags are:
. src attribute: if not available, not a photo
. src attribute: if it contains the string buddyicons it is not a photo
. src attribute: if it does not contain the string static.flickr.com it is not a (Flickr) photo
. alt attribute: if it contains UCPthumbnail it is not considered a photo (used in thumbnail view, and photo information box)
. width attribute: if the width attribute is specified, and is less than 275, not a photo
. src attribute: if the src contains the Flickr codes for thumbnail size or small size version, it is not a photo
. src attribute: if the src is listed as a non-photo image in the group definitions, it is not a photo

Note: the restrictions on the width attribute can be removed if you define the challenge as an icon challenge
Originally posted 37 months ago. (permalink)
Alesa Dam edited this topic 28 months ago.

TPorter2006 says:

History - Manual Moderation:
At first, all challenge group moderation was manual.
1. Start a challenge thread with a theme and copy the rules for the challenge into the header.
2. Players would post their entries
3. A moderator would change the challenge from an Open state to a Vote state after first checking that all images submitted followed the rules. Was the player entered into too many challenges? Excluded from a challenge for being a previous winner? Did the entry fit the theme? Did they vote in the time limit allotted?
4. Players would vote in whatever format the group required. Could be 0-0-1 to cast a vote for pic #3 in a 3 pic challenge. Or 0-0-0-0-1 in a five image challenge. There were several other variants of voting styles.
5. Moderators would have to check that the voting was right. Did the player vote for more than one image? Did a vote slip in while they were voting that would get the sequence wrong? Votes would have to be corrected and sometimes whole challenges rolled back.
6. Once the voting was complete, at 5 votes or 10 votes or whatever the group rules stated, the moderator would close the thread. They would have to change the status from voting to closed and indicate the winner’s name. Checking the voting again was needed to make sure a win was properly reached. Then award the medal to the winning pic and possibly tag it as well.
7. Finally, start a new challenge thread so the whole process could repeat.
8. Each challenge group had a chat thread where players could ask questions and moderators were expected to monitor the chats and provide answers
Originally posted 33 months ago. (permalink)
TPorter2006 edited this topic 33 months ago.

Alesa Dam says:

Challenge configuration box: player voting: player participation

recap from above: Indicates if a player in this challenge may vote / must vote / may not vote in this challenge. (this has nothing to do with the almost general rule that players should vote in all VOTING challenges)

MAY VOTE: players in this challenge can vote, but they don't have to; they should never vote on their own photos, though

MUST VOTE: players in this challenge must return to this challenge once it enters the VOTE state; typically they risk not getting their medal if they did not vote; they should never vote on their own photos, though

MAY NOT VOTE: players in this challenge are forbidden to vote in this challenge, not even against their own photo(s)

Special value: 'n/a' = not applicable; used in Chat, Showroom, Info and other non-challenge threads

[Player]

Alesa Dam says:

Make multiple threads sticky

The Title column on the Discuss page offers the possibility to make selected challenges sticky:

Use the checkbox in front of a challenge to select it (or use the select all, select open, select vote or unselect all links).

Press the make sticky button.

The script will make all selected threads sticky

If a thread was successfully made sticky, it will have a green check mark in front of it.
On failure, it will have a red cross in front of it. When you hover the mouse over the red cross, you will get the reason of the failure.
Most common errors:

. You have reached the sticky threads limit
There is a maximum of 20 sticky threads for every group.

. You don't have permission to make a thread sticky
The script checks for admod privileges every 24 hours. If you were demoted from your privileges recently, the script may still provide the button(s).
Originally posted 25 months ago. (permalink)
Alesa Dam edited this topic 25 months ago.

Alesa Dam says:

Workflow

The workflow feature of the UCheckPlay admin script is only implemented for a few challenge groups.

In short, the workflow feature lets you manage a challenge thread, from start to finish, from the challenge page itself:
. change the title from OPEN to VOTE
. change the title from VOTE to CLOSED
. award medal(s), add tags, drop admin invites, ...
. start a new challenge, recycling challenge number, and theme (changeable, of course)
without leaving the challenge thread




Click the workflow button to access the different parts of the workflow. It will open a small dialog with the different steps:


The first choice allows to change the title from OPEN to VOTE, while staying on the challenge thread page.

The second choice allows to close the challenge thread. The person closing the challenge thread takes responsibility to complete the rest of the workflow.

The third choice will finalize a challenge thread (change the thread title from VOTE to CLOSED, unstickify the thread, award medals and add tags to the winning photo, and invite the winner to the group pool) without leaving the challenge thread.

With the forth choice, a new challenge can be created, based on the current challenge thread, again, without leaving the challenge thread. It will copy the challenge number (if applicable), and challenge theme into the new thread, but with a possibility the suggested default. Themes and challenge headers, will be read from specially formatted threads in the admod's backroom.

From OPEN to VOTE

The first step in the workflow is promoting the challenge from OPEN to VOTE.

If the challenge requires a certain amount of entries (the UCP script will show [Filled]), and if that amount has been reached, the first option will be enabled by default.
In any other case, this option will not be enabled. Enable it by clicking the radio button.

Click the Promote.. button to open the promotion dialog:


The script changes the title according to the group's policy: change OPEN into VOTE (in this case, the group uses TO VOTE).
One can change the provided title with the edit button at the right:


It will put the new title in a text field:


Save your changes with save button at the right:


The Promote.. dialog also has a button Check all photos. This will run the standard check on all non-approved entries. Click the link to the photo entry, and the script will take you to that entry. The Promote.. dialog will follow.

Click the SAVE button to change the title.
If there is an error, the script will show a red cross next to the new title. Hover the image to read the error.
If all went fine, the script will reload the thread, showing the new title.

Claim ownership

The second step will close the challenge thread. In order to prevent simultaneous processing of the challenge, one should claim ownership of the thread. The admod that gets to close the thread, shall complete the workflow.

If the challenge requires a certain amount of votes (the UCP script will show [Finished]), and that amount has been reached, the second option will be enabled by default.
In any other case, this option will not be enabled. Enable it by clicking the radio button.

Click the Claim ownership.. button to open the close dialog:


Click the CLOSE button to claim ownership, and take responsibility to complete the workflow.

If the challenge thread has been closed by someone else before you clicked the CLOSE button, the script will show:


If the challenge thread has not been closed between you visiting the thread, and clicking that button, the thread will be closed, and reloaded. The workflow dialog will automatically present the next step:

Finalize

The third step finalizes the challenge.

If the challenge requires a certain amount of votes (the UCP script will show [Finished]), and that amount has been reached, and the thread has been closed by yourself, the third option will be enabled by default.
In any other case, this option will not be enabled. Enable it by clicking the radio button.

Click the Finalize.. button to open the finalization dialog:



Based on the last vote, the script indicates the winner(s). If the script's decision is in error, choose the winner(s) yourself.

The script changes the title according to the group's policy: change VOTE into CLOSED (some groups use AWARDED, or something else). There is support to include the winner's name in the new title (if there are multiple winners, their names will be separated with - and -). The proposed title can be changed with the edit button (see also above).

A list of medals is read from a specially formatted thread (typically in the admods' backroom). Each medal comes with tags (optional) and an invitation for the group pool (optional, multiple group pools supported).

The tags and invite group ids can be changed, or added manually with the edit button (see also above).

When medals are also awarded to the runner up (e.g. runner up medal in Faves Contest, CY-niner in Challenge You, ...), select the award second place checkbox. That will provide a similar player list to allow the posting of a runner up medal. Similar for third place.

The award second place/medal can also be used to provide multiple medals to the winner: the photo gets a regular medal, next to a sweep medal, for example. The script does not care for first vs. second vs. third place or medal. It only uses the winner(s) list to fill in the title.

Click the SAVE button to
. change the challenge title
. close the thread
. remove the stickiness from the thread
. post the selected medal(s) to the winner/second/third
. post the selected tags(s) to the winner/second/third
. post the selected admin invite(s) to the winner/second/third

If one of the actions errors out, the script will report with a red cross. Hover the image to see the error.
If all is fine, the script will reload the page.

Create new challenge

The last step in the workflow is creating a new challenge out of a closed one.

If the challenge is CLOSED, and you closed the thread yourself, the forth option will be enabled by default.
In any other case, this option will not be enabled. Enable it by clicking the radio button.

Click the Create.. button to open the creation dialog:


The script automatically uses the same number and theme as the current challenge. This title can be changed
. with the edit button (see also above)
. with the theme list (which is read from a specially formatted thread)
. with a fixed theme assigned to a challenge header chosen from the list

On selecting a predefined header, its content is copied into the new header which will be used as the opening comment of the new challenge:

This header can be edited using the edit button (see also above)

The script supports templates for the name of the winner in this challenge (its name, photo title, and photo page url). They are filled in when selecting the player in the winner(s) list. (support for this data for second and third place will be added in future versions).

Click the SAVE button to create a new challenge:
. with the given title
. with the given header
. and made sticky (if selected)

If the script is unable to create the challenge, or it can not make the new challenge sticky, it will report with a red cross. Hover your mouse over the image to read the error.
A link to the newly created challenge is provided at the bottom of the creation dialog.
Originally posted 25 months ago. (permalink)
Alesa Dam edited this topic 11 months ago.

Alesa Dam says:

Formatting for the workflow feature

the medals

The script needs to know about the thread were the medals are defined. This thread typically resides in the group's backroom, accessible to the group's admods. The thread header is skipped, and can be used to clarify about the formatting.
Each comment in the thread is parsed with these tags

===Start of Title===
Monthly Icon Medal
===End of Title===
===Start of Medal===
Congratulations! You have won our Monthly Icon Challenge!

You are welcome to post this image in the group pool
===End of Medal===
===Start of Referrer===
===End of Referrer===
===Start of Tag===
"Monthly Icon Winner"
===End of Tag===
===Start of GroupID===
===End of GroupID===

...
===Start of Referrer===
---
You have won our <a href="%__referrer__url__%">%__referrer__theme__%</a> challenge!
===End of Referrer===
...

---
You have won our Monthly Icon challenge!

===Start of theme list===
Anything goes!
Bird in flight
...
===End of theme list===

===Start of Title===
Monthly Icon Challenge
===End of Title===
===Start of Header===
Rules of the Monthly Icon Challenge:
1...
===End of Header===
===Start of Theme===
00 - OPEN - Monthly Icon Challenge
===End of Theme===

...
===Start of Header===
...
The last one to win this Monthly Icon Challenge was <b>%__previousWinner__name__%</b> with "%__previousWinner__title__%":
[%__previousWinner__url__%]
===End of Header===
...

...
The last one to win this Monthly Icon Challenge was Alesa Dam with "Candle Light":

Alesa Dam says:

Challenge Cross-Inspection

In the title row of the Challenge table on the group's Discuss page, there is a new button next to the make sticky, bump, and expand/collapse button: cross-inspect. This button will open a dialog above the challenge list.

When opening, it will read in the selected challenge threads, and collect most of the necessary information (photo entries and votes, mainly).

Once the script has that information it will provide the following checks:
• check the challenge numbering / challenge name format
• check for similar themes
• count player entries
• check for photos that are participating in multiple challenges
• check for players that did not vote

For each available check, you have an option on when to run it:
• always run the check
 the check is always performed when you open the Cross-Inspect dialog
• never run the check
 the check will only be run if you click it yourself
• only run the check in auto-mode
 the check is performed only when you open the Cross-Inspect dialog with no challenges selected

• Caveats!

Click the arrow (or the line itself) to start the given check.

check the challenge numbering

This check will list the selected challenges sorted by their challenge number.
Double numbering will be colored red; missing numbers are listed at the bottom.

The script will need a regular expression to extract the challenge number. Here are some examples:

• You Rock!

05 - OPEN - Theme: Bird/s
06 - TO VOTE - Theme: Musician/s
...

The regular expression would be
 ^(\d{2})

Which denotes:
 ^ : "starts with"
 \d{2} : "two digits"
 (..) : extracts the number

#10 ~OPEN~ MEGA Challenge!
#9 ~VOTE~ Sweeps!Challenge
...

Regular expression would be
 ^#(\d{1,2})

Which denotes:
 ^# : "starts with '#'"
 \d{1,2} : min. one digit, max. two digits
 (..) : extracts the number

Bridge
Bridge/s
Bridge(s)
Bridging
 should all be reported as equal

bridge
Bridge
BRIDGE
 should all be reported as equal

This is not a check on the group limit!!
In a future version, the script will take the group limit into account (if applicable), and will even distinguish between different limits (per challenge category, for example), if your group has those.

output

• exact matches will be colored red
(a match is considered exact if the script was able to parse both required timestamps: "edited this topic xx minutes ago", for the change to VOTE, and "Posted xx minutes ago", for the challenge entry)

• "--none found--"
this means that every participant in any of the selected OPEN challenges is participating, or has voted, in any of the selected VOTE challenges

• "--no violators found--"
this means there might be participants that have not voted yet, but they still have time left to do so, or they have posted their entry prior to the challenges changing to VOTE