I’d like to borrow Nomad for an hour so he could wipe my bosses’ memory clean. Then I could retrain him....”I am now your King. You are my lowly, worthless servant. You will grovel at my feet.”![]()
Dilbertesque

I’d like to borrow Nomad for an hour so he could wipe my bosses’ memory clean. Then I could retrain him....”I am now your King. You are my lowly, worthless servant. You will grovel at my feet.”![]()
Maybe they put Uhura through the transporter and it restored her memories like every other time that they lost something and couldn't cure because it held a molecular print of their pattern from another time?
JB
Keeping it a one-shot character who had their brain erased would've made a lot more sense. I can understand Roddenberry wanting it to be one of the show's recurring players, though. If you're paying for them, you might as well use them. But having the brain erasure thing be so easily undone killed the drama of it.For fun, here’s some of the evolution of this scene.
The scene was originally written to feature a character named Yeoman Barbara Watson. In the outline dated March 15, 1967, she’s on the bridge because she’s delivering a message to Uhura. This excuse was changed in the first draft script (May 1, 1967) to delivering coffee to the crew of the bridge. In broad terms, the scene as written in the outline and the first draft is similar to the one in the filmed version except that Watson is whistling and Nomad (Altair in the first draft) erases her thinking processes/units. In both early versions, Sulu comments that the alien machine must have burned out her mind in the same way that it previously burned out the translator computer.
D.C. Fontana didn’t like the reason in the first draft as to why Watson was on the bridge. In a May 3, 1967 memo to Gene Coon, she wrote, “Yeoman Watson should be on the bridge on business, collecting some report tapes or papers or something. This car-hop service writers keep putting in for the yeomen is ridiculous.”
Roddenberry preferred that the scene not use Yeoman Watson at all. He specifically said this about it in a May 8, 1967 memo to Gene Coon: “Can we use Nurse Christine Chapel instead of Barbara in the whistling sequence? Would prefer a continuing character here if we can find a way to avoid her brain being washed clear of all intelligence.”
Fontana, who was tasked to write the next draft of the script, changed the whistling character to Uhura, but Justman had a problem with the scene. From his June 1, 1967 memo to Gene Coon he said, “I find it awkward for Uhura to be whistling because she is happy in Scenes 41 and 42. This is odd behavior for anyone in a situation such as we have developed. After all, the little machine has demonstrated to her that it has enormous destructive capabilities.”
And finally, good or bad, the June 29, 1967 shooting script finds Uhura singing instead of whistling.
You can never have too many Uhuras. Here's where replicators could come in handy. She could could become the SOUTH PARK Kenny of TREK while never missing an episode.
Don't forget we need to squeeze Mirror, Mirror into the timeline, and Uhura needs to be at the top of her game for that episode. I usually put it before JTB. YMMV.The next episode is "Journey to Babel" stardate 3842 (20 January 2269) nearly four months after her encounter with Nomad. And here we do see her running through some pretty technical tasks while trying to figure out what would be learned was an Orion ship.
Don't forget we need to squeeze Mirror, Mirror into the timeline, and Uhura needs to be at the top of her game for that episode. I usually put it before JTB. YMMV.
At that time in the episode, Kirk had no idea that the men were seeing different Nancy Craters, so, this log entry must have been added to the "mission report" after the events. This convenience allows me to move some episodes back in time a little and fit them in stardate gaps if needed.Captain's log, additional entry. Since our mission was routine, we had beamed down to the planet without suspicion. We were unaware each member of the landing party was seeing a different woman, a different Nancy Crater.
....
Even when two episodes overlap (as with The Corbomite Maneuver and The Man Trap), I assume Kirk is recording the previous mission report in an offscreen moment during the middle of the next mission event. After all, we see Kirk working from his desk in his quarters. Working on what? Probably on his most previous mission report(s) while they are still fresh in his brain. YMMV.
Here's my repost of my Stardate rules:This is a brilliant justification that never occurred to me. I'll definitely be applying this idea to my own timeline project.
Thanks!
--Alex
It is important to understand the difference of a stardate given in actually dialog versus the voice-over stardates given in log entries either during or after the events occurred. The voice-over stardates are given at the time of the log entry, and not the stardate of the events being shown in episode.
For me, I choose actual stardates based on a hierarchy of rules with the last rule: "If there is no explanation for something that doesn't fit, assume it is a script error and move along." The most important rule is "have fun".
1 1000 stardates = one Earth year or 365.25 days or 8766 hours; or ~2.74 stardates = 1 day;
2 Scene or character delivered stardates are actual stardates of the event and cannot be changed;
3 Log entries are usually spoken in the present tense narrative;
4 "Log" entries can be minutes, hours, days, weeks, months after actual events as-recorded in the ship's records during the episode or as-edited in the mission report after the event;
5 I try to assume the least amount of lapsed time of log entries (report while still fresh in memory) but you can also assume any length of time prior to the inserted log stardates, even several months on rare occasion.
6 It is better to sort the episodes by finish stardates, but this is only a minor issue versus start stardates;
7 Episode durations and time between episodes must be estimated based on episode dialog or action; as a rule of thumb, one to two weeks (20-40 stardates) should be allowed between episodes, but only a day or two is sufficient to travel several star systems if they are in a hurry like answering a distress call (speed of plot can be very fast);
8 Several unknown stardate episodes must be estimated; as a rule of thumb, try to stick to production order if possible, i.e. put episode 54 as close to 53 or 55 as possible;
9 I put in additional time to complete the unaired parts of each mission (x days scanning before episode, deliver x to y after episode) or for repairs, set changes and starbase visits; serious ship repairs can take one or two weeks; upgrades maybe longer.
10 If there is no explanation for something that doesn't fit, assume it is a script error and move along. (This actually occurs with five episodes: TCOTK; TGOT; TDY; ATCSL; SB which I rule all have script errors.)
Personally, I think the fact that we get (IIRC) one scene of Uhura's recovery where it's stated that she'll be restored to normal and back on duty inside of a week means that it was more or less magically undone. After all, it's not like the show ever referred to Uhura ever having any other difficulties with the aftereffects of Nomad's mind probe. In the grand scheme of things, it might as well have never even happened.The idea that such an enormous thing could happen to a regular, that it wasn't magically undone, and dealt with in a real world way, added a lot of imaginative punch to the episode.
Do you happen to have your Chronology online anywhere, @Albertese? I'd be very interested in seeing it.So, now you got me thinking about a window for "Mirror, Mirror" to fit in. My initial thoughts are that Dr. McCoy "spilled acid there a year ago" and he would seem to have come aboard in September 2266, in the week or so between WNMHGB and "Mudd's Women." Which places an earliest date for "Mirror, Mirror" in September 2267 (a year after he came aboard assuming he spilled that acid on day one) in the stardate 2400 area--well before "The Changling" ever happens. This happens to be a several month stretch where no actual episodes happen, so it'd be easy to fit in there.
Personally, I think the fact that we get (IIRC) one scene of Uhura's recovery where it's stated that she'll be restored to normal and back on duty inside of a week means that it was more or less magically undone. After all, it's not the show ever referred to Uhura ever having any other difficulties with the aftereffects of Nomad's mind probe. In the grand scheme of things, it might as well have never even happened.
Do you happen to have your Chronology online anywhere, @Albertese? I'd be very interested in seeing it.
Sounds interesting! So if I'm understanding you correctly, it sounds like you're creating your own episode order based on evolving characterizations, rather than going by airdate, production order, or Stardate order?However, I prefer to arrange an elaborate head canon where the characters are impacted by their experiences. I prefer a world of Consequence. And it makes the episodes much richer to imagine these characters dealing with the previous episodes still. Watch "This Side of Paradise" where Spock is enjoying the company of a former suitor and realize that this is less than a month since his divorce of T'Pring in "Amok Time." How much of his behavior was just the spores?
Sounds interesting! So if I'm understanding you correctly, it sounds like you're creating your own episode order based on evolving characterizations, rather than going by airdate, production order, or Stardate order?
....
I gave up on Stardate order pretty quickly when I saw that "Amok Time" took place on Stardate 3372.7 and the next episode that came up in Stardate order was "This Side of Paradise" on Stardate 3417.3. Since both of those episodes depend upon "Why is Spock acting so emotional?" as story hooks, I decided it was best to keep them as far apart as possible. And since the precise numbers were fairly arbitrary, I thought it was kind of silly to have them determine the episode order.Well, not quite. Stardate order is the main factor, though where there's room for flexibly characterization is definitely a factor.
We use essential cookies to make this site work, and optional cookies to enhance your experience.