View Single Post
Old 02-04-2021, 01:56 PM   #5361
ownedbycats
Custom User Title
ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.
 
ownedbycats's Avatar
 
Posts: 11,110
Karma: 77213681
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
Quote:
Originally Posted by ownedbycats View Post
Also, as expected, it did result in some weird behaviour on crossovers: it added both prefixes to all the characters. Any idea how to handle this?

This is my best idea so far:

Code:
characterlist=>(Character1|Character2)=>Fandom1.\1&&category==Crossover
characterlist=>(Character3|Character4)=>Fandom2.\1&&category==Crossover
EDIT: I made it worse!

Attachment 185218
I thought that perhaps an exclude metadata would work, but halfway through adding it I realized it would just strip the characters entirely. Still a little stumped.

I guess I could just set the column as new only and manually sort it out.

EDIT: For now, I just disabled all the prefixes and am focusing on sorting out all the standardization.

Last edited by ownedbycats; 02-04-2021 at 03:23 PM.
ownedbycats is offline   Reply With Quote