The Archivist's Guide to Archiving

From Caelwiki

Greetings, archivists in training!


We're here with a couple (...ok, a lot) of tips to help you get started in creating logs of IRC transcripts, hopefully as painlessly as possible. To be clear, creating a clean log DOES take some effort, so be prepared to set aside a good chunk of time to devote to your archiving. It is difficult at first, but will get faster with practice.

Contents

What should be Archived?

We usually archive sessions that involve a DM's participation. This gives a sort of structure that will help the formatting and lends the session authenticity within the story arc. When significant character development occurs outside of a structured RP session, and is accepted within the RP universe, such non-DM run sessions may be logged as well. (see In memoriam: Hadin the Artificer passes on for an example)

Sessions to be archived start off as raw logs captured from your IRC client. There may be several channels involved in the telling of a particular session, as well as possible PM logs to individual characters. Be thorough in collecting all the necessary data!

How do I get these logs?

You first need to have an IRC client that allows for logging (i.e. mIRC, Ircle, Trillian). The Java applets do not log. Your client should have an option somewhere for turning logging on, check the help file if you can't find it. Make sure to log both channels as well as queries, as there may be sessions that involve private messages to your character from the DM.

Also make sure you find out where your client is storing the logs, and what format they're in! Some log as plain text files, some as .xml, and there are other variations. Be sure whatever format you save as is editable in a text editor. You may also want to check with a few test logs to make sure they don't write over each other.

Finally, turn on timestamps! They're not necessary, but they can be helpful in figuring out how to piece together multiple-channel-spanning logs.

If you absolutely cannot get logging to work on your computer but you really want to help out archiving, there are several players on Caelestia who log everything, and if you ask them nicely, they may email you a copy of their raw log. ;)

Ok, I've got the logs, what do I do now?

First you'll want to create a new wiki page for your log. For some strange reason there is no "create page" button on the website, so what you'll want to do is this:

  • Type the title you want for your page into the search bar on the left.
  • A page will come up saying "No page with this exact title exists, trying full text search."
  • Click on the words "this exact title"

A new page should open, and this is what you will want to paste your log into.

A note on naming conventions for new pages: Logs from #darkabode are generally named something appropriate for the event. Logs from #epic are titled "The Epic - Session (roman numeral here)". If the epic is very long and needs to be split into parts, the title should be "The Epic - Session (numeral): Part 1" and so forth.

I made a new page, let's start archiving!

This is a method I've worked out for clarity of DM direction, as they usually write the story. It is by no means the only way to log a session, and you may argue the players contribute just as much to the session as the DM. However for the purposes of this tutorial I am going to consider the DM's direction as the final say in matters involving plot advancement and consider them the "authors" of the session.

What you're going to want to do with these logs is highlight the DM's lines in bold. It sounds simple enough, right? Well, there are a few ways to do it so it will show up in the wiki:

  1. Use the wiki editor. There's a "bold" button in the top left corner that will add the proper tags into your entry. However, this involves actually moving your mouse around to highlight the line, then click the button over and over again. This can be time consuming. There are also other factors to take into consideration (more on this below)
  2. Use an outside editor. You'll want one that can utilize the ctrl-B command to automatically bold a line, and can also translate your log into html code when you're finished. Googledocs is a good editor, I've found. Once you're done bolding the lines you need, you can click "Edit HTML" to get the proper code to paste into wiki. This is my preferred method, but whatever works best for you is what you should use.

Either way, you'll want to make sure when you paste the raw log into your editor, it includes line breaks. If you're getting a big block of text with a bunch of <BR>s in it, that will be a nightmare to edit.


This is what you don't want to start with as a raw log:

[17:28] >Ambiance<: There is a familiar tugging sensation as if your stomach is being twisted<br>[17:28] * Elenor puts it on, under her robes.<br>[17:28] Cerbero: ((T_T))<br>[17:28] Durroth: aw crap<br>[17:28] * Nick grabs his stomach.<br>[17:28] Durroth: not again<br>[17:28] GT: "Now what is going on?"<br>[17:28] silversyte: aw come on<br>[17:28] Nick: Now!<br>[17:28] * Lkeas doubles over. "Geez, not a moment of peace.."<br>[17:28] Stromy: "Bad things..."<br>[17:28] Elenor: Oh hell<br>[17:28] * Strider grasp his stoamach<br>[17:28] Strider: "What is this??<br>[17:28] * Clyde hunches over with pain, grabbing his stomach tightly. ".Not.....again!"<br>


This is what you do:

[17:28] >Ambiance<: There is a familiar tugging sensation as if your stomach is being twisted
[17:28] * Elenor puts it on, under her robes.
[17:28] Cerbero: ((T_T))
[17:28] Durroth: aw crap
[17:28] * Nick grabs his stomach.
[17:28] Durroth: not again
[17:28] GT: "Now what is going on?"
[17:28] silversyte: aw come on
[17:28] Nick: Now!
[17:28] * Lkeas doubles over. "Geez, not a moment of peace.."
[17:28] Stromy: "Bad things..."
[17:28] Elenor: Oh hell
[17:28] * Strider grasp his stoamach
[17:28] Strider: "What is this??
[17:28] * Clyde hunches over with pain, grabbing his stomach tightly. ".Not.....again!"


NOTE - If you are logging within the Wiki editor, you will need to specify each line break with a colon ":". You can do this by hand (again, time-consuming), or you can open up your log in Notepad and use the "Find and replace" function to add it in automatically. Replace all "[" with ":[" and that should do it for ya.

Once you've got your log set up with proper line breaks, you can start highlighting the DM's lines.


How do I know which lines are the DM's?

Alright, now that you've got the technical stuff down, here's where it starts getting into the "art" of archiving. Knowing which actions to highlight requires you knowing your DM well, and understanding the things s/he is trying to do within the session. Here are the basic highlights:

  • >Ambiance<
  • The DM's main character actions and dialogue
  • Any other characters played by the DM
  • Actions that the DM takes out on the players (legal bunnying)

It should be pretty straightforward for the most part. There may be times when a DM plays many characters and it may be tricky to spot them all. An archivist must be observant!


Regarding instances of bunnying: These can be hard to find since it can be difficult to know whether a player performed an action or whether the DM used /faction or /fsay. If you are unsure, you can ask the player (as they'll probably remember better than the DM who has to keep track of a bunch of other stuff), or just leave it unhighlighted. Usually you can tell it's the DM if a player "attempts" something and another line occurs as an effect. For example:

[19:16] * TaloToecan continues to try and envision himself in full health, desiring the nature of speech despite the chaos of his mind.
[19:16] Cerbero: Reality is relative.
[19:16] * LordBarrius shakes his head, escaping his thoughts, and holds Talo in one arm while reaching out the other to pet him gently and almost absent-mindedly.
[19:16] * silversyte thinks of a shiny golden longsword
[19:16] Taimat: "Well...It appears that only a select few of us can create thing simply via pictureing them...I,for one,am still waaiting on that drink."
[19:16] Rimblade: "Aunt or uncle?"
[19:16] * TaloToecan is healed

The last line was done by the DM in response to TaloToecan's attempt at the beginning of the log.


Hey, I think my DM made a mistake...

DMs are people too, and sometimes with all the crazy stuff that happens in a session their scripts may break, or they may accidentally play a wrong character. Ultimately it is up to you whether you want to try to correct errors. Usually I edit things that will cause confusion to a player trying to understand a session they were not a participant in. Spelling/grammar errors are usually not necessary to correct unless there is some major problem that will cause confusion.

The DM will sometimes give direction within the session as to how the error should be corrected:

[18:14] >Ambiance<: The strains of some odd music filter through the abode
[18:14] Fal-away: (Forest)

Could be changed to:

[18:14] >Ambiance<: The strains of some odd music filter through the forest


[20:44] Fal-away: "Hello Profitless" (without rancor)
[20:44] Fal-away: *Tirlerion

Should be changed to:

[20:44] Tirlerion: "Hello Profitless" (without rancor)


There may also be instances where the DM voices the wrong character but does not indicate what it should be corrected to. Most of the time it can be inferred who should be speaking, by dialogue surrounding the aberrant line.

Be wary though, as the DM may choose to run along with what seems like it could be a mistake, and not wish for a correction to be made later. For example:

[19:26] Cerbero: I have one question for you, Cartwright.
[19:26] Amelie: I have no answer for you
[19:26] Cerbero: How well do you know your master?
[19:26] Selarep: "Grah..."
[19:26] Amelie: The time for answers are done
[19:26] * Nick laughs "Which one of us?"
[19:26] Amelie: I am under his control;

In this case, Amelie responds to Cerbero when it appears that it should be Cartwright answering. However, the DM modified the character to be under Cartwright's control, so there is a reason why Amelie does the talking. No corrections need to be made.

Done! Where do I put it?

Once you're done formatting your log, hit the "Show preview" button to see how it will look when it's published. If you see anything wrong with it, go back and keep editing. When it looks good, hit "Save Page" and your log is archived!

But you're not done yet, you need to link your page to the index so other players can find it! Here's what you do:

  • Find the index page and click the "Edit" tab.
  • Scroll down to where you want to put in your link. Try to follow the example of the links that are already there (title of log, date, description if it's an epic, category if not)
  • Type the name of your page inside double brackets like so: [[Name of page]]. This will create a link on the page.


For epics and other multi-part logs Say you have an epic in two parts. In the index you will list it like this:


Session XXX - Part 1 Part 2 - 03/07/07


You want "Part 1" and "Part 2" to be the links to your pages, but you named your pages "The Epic - Session XXX: Part 1" and "The Epic - Session XXX: Part 2". Pretty long, huh? Here's how you type in the code to make the links small:


[[name of page | what you want the link to say]]

In this example:

[[The Epic - Session XXX: Part 1|Part 1]]

When you're done you should have code that looks like this:

Session XXX - [[The Epic - Session XXX: Part 1|Part 1]] [[The Epic - Session XXX: Part 2|Part 2]] - 03/07/07

And when you preview the page, it should look like this:

Session XXX - Part 1 Part 2 - 03/07/07


Congratulations! You've contributed to the archive! Your fellow players will thank you for your service to the roleplaying community.


Player Typos by Eitak Razal

What? You or another player made a typo during the Epic? Then Fix it in the log.

Rules for fixing player typos

The rules are practly the same as when a DM makes a typo, therefor I am not provideing examples at this time.

  1. Only fix your own typos unless there is a correction within the log, the play may have intended it.
  2. ONLY fix typos. Do not alter the lines to say something else under the guide of fixing typos.
  3. If the typo is acted upon in charcter DO NOT change it.

This section is by no means approved by others.Check with others before editing typos.

Personal tools