Needs Help: My Baby Doll

Looks like a premature launch. Not indexed, no wicks, only four examples. And the YKTTW only had two hats. Looks like a valid trope, but I suspect it really needs to spend a little longer in YKTTW to get examples, and maybe help it find some indexes.

Send it back to YKTTW. Two of the examples are totally spoilered out anyways, which makes for rather poor examples.

Googled Soryu Syndrome. First two hits are the YKTTW and article respectively. Rest are not actual uses, just pages with both words. Good catch, Doktor.

edited 17th May '12 8:19:58 AM by tdgoodrich1

Send it back, and while there it needs to get rid of "also known as Soryu Syndrome", which I'm fairly sure isn't a pre-existing term, just some Evangelion reference.

It also has zero wicks but one inbound! I suspect the creator was in a bit of a rush to have a page to link to.

Bump for more comments. (Plus, I'm not quite sure how to actually send something back to YKTTW.)

You copy-paste the code into a new YKTTW and cutlist the original page with an explanation.

Before we cutlist, we should probably wait for a little more feedback.

And the third Google hit is this very discussion. I cut it out.

I'm all for re-YKTTW-ing it.

Bump again. Should we bother with a crowner, or is the consensus pretty clear? Even the creator hasn't bothered to pop into this thread to try to defend the trope, so I'm not seeing much hope for it.

Bump. It's been over a month, and nothing has changed here, including the trope. Is it too late to ask Eddie to unlaunch this?

I say go ahead and ask him.

Clocking due to lack of activity.

I would do what needs to be done in a heartbeat if I knew what that was. We need a simple, easy procedure to deal with "premature launch needs to go back to YKTTW". If we have such a procedure, I'm really not sure what it is.

Surely someone has done this before and can provide simple step-by-step instructions? This can't be that unusual.

I don't think TRS is allowed to do anything these days without a successful crowner first. That said, you send something to YKTTW simply by starting a new YKTTW with a copy/paste of the article text, then cutlist the article, then keep an eye out whether it actually gets cut, then ask for a star on the TRS thread, then keep the thread open with regular bumps until the YKTTW concludes, then (if needed) create a redirect from the current title to the now-launched YKTTW. It's not hard but it's a lot of work.

Gah, a problem this common really needs an easier solution.

Ok, what should go on the crowner? Page action? How many options do we have here?

Bump? Anyone? Surely someone has dealt with something like this before?

Okay.

You can send something back to YKTTW (note: by this, I mean send without cutting) without TRS consensus. Going through YKTTW to garner examples is not something that can hurt or alter a page.

You can trim, clarify, remove an Example As Thesis, and mildly change the description of a trope without a crowner. I know "mildly" is subjective - please use common sense.

You cannot cut a page and resend to YKTTW without a crowner unless it is a recent launch. Normally I'd say we missed our window here, although given the lack of wicks and inbounds we can probably make an exception.

You cannot rename a trope without a crowner, unless it is a very recent launch.

You cannot radically change the definition of a trope without a crowner. Again, use common sense about when and judge others' reactions to the proposed change(s).

edited 20th Sep '12 2:32:10 PM by ccoa

Ok, YKTTW is here. As for the name and description, I don't have strong feelings about them.

On the other hand, this was sent to TRS the day after launch, and has had zero examples or wicks added since then (the only edits are for phrasing and namespaces). So, even though it's been a while, I would argue that it should still count as a new launch, despite the actual passage of time caused by my lack of experience in dealing with mislaunches.

That last may be a non-issue unless people at YKTTW really want to change the name or description, but I tend to think they should have the option if they want it.

edit: fixed URL

edited 20th Sep '12 2:59:18 PM by Xtifr

I have no issues treating this as a mislaunch. As such, we can cut the page or rename without a crowner so long as no one objects.

None here.

None here, either.

The thing is, if you "send a page to YKTTW" without actually cutting it, you're quite possibly going to end up with two pages. That's generally not what you want.

I figure that if we don't cut it, I can simply add the new YKTTW to the discussion page, so there's a link, then "discard" the YKTTW.

Since the whole thing is being tracked on TRS, we should be able to avoid accidentally creating two tropes.

That said, I have no particular objection to cutting. If YKTTW decides not to change the name, I know how to request an unlock.

eta: furthermore, cutting might allow us to close this thread.

edited 20th Sep '12 4:24:20 PM by Xtifr

Spark, you do not end up with two pages. You end up with more examples for one page. If there were objections to the name in YKTTW (or here), then that would be intelligently dealt with by cutting or redirecting the old page (after a crowner, if necessary). We don't blindly follow procedure and robotically produce the outcome. We are capable of critical thinking and problem solving, by large.

EDIT: That said, I also do not care if we cut this while it runs through YKTTW.

edited 20th Sep '12 5:12:36 PM by ccoa

I'm happy to report that the YKTTW is going well, and we've more than doubled the number of examples already. I was a little concerned going in that this might turn out to be so rare that it would take a long time to come up with examples, but that doesn't seem to be a problem.

Nobody has objected to the name yet, even though I made it fairly clear that I'd entertain suggestions. I'm still looking for index suggestions, though. I think we have a Parenthood Tropes index (or something like that), but I think we need more than just that.

I don't have any suggestions for the name, but it does need changing. The current name is completely unintuitive.