The bulk update request #2619 has been rejected.

create implication sibling (0) -> relatives_(lore) (0)
create implication parent (0) -> relatives_(lore) (0)
create implication grandparent (0) -> relatives_(lore) (0)
create implication cousins (0) -> relatives_(lore) (0)
create implication son_(lore) (24325) -> relatives_(lore) (0)
create implication daughter_(lore) (15332) -> relatives_(lore) (0)
create implication aunt (0) -> relatives_(lore) (0)
create implication uncle (0) -> relatives_(lore) (0)
create implication niece (0) -> relatives_(lore) (0)
create implication nephew (0) -> relatives_(lore) (0)
change category relatives_(lore) (0) -> lore

Reason: Have you ever just wanted to see posts with family in general, and not necessarily as specific as a particular paring?

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

still a bit weird to me that all of the familial relation tags are not lore tags, honestly.

versperus said:
The bulk update request #2619 has been rejected.

create implication sibling (0) -> relatives_(lore) (0)
create implication parent (0) -> relatives_(lore) (0)
create implication grandparent (0) -> relatives_(lore) (0)
create implication cousins (0) -> relatives_(lore) (0)
create implication son_(lore) (24325) -> relatives_(lore) (0)
create implication daughter_(lore) (15332) -> relatives_(lore) (0)
create implication aunt (0) -> relatives_(lore) (0)
create implication uncle (0) -> relatives_(lore) (0)
create implication niece (0) -> relatives_(lore) (0)
create implication nephew (0) -> relatives_(lore) (0)
change category relatives_(lore) (0) -> lore

Reason: Have you ever just wanted to see posts with family in general, and not necessarily as specific as a particular paring?

Aren't lore tags in the meta category and not their own?

According to this thread, you need an admin to manually create the lore tag, it can't be handled through BURs?

furrin_gok said:
According to this thread, you need an admin to manually create the lore tag, it can't be handled through BURs?

It seems that way, I figure an admin can do their thing to make it work even it says it won't work right now.

darryus said:
still a bit weird to me that all of the familial relation tags are not lore tags, honestly.

I assume it's in part due to the fact that it would require moving a bunch of tags around with removing implications and aliases to *_(lore) tags (which I think is mandatory for lore tags?) which, if that's the case it would be a major pain in the ass.

darryus said:
still a bit weird to me that all of the familial relation tags are not lore tags, honestly.

Yes, this really needs to be done. Unfortunately it requires a huge number of aliases and implications to be undone and remade, which is infuriatingly difficult to do with BURs, and even worse since they limited BURs to only 10 tags at a time.

For example, aliasing grandparent_and_grandchild to grandparent_and_grandchild_(lore) would require a total of 24 BURs alone.

wat8548 said:
and even worse since they limited BURs to only 10 tags at a time.

10? I thought it was 25?

wat8548 said:
Yes, this really needs to be done. Unfortunately it requires a huge number of aliases and implications to be undone and remade, which is infuriatingly difficult to do with BURs, and even worse since they limited BURs to only 10 tags at a time.

For example, aliasing grandparent_and_grandchild to grandparent_and_grandchild_(lore) would require a total of 24 BURs alone.

10? Not much of a bulk if you ask me, i expected it to have no limits honestly, why have it so low?

benjiboyo said:
10? Not much of a bulk if you ask me, i expected it to have no limits honestly, why have it so low?

I'm assuming because BURs need to be verified by a human and having to go through a 200 tag BUR for mistakes is daunting as all hell

versperus said:
I'm assuming because BURs need to be verified by a human and having to go through a 200 tag BUR for mistakes is daunting as all hell

Allright, hundreds definitely is overkill, maybe 50 even. But 10 definitely feels really low.

benjiboyo said:
Allright, hundreds definitely is overkill, maybe 50 even. But 10 definitely feels really low.

Last I checked, it was 25, not 10.

I thought it was to not overstress the system with processing too many requests all at once.

Whether it's 25 or 10, we're still talking about a number of BURs in the double digits (at least) to undo and redo everything necessary. That's just one reason why it hasn't been done yet.

The bulk update request #2634 has been rejected.

remove implication mother_and_son (0) -> son (0)
remove implication father_and_son (0) -> son (0)
create implication mother_and_son_(lore) (12387) -> son_(lore) (24325)
create implication father_and_son_(lore) (11435) -> son_(lore) (24325)
mass update father_and_son -> father_and_son_(lore)
mass update mother_and_son -> mother_and_son_(lore)
mass update son -> son_(lore)
change category father_and_son_(lore) (11435) -> lore
change category mother_and_son_(lore) (12387) -> lore
change category son_(lore) (24325) -> lore

Reason: Lore tag updating

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

The bulk update request #2635 has been rejected.

create alias mother_and_son (0) -> mother_and_son_(lore) (12387)
create alias father_and_son (0) -> father_and_son_(lore) (11435)
create alias son (0) -> son_(lore) (24325)

Reason: lore bur update

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

The bulk update request #2636 has been rejected.

remove alias mother/son (0) -> mother_and_son (0)
remove alias son/mother (0) -> mother_and_son (0)
remove alias son_and_mother (0) -> mother_and_son (0)
remove implication mother_and_son (0) -> son (0)
remove implication mother_and_son (0) -> mother_and_child (0)
mass update mother_and_son -> mother_and_son_(lore)

Reason: Mother/son -> Lore update

Part 2
alias mother/son -> mother_and_son_(lore)
alias son/mother -> mother_and_son_(lore)
alias son_and_mother -> mother_and_son_(lore)
imply mother_and_son_(lore) -> son_(lore)

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

The bulk update request #2637 is active.

mass update father_and_daughter -> father_and_daughter_(lore)
mass update mother_and_daughter -> mother_and_daughter_(lore)
mass update daughter -> daughter_(lore)
change category father_and_daughter_(lore) (7015) -> lore
change category mother_and_daughter_(lore) (9491) -> lore
change category daughter_(lore) (15332) -> lore

Reason: Daughter lore updating

Part 2
alias mother_and_daughter -> mother_and_daughter_(lore)
alias father_and_daughter -> father_and_daughter_(lore)
alias daughter -> daughter_(lore)

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

The bulk update request #2638 has been rejected.

remove alias mother/daughter (0) -> mother_and_daughter (0)
remove alias daughter/mother (0) -> mother_and_daughter (0)
remove alias daughter_and_mother (0) -> mother_and_daughter (0)
remove implication mother_and_daughter (0) -> daughter (0)
remove implication mother_and_daughter (0) -> mother_and_child (0)
mass update mother_and_daughter -> mother_and_daughter_(lore)

Reason: Reason: Mother/Daughter -> Lore update

Part 2
alias mother/daughter -> mother_and_daughter_(lore)
alias daughter/mother -> mother_and_daughter_(lore)
alias daughter_and_mother -> mother_and_daughter_(lore)
imply mother_and_daughter_(lore) -> daughter_(lore)

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

The bulk update request #2638 (forum #337619) has been rejected by @slyroon.

The bulk update request #2637 (forum #337618) has been approved by @slyroon.

The bulk update request #2636 (forum #337617) has been rejected by @slyroon.

The bulk update request #2635 (forum #337616) has been rejected by @slyroon.

The bulk update request #2634 (forum #337615) has been rejected by @slyroon.

The bulk update request #2619 (forum #337394) has been rejected by @slyroon.