The bulk update request #1203 is active.

create implication meat_grinder (57) -> shredder_(machine) (94)
create implication woodchipper (13) -> shredder_(machine) (94)
create implication industrial_shredder (13) -> shredder_(machine) (94)
create implication food_processor (1) -> shredder_(machine) (94)
create implication paper_shredder (11) -> shredder_(machine) (94)
create implication shredder_(machine) (94) -> machine (114597)

Reason: I noticed there seemed to be bits of confusion regarding machinery tagging for some gore/peril types, so here's an umbrella tag and implication back to machinery

Edit: Added paper_shredder implying shredder_(machine).

EDIT: The bulk update request #1203 (forum #315047) has been approved by @slyroon.

The bulk update request #1204 is active.

mass update shredder -> shredder_(tmnt)
remove implication shredder (0) -> teenage_mutant_ninja_turtles (6522)
create alias shredder_(teenage_mutant_ninja_turtles) (0) -> shredder_(tmnt) (47)
create implication shredder_(tmnt) (47) -> teenage_mutant_ninja_turtles (6522)

Reason: Still Shredder content.

EDIT: The bulk update request #1204 (forum #315077) has been approved by @slyroon.

create alias shredder -> shredder_(disambiguation) # duplicate of has blocking transitive relationships, cannot be applied through BUR

This line will have to be left to another BUR, or else the error will cause the whole script to fail.

gattonero2001 said:
This line will have to be left to another BUR, or else the error will cause the whole script to fail.

What exactly is the issue? (for avoidance of it in any other scenarios) And do you mean it'd work if simply removed from that BUR and placed in another?
Edit: Realized that's not to me, but my question is still relevant

tabbyseraph said:
What exactly is the issue? (for avoidance of it in any other scenarios) And do you mean it'd work if simply removed from that BUR and placed in another?
Edit: Realized that's not to me, but my question is still relevant

"duplicate of has blocking transitive relationships" means that, since shredder has an active implication to another tag, it cannot be aliased. After Furrin's BUR is approved, that relationship will no longer be active and the alias will no longer be blocked. However, as long as the implication is still active, any BUR containing a similar line will fail.

The bulk update request #1207 has been rejected.

create alias shred (0) -> shred_(disambiguation) (0)
create alias shredder (0) -> shred_(disambiguation) (0)
create alias shredding (4) -> shred_(disambiguation) (0)
create alias shredded (5) -> shred_(disambiguation) (0)
create alias shredded_clothes (0) -> torn_clothing (68471)
create alias shredded_clothing (0) -> torn_clothing (68471)
create alias clothing_shredding (0) -> tearing_clothing (1207)

Reason: Following up on Furrin's BUR above (aside from alias shredder -> shredder_(disambiguation)), I've found a small web of tag misapplication within tags using shred*, so here's another little BUR cleaning all that into a single disambiguation tag (featuring some torn_clothing aliases), and there's now a shred_(disambiguation) wiki page.

EDIT: The bulk update request #1207 (forum #315104) has been rejected by @TabbySeraph.

EDIT: The bulk update request #1207 (forum #315104) has failed: Error: Antecedent name has already been taken (create alias shredded -> shred_(disambiguation))

tabbyseraph said:
The bulk update request #1207 has been rejected.

create alias shred (0) -> shred_(disambiguation) (0)
create alias shredder (0) -> shred_(disambiguation) (0)
create alias shredding (4) -> shred_(disambiguation) (0)
create alias shredded (5) -> shred_(disambiguation) (0)
create alias shredded_clothes (0) -> torn_clothing (68471)
create alias shredded_clothing (0) -> torn_clothing (68471)
create alias clothing_shredding (0) -> tearing_clothing (1207)

Reason: Following up on Furrin's BUR above (aside from alias shredder -> shredder_(disambiguation)), I've found a small web of tag misapplication within tags using shred*, so here's another little BUR cleaning all that into a single disambiguation tag (featuring some torn_clothing aliases), and there's now a shred_(disambiguation) wiki page.

Seems fine, except I think it should be shredder -> shredder_(disambiguation) instead, since it can be referring to the character.

scaliespe said:
Seems fine, except I think it should be shredder -> shredder_(disambiguation) instead, since it can be referring to the character.

If my BUR gets approved first, I've removed that alias from it, and mine will unimplicate it from the copyright so that the alias can be approved in Tabby's BUR. It "might be the character," but it might not be. Aliasing to the character would be silly. Putting it in as a disambiguation makes it an easy enough fix without needing to remove a copyright tag somebody might not have noticed.

furrin_gok said:
It "might be the character," but it might not be. Aliasing to the character would be silly. Putting it in as a disambiguation makes it an easy enough fix without needing to remove a copyright tag somebody might not have noticed.

I think they mean aliasing shredder to shredder_(disambiguation), instead of shred_(disambiguation). Shred and Shredder have two different sets of possibilities (shred is an adjective or verb, meaning a torn pieces of something, a small piece of something, or the act of ripping something apart; while shredder is a noun, which can refer to various things like a wood chipper, juice mixer, cheese grater, or be a certain character's name), so it doesn't make much sense to have both shred and shredder aliased to the same disambiguation.

watsit said:
I think they mean aliasing shredder to shredder_(disambiguation), instead of shred_(disambiguation). Shred and Shredder have two different sets of possibilities (shred is an adjective or verb, meaning a torn pieces of something, a small piece of something, or the act of ripping something apart; while shredder is a noun, which can refer to various things like a wood chipper, juice mixer, cheese grater, or be a certain character's name), so it doesn't make much sense to have both shred and shredder aliased to the same disambiguation.

Yeah, this.

The bulk update request #1207 (forum #315104) has been rejected by @TabbySeraph.

The bulk update request #1212 is active.

create alias shredded_clothes (0) -> torn_clothing (68471)
create alias shredded_clothing (0) -> torn_clothing (68471)
create alias clothing_shredding (0) -> tearing_clothing (1207)

Reason: Reconsidered with the above comments and the infrequency of shred/shredding being used on their own, so here's an altered version of the followup to Furrin's BUR now using shredder_(disambiguation), plus shredded moved directly to muscular. (shredded -> muscular alias removed due to debate, while the rest should have no issues)

EDIT: The bulk update request #1212 (forum #315195) has been approved by @slyroon.

tabbyseraph said:
create alias shredded -> muscular

Shredded should probably go to shred_(disambiguation), since it can refer to shredded paper, clothes, etc, along with being a colloquialism for being muscular.

watsit said:
Shredded should probably go to shred_(disambiguation), since it can refer to shredded paper, clothes, etc, along with being a colloquialism for being muscular.

Shredded itself has been exclusively used for muscular characters as far as I can tell; tagging for shredded things tends to come in the form of shredded_[object], hence the aliases to torn_clothing in the lines above that. Would it be worth putting through a disambiguation tag regardless?

I’m generally in favor of direct aliases as opposed to disambiguations whenever possible, as it seems most of these disambiguations never get cleaned up, and we have enough tagging projects as it is. If it turns out that everyone who uses shredded with the intent of muscular, I would tend to think a direct alias may be preferable.

tabbyseraph said:
Shredded itself has been exclusively used for muscular characters as far as I can tell; tagging for shredded things tends to come in the form of shredded_[object], hence the aliases to torn_clothing in the lines above that. Would it be worth putting through a disambiguation tag regardless?

I would say yes. "Muscular" isn't the first thing I thought of with "shredded", and there were a few times it was used to mean something else.

tabbyseraph said:
The bulk update request #1212 is active.

create alias shredded_clothes (0) -> torn_clothing (68471)
create alias shredded_clothing (0) -> torn_clothing (68471)
create alias clothing_shredding (0) -> tearing_clothing (1207)

Reason: Reconsidered with the above comments and the infrequency of shred/shredding being used on their own, so here's an altered version of the followup to Furrin's BUR now using shredder_(disambiguation), plus shredded moved directly to muscular. (shredded -> muscular alias removed due to debate, while the rest should have no issues)

Did you hit the wrong button or not realize that there was an option to edit the implication, or was this meant to be an alternative for vote? forum #315104 was rejected now, but I'm wondering why a second "after mine" showed up.

furrin_gok said:
Did you hit the wrong button or not realize that there was an option to edit the implication, or was this meant to be an alternative for vote? forum #315104 was rejected now, but I'm wondering why a second "after mine" showed up.

I'm aware of the option; I'm honestly not sure why I didn't just edit it rather than rejecting and making a new one

The bulk update request #1203 (forum #315047) has been approved by @slyroon.

The bulk update request #1204 (forum #315077) has been approved by @slyroon.

The bulk update request #1207 (forum #315104) has failed: Error: Antecedent name has already been taken (create alias shredded -> shred_(disambiguation))

The bulk update request #1212 (forum #315195) has been approved by @slyroon.