This is a short guide on how to prep "bad shells" on site for ShellPageBot to fix them.Quick Fix1. Replace the lyrics with the following phrase.
Page needs help... Paging ShellPageBot
2. Message Daktar with a link to the user who created the song. I will do an in-depth search of the other transcriptions for the user to find additional 'bad shells'.
3. Send message to user alerting them how to correctly create 'shells'.
Example:
Please do not create songs with lyrics such as "Lyrics not available, no lyrics, etc."
Please check out this page for more information.In-depth Fix1. Replace the lyrics with the following phrase.
Page needs help... Paging ShellPageBot
2. Look in Contributions to see who created the song.2a. There are some cases where another user edited the lyrics after creation, if you see this, then you are done.
3. Open page of the user who created the page and manually go through their transcriptions to see if they created other shells.
Helpful Addons
• Firefox: Snap Links
• Chrome: Linkclump
4. Send message to user alerting them how to correctly create 'shells'.
Example:
Please do not create songs with lyrics such as "Lyrics not available, no lyrics, etc."
Please check out this page for more information.Q+AWhy would you use an indepth search of a users transcriptions to find 'bad shells'?
There are certain phrases that users use to create bad shells that cannot be searched for such as "[?]", "the song name", "headers". We can find these oddities by going through the transcriptions manually.
Wouldn't search work for this?
Sadly, after a certain point, the search on site seems to bug and not return further results even when there are still pages on site. I have reported this to Tech but unsure of how soon it will be fixed.
How often is ShellPageBot ran?
Every 15 minutes.If you want, you can also use some of the pre-saved searches here to possibly find more "bad shells."
Warning: There will be scrolling involved and search is a bit wonky at times and will not show all instances on site. Getting creative might work better by taking a couple keywords from the longer phrases and just searching those.
Page needs help... Paging ShellPageBot
2. Message Daktar with a link to the user who created the song. I will do an in-depth search of the other transcriptions for the user to find additional 'bad shells'.
3. Send message to user alerting them how to correctly create 'shells'.
Example:
Please do not create songs with lyrics such as "Lyrics not available, no lyrics, etc."
Please check out this page for more information.In-depth Fix1. Replace the lyrics with the following phrase.
Page needs help... Paging ShellPageBot
2. Look in Contributions to see who created the song.2a. There are some cases where another user edited the lyrics after creation, if you see this, then you are done.
3. Open page of the user who created the page and manually go through their transcriptions to see if they created other shells.
Helpful Addons
• Firefox: Snap Links
• Chrome: Linkclump
4. Send message to user alerting them how to correctly create 'shells'.
Example:
Please do not create songs with lyrics such as "Lyrics not available, no lyrics, etc."
Please check out this page for more information.Q+AWhy would you use an indepth search of a users transcriptions to find 'bad shells'?
There are certain phrases that users use to create bad shells that cannot be searched for such as "[?]", "the song name", "headers". We can find these oddities by going through the transcriptions manually.
Wouldn't search work for this?
Sadly, after a certain point, the search on site seems to bug and not return further results even when there are still pages on site. I have reported this to Tech but unsure of how soon it will be fixed.
How often is ShellPageBot ran?
Every 15 minutes.If you want, you can also use some of the pre-saved searches here to possibly find more "bad shells."
Warning: There will be scrolling involved and search is a bit wonky at times and will not show all instances on site. Getting creative might work better by taking a couple keywords from the longer phrases and just searching those.
Comments (0)
The minimum comment length is 50 characters.