Well, I was going to say "hold off on that" but... As it happens, there
seem to be only 2 ways to fix the rearrangement of recipients, which are
greatly and fairly undesirable, respectively. Plus now that folks are
already posting their works, I think I've cut off the path to one fix (at
least without making it way too difficult for participants, who we don't
want to irritate, to keep people willing to participate for future
dSSSes)...
But I had not considered the simple solution you've suggested! (Which seems
so obvious I'm embarrassed I didn't think of it already. Duh...) You must
run some other challenges, lol!
:-)
Anyway, would you be willing to be an experimental subject, lol? Would you
consider doing what you just described, as an experiment, & I'll see how it
looks on our end?
If it looks like it came out wrong or weird on our side, we can always
delete it. If not, we can tell other people to do what you did! :-)
Although I guess we wouldn't really know until the collection opens Dec. 24
at 23:59...
Here's the complete back story... The two ways of doing this are:
1 was "purge ALL dSSS assignments (saving a record of the originals first,
of course, so everyone else can be reassigned there original recipient) and
reassign manually." But I can't do that now because people have already
submitted works... So already-submitted works will be deleted too,
requiring them to re-upload. And tbh that option seemed pretty nuclear &
scared the crap out of me (of screwing up)... Hence my procrastinating it.
Sigh. Anyway it now appears to be moot.
2 is "default originally assigned creators, and reassign volunteers as
pinch hitters." But as I understand it, that means the originally assigned
creator then forever has a defaulted assignment listed in their AO3
assignments. Which kind of sucks & doesn't seem quite right -- plus,
actually, everyone who volunteered to be reassigned actually did us a HUGE
favor. So they least deserve the defaulted listing (not that anyone who
didn't default does; they don't).
no subject
Date: 2019-12-07 02:47 pm (UTC)Well, I was going to say "hold off on that" but... As it happens, there seem to be only 2 ways to fix the rearrangement of recipients, which are greatly and fairly undesirable, respectively. Plus now that folks are already posting their works, I think I've cut off the path to one fix (at least without making it way too difficult for participants, who we don't want to irritate, to keep people willing to participate for future dSSSes)...
But I had not considered the simple solution you've suggested! (Which seems so obvious I'm embarrassed I didn't think of it already. Duh...) You must run some other challenges, lol! :-)
Anyway, would you be willing to be an experimental subject, lol? Would you consider doing what you just described, as an experiment, & I'll see how it looks on our end?
If it looks like it came out wrong or weird on our side, we can always delete it. If not, we can tell other people to do what you did! :-) Although I guess we wouldn't really know until the collection opens Dec. 24 at 23:59...
Here's the complete back story... The two ways of doing this are:
1 was "purge ALL dSSS assignments (saving a record of the originals first,
of course, so everyone else can be reassigned there original recipient) and reassign manually." But I can't do that now because people have already submitted works... So already-submitted works will be deleted too, requiring them to re-upload. And tbh that option seemed pretty nuclear & scared the crap out of me (of screwing up)... Hence my procrastinating it. Sigh. Anyway it now appears to be moot.
2 is "default originally assigned creators, and reassign volunteers as
pinch hitters." But as I understand it, that means the originally assigned creator then forever has a defaulted assignment listed in their AO3 assignments. Which kind of sucks & doesn't seem quite right -- plus, actually, everyone who volunteered to be reassigned actually did us a HUGE favor. So they least deserve the defaulted listing (not that anyone who didn't default does; they don't).
So. That's the story.