The bulk update request #6350 has been rejected.

remove implication minotaur (5871) -> greek_mythology (22795)
remove implication minotaur (5871) -> bovine (71339)
create implication minotaur (5871) -> minotaur_(lore) (0)
create implication bovine (71339) -> minotaur_(lore) (0)
create implication greek_mythology (22795) -> minotaur_(lore) (0)

Reason: With specificity between the two being so hazy.
These being Minotaurs
post #4223712 |post #2793794

And These Aren't
post #4571955 |post #4561720

Why not simplify and make it so that the minotaur are minotaur when the artist says they are?
Reduces the tags turning into an Assassination Classroom style Fight for who is right
and allows for more creative say for the peeps making the piece.

If they say it isn't, it isn't.
If they say it is, it is, Dood.
╹‿╹)~★

EDIT: The bulk update request #6350 (forum #388746) has been rejected by @slyroon.

Kk, I did not know you had to remove the implications before aliasing, My Bad!
Plan, Move the current implications to lore and aliase once everything is set
and done, Dood ◠‿╹)~★

This doesn't really match what lore tags are for (at least in my opinion). I could see it possibly being aliased to bovine or something though

I'm not sure species tags are appropriate for lore purposes. Same with demons on e6, species imo can already be twyk rather than twys

definitelynotafurry4 said:
I'm not sure species tags are appropriate for lore purposes. Same with demons on e6, species imo can already be twyk rather than twys

True

species tags, and especially fictional species tags, are already tagged on a heavily TWYK standard. I don't really see gow this change would help anything.

The bulk update request #6350 (forum #388746) has been rejected by @slyroon.