Hello Licensing Junior Staff, and welcome to the 5 Images a Day Initiative! This Initiative intends to bring the entire SCP wiki under compliance with CC BY-SA 3.0 in a short time frame while also not taxing one individual too hard. There is a method to it that is very detailed, but by reading this guide, you’ll be able to comprehend it and apply it in your actions.
First, let me introduce you to the Tag Search tool. You'll come to be familiar with this tool as it will be the primary means of finding articles with unchecked images. All articles with unchecked images have the _image tag. We'll be working from most recent articles to least recent articles, so type "_image" into the Select tags bar, and sort by "Creation Date Descending".
Now that you've chosen an article, place a link to the article in the table below under "Article". The point of the table is so everyone knows if an article has been sourced or not, to make sure an article isn't sourced twice. Once you've placed a link, put your name under "Sourcer" as well. Now it's time to get into the article. Scan the article for images, see how many images are there, and look into the discussion page. If the image(s) is sourced somewhere in the discussion page and is cc-compliant, replace the _image tag with the _cc and put a link to the comment sourcing the image(s) in the table under "Source". Afterward, simply move on to the next article. If there's a source for the image and it isn't cc-compliant, well, you'll see later.
Now that you've chosen an article to source, check the author of the article. First, see if they're active. By active, I mean they've made at least one edit or post in the last month. To do this, check their Wikidot account for Recent Contributions and Recent Posts and Discussion. You should also check if the author is active on Discord, IRC, Twitter, or other social media/communication outlets, which would also count as being active. At this point, you're path will branch into multiple different paths, which I've laid out below.
Author is inactive, image is sourced and non-compliant:
This is the easiest of the procedures. Simply remove the image block from the source code of the article, leaving a comment such as "Image is non-compliant" or "Images are non-compliant". Afterward, leave a comment responding to the discussion post with the title "Junior Staff Post" and the following statement:
"This image is non-compliant because [Insert reasoning for why the image is non-compliant here]. As such, the image has been removed."
Afterward, leave a link to the comment sourcing the image on the table under "Source", and move on to the next article.
Author is inactive, image is unsourced:
This is where you'll truly enter the Wild West on the internet. At the point, there are three tools that I use. First, I use Google Reverse Image Search. Right click the image and select "Search Google for image". At this point, you may receive a lot of results or very little results.
If there's a lot of results, just skim the results of the first couple of pages. If you can't find anything useful, then move on to the next tool. If there's not a lot of results, just click through all the results there are. Avoid links that're SCP related, as they don't provide any help. Sometimes you'll find the source of the image via the direct Google results, which is great. Sometimes, however, you'll need to click through other pages to find the source. News articles often contain the sources, but you may have little luck in your endeavors. If you have no luck, then again, move on to the next tool.
The next tool is the infamous TinEye. To use this tool, copy the image URL, and Sort by oldest. Like Google Reverse Image Search, you may receive a little or a lot of results. Just go through the results and see if you can find anything.
If you don't find anything via TinEye, the last resort is using Yandex's Reverse Image Search. Simply click the Camera icon, paste in the image link, and search it up. Hopefully, it should be there.
If you find the source and it is cc-compliant, leave a post on the discussion page of the article with the title "Junior Staff Post" and the statement "This image comes from [Insert source of image here] and is cc-compliant with the SCP wiki's license (CC BY-SA 3.0)." Then, replace the _image tag with the _cc and move on.
If the source isn't cc-compliant, or you can't find a source to the image, remove the image block from the source code of the article and leave this comment:
"This/these image(s) is/are is non-compliant because [Insert reasoning for why the image(s) is non-compliant here]. As such, the image has been removed."
In both cases, leave a link to your comment in the table under "Source" and move on to the next article.
Author is active:
First, see if the author has written any other articles with the _image tag. To do this, we'll again use the Tag Search tool. Type in "_image" and sort by "Author Name Ascending". Scroll down or f3 to find the article, and see if there are other articles by the same author. If there aren't, focus on those articles. This is so we won't be sending multiple requests for sources to the same author, instead sending one big PM with all the sources they need to provide.
If the author has multiple unsourced images, send them the "Multiple Images Unsourced" Format that you'll find in the collapsible below this. If the author has one unsourced image, send them the "One Image Unsourced" Format. After you send the PM, put the source on the table as "Pending". If a week passes with no response, or you receive a response where the author doesn't remember the source and doesn't provide a replacement, follow the "Inactive author, image is unsourced" procedure.
If the author responds in a week and provides a source that's cc-compliant, then add a post in the discussion page with the source and replace the _image tag with the _cc tag. If the source they provide is non-compliant, then remove the image block from the source code, leave a comment on the discussion with the source and why it's non-compliant, and send a PM back with the "Image Sourced is Non-Compliant" format.
If you have any questions on this process, please contact Elogee FishTruck via Wikidot PM or (preferably) IRC via .tell (my IRC nickname is "elogee").
Modern_Erasmus if non-compliant)
