The bulk update request #2880 is active.

Reason: Copyright (Jewelpet belongs to both Sanrio and Sega)
Also filling in the remaining pets' implications, something our wiki page outright said to do.

Please add suggestions if anything more needs done

EDIT: The bulk update request #2880 (forum #340253) has been approved by @Rainbow_Dash.

There are other characters tagged with ryl, sapphie and titana: ~sapphie ~ryl ~titana -jewelpet . Those tags should be cleared up and given _(jewelpet) suffix.

Same for rald, larimar and chite (chite lol). While currently only jewelpets can be found there, it's not inconcievable that someone else will name their character with one of those.

Update: fixed ryl_(jewelpet), titana_(jewelpet), rald_(jewelpet), larimar_(jewelpet) and chite_(jewelpet).
It should be safe to mass update sapphie -> sapphie_(jewelpet) as well.

You missed avenue_(jewelpet).

Also, jewelpet wiki should have suffixed names in plain list instead of table to make copy-pasting easier and prevent future mistaggings.

waydence said:
Update: fixed ryl_(jewelpet), titana_(jewelpet), rald_(jewelpet), larimar_(jewelpet) and chite_(jewelpet).
It should be safe to mass update sapphie -> sapphie_(jewelpet) as well.

You missed avenue_(jewelpet).

Also, jewelpet wiki should have suffixed names in plain list instead of table to make copy-pasting easier and prevent future mistaggings.

Updated.
I had misgivings about Sapphie (name isn't as common as Ruby), but it makes sense for consistency's sake (to be fair, The wiki page doesn't have Avenue either)
I also see the others have aliases of the gems themselves, but the remaining ones wouldn't fit in this BUR. "Charlotte" is just (understandably) a misinterpretation of the name I see a lot (Like in the subs for the movie)

glyme said:
create alias sapphie (144) -> sapphie_(jewelpet) (0)

You shouldn't alias ambiguous names to a specific character like that. If sapphie is ambiguous, the posts need to the tag to be changed to the correct character manually, and it needs to be aliased to sapphie_(disambiguation), which also needs to be set to the Invalid category. i.e.

alias sapphie -> sapphie_(disambiguation)
category sapphie_(disambiguation) -> invalid

watsit said:
You shouldn't alias ambiguous names to a specific character like that. If sapphie is ambiguous, the posts need to the tag to be changed to the correct character manually, and it needs to be aliased to sapphie_(disambiguation), which also needs to be set to the Invalid category. i.e.

alias sapphie -> sapphie_(disambiguation)
category sapphie_(disambiguation) -> invalid

Does mass update work? Or would this require a piece-by-piece check?
Is updating and invalidating allowed at the same time?

glyme said:
Does mass update work? Or would this require a piece-by-piece check?

It will need some piece-by-piece checking. But if the majority of uses are for the Jewelpet character, and you endeavor to keep the tag clear of uses that aren't of that character, you can use a mass update to move the remaining uses.

glyme said:
Is updating and invalidating allowed at the same time?

No, because the order of operations for a BUR are undefined. If you do both update sapphie -> sapphie_(jewelpet) and alias sapphie -> sapphie_(disambiguation) in the same BUR, the alias could happen first so they all end up in sapphie_(disambiguation) and the update doesn't move anything to sapphie_(jewelpet) (or they could happen at the same time, so some end up in sapphie_(jewelpet) from the update and others end up in sapphie_(disambiguation) from the alias).

watsit said:
It will need some piece-by-piece checking. But if the majority of uses are for the Jewelpet character, and you endeavor to keep the tag clear of uses that aren't of that character, you can use a mass update to move the remaining uses.

No, because the order of operations for a BUR are undefined. If you do both update sapphie -> sapphie_(jewelpet) and alias sapphie -> sapphie_(disambiguation) in the same BUR, the alias could happen first so they all end up in sapphie_(disambiguation) and the update doesn't move anything to sapphie_(jewelpet) (or they could happen at the same time, so some end up in sapphie_(jewelpet) from the update and others end up in sapphie_(disambiguation) from the alias).

OK, I did a look through of Sapphie and only found one pic that wasn't her. Changed its tags.
I think we're good to go now.

Is having one other character named sapphie really worth a disambiguation? This seems extremely unnecessary. I am in favor of aliasing to the more prominent usage.

The bulk update request #2880 (forum #340253) has been approved by @Rainbow_Dash.