AO3 News

Post Header

2010-08-12 16:21:12 -0400

Creating and editing a collection

So, you've decided to run a gift exchange challenge. Awesome. Here's a guide to help you get started.

1. Go to the Collections tab and click New Collection.

A gift exchange is run within a Collection.

New collection button, black text on white. To the left are Title, Date and Size buttons.

2. You should see this screen:

Screen headed New Collection, with suggestion text and a series of text boxes used to set up a new challenge.

  • Select owner pseudonym(s): Which pseudonym you'd like to be shown as the owner of the collection.

  • Icon: The icon (if any) you'd like to represent the challenge.

  • Parent collection: If this is a sub-set of another collection (for example, one year of a challenge that has been run for multiple years), enter the parent collection here.

  • Collection name: the name of the collection. For example, Annual_Example_Challenge_2010. This will define the URL (web address) of your challenge so there can be no spaces.

  • Display Title: For example, Annual Example Challenge 2010. There can be spaces here.

  • Email: If you've got a separate email address for running the challenge enter it here. If you haven't, by default email messages will go to the challenge owners.

  • URL for custom header: If you'd like to have a custom header for your challenge, enter the URL where the image can be found on either your own webspace, or that of a photo sharing site.

  • Brief description: A brief description of your challenge, which will show on the Collections main page and the Profile page.

Series of tick-boxes with options for seting up a new challenge.

  • Is this collection moderated?: Tick this if you would like your collection to be moderated. If a collection is moderated any registered user can post to it, but all works must be approved by a moderator or owner.

  • Is this collection closed?: Tick this if your collection is Closed. If a collection is closed, no one can post to it. Remember to open it when asking people to post their works.

  • Is this collection currently unrevealed?: Tick when you would like to hide your challenge entries, untick when you would like to reveal them.

  • Is this collection currently anonymous?: Tick if you would like your challenge's works to be anonymous. Untick to reveal the authors of the works.

  • Would you like to show random stories on the front page instead of the most recent: Tick this if you'd like to show random works on the home page of the collection instead of the most recent.

  • If this collection is for a challenge, please choose the type: Select gift exchange from this drop down menu.

The next three optional fields are where your Introduction, FAQ (Frequently Asked Questions) and Rules can be entered. These will appear on the Profile page. However, the Rules and FAQ become their own menu entries on the left-hand side once entered so they can be easily found by your participants.

Menu with Dashboard at the top in white on black text, followed by menu items, Profile, FAQ, Rules and Parent Collection below.

Note: If you are creating a sub-collection these will be inherited from the parent collection by default, but anything you enter in this sub-collection will take precedence.

Gift Notification Message: In this field you can create a custom message that will appear in the emails when works are revealed and participants are notified of their gift. This is optional.

To alter these at any time go to the Settings menu item, or select the Settings button at the bottom of the Profile screen.

Black on white row of buttons. Signups button to the left, with Challenge Settings, Settings, Delete and Delete Challenge to the right.


Depending on what sort of challenge you're running and its size, you may want to assign moderators and tightly control who can post to the collection. This is done on the Membership screen.

To go there click the 'Membership' button on the challenge's dashboard or Profile page.

Black on white row of buttons, Profile, Membership and Manage Items, from left to right.

By default you will appear as an owner of the challenge. You can have multiple owners if there is someone or a few someones helping you run the challenge. Everyone you assign a role to must have an AO3 account. When you enter a name the site will search for AO3 user names.

The roles it is possible to assign are:

  • Member: This person can post works to the challenge without prior approval.
  • Moderator: This person can approve/reject works, and add members.
  • Owner: The owner can approve works, assign pinch-hitters, and alter the sign-up form and FAQ and Rules fields. You can have multiple owners.

  • Invited: This functionality has yet to be rolled out.

Note: By default, all registered users can post to a challenge, being a member of a challenge just means that they can post to a moderated challenge, and their work will be accepted without moderator approval.

Sign-Up Form Settings

To set up the challenge sign-up form go to Challenge Settings, this is near the bottom of the left-hand side menu.

Menu with Dashboard at the top in white on black text, followed by menu items Profile, Parent Collection, Your Signup, Signups, Matching, Fandoms, Works, Bookmarks, Random Items, People, Tags, Challenge Settings which is highihgted in red with white text, and Settings.

You should see this page:

Sign up form headed 'Setting up the 2010 Example Challenge Gift Exchange. Below that is paragraphs of suggestion text and then a Schedule heading with a series of drop down menus with times.


To set up the timings of your challenge, use the Schedule.

Close-up of Schedule drop down menus with a sign-up open tick box at the top which is not selected.

These times are only for information and will not automatically open sign-ups, close sign-ups or reveal works. This will all need to be done manually.

The times will appear on the Profile page of the challenge.

Sign Ups Open?

The Sign Up open tick-box is where you open or close sign-ups. Leave this box unticked until you have your sign-up form ready.

tickbox with sign up open? written beside it. it is not selected.

Requests and offers

Request and Offers sets the number of requests and offers you'd like the participants to use. You can set a required number (how many they need to have) and an allowed number (what is the maximum number they can have).

Two rows of two text boxes with Required 1 and Allowed 1 on the top row, and Required 1, Allowed 2 on the second.

In the example above, participants must be make at least one request and offer, but can make two separate offers if they chose.

Then, you have to set the tag settings for the requests,

A series of text boxes listing field names with a field beside each one for Required and Allowed numbers.

and offers.

Another series of text boxes listing field names with a field beside each one for Required and Allowed numbers.

These will define what a participant's requests and offers can contain.

  • Optional tags: Click this if you would like to allow optional tags. These are tags that participants can add which will be matched on if possible, and allows your participants a little more flexibility with their requests and offers.
  • Details/Description: Tick Required if your challenge needs to include more details than just a relationship or fandom, and Allowed if you would like to give participants the choice to include more details.
  • URL : Tick Required if your challenge needs a URL (for example, where the participants works are archived) or Allowed if you would like to give participants the option of including one (for example, a link to a Yuletide letter).

You can leave both of these blank if you like and select neither box.

Now, you can define how many fandoms, relationships, or ratings participants are allowed to chose.

To do this enter numbers into the required and allowed boxes. You do not have to fill in all of these, and if you are using automatic matching it will take a longer time to match them if you fill in too many.

If you are running a challenge that is specifically for a given fandom or relationship or character, just leave that set of tag options set to no tags required or allowed -- don't put in that one tag as the only choice. Tag options should only be used where you want participants to have a choice.

Next you can define what tags people can chose from when making their requests and offers.

Seven text fields. Character, Relationship, Freefrom, Category, Rating and Warning are all blank, but Fandom has a series of fandoms listed in in separated by commas.

In the example above, participants can choose from any of the fandoms listed in the fandoms field. Anything entered in these fields should be comma-separated and will auto-fill.

Close up of Character text field. Buff is typed with auto-filled fields showing below listing, Buffy Summers, Buffybot, Pheobe Buffay ...

Note: In all of the fields, you will only be able to choose canonical tags that are already in the AO3 system. If you wish to include a fandom, relationship, character or additional tag (freeform) which is not already in the system, please contact the Tag Wrangling Committee through the Support and Feedback form or via the Tag Wrangler's twitter account, @ao3_wranglers. When possible, the committee asks that these requests be lodged at least one month before opening a challenge, to give tag wranglers time to review and add necessary tags. The Committee can also add additional tags (freeforms) for members to add to their posted works as required.


The next set of drop-downs determined the minimum level of matching that must occur in each field. That is, how many characters or fandoms must match between the participants to consider them a match. The simplest option is to chose to match them on Requests, meaning anyone with a Request matches another person with a Request, but this may not work for more complicated challenge with a variety of different tags in use.

Image:List of drop down menus with numbers for minuimum number of matches to make. List includes Requests, Fandoms, Characters, Relationships, Freeforms, Categories, Ratings, Warnings.

If you leave a 0 in the drop down it will not match on this field.

Note: the most options that are chosen here the longer matching may take, and the harder it will be for matches to be found.

Optional tags: If you chose to use optional tags above, you can choose what field(s) they are used to match on if possible.

Next are three fields which define the challenge-specific instructions that will go with the sign-up form.

You can also change the labels for the URL and Description fields if you are using them.

Three large text boxes, and four smaller text boxes for changing labels in Sign-up form.

For example, as seen above, if you are running a challenge where participants need to provide a link to where their fic is archived, you could call the field, 'My fic is located at:.'

Remember: check the Sign-Up Form to make sure it's working how you'd like before opening it up for people to sign-up for the challenge.

Now you're ready to open the sign-ups!

To do this go to the Settings menu and tick the 'Signups open?' tickbox.

Checking the Sign-Ups

You can check the sign-ups as they come in by going to the sign-ups menu item on the challenge side-bar.

Two rows of light pink boxes in a table with a summary of a sign up going horizontally.

Here you can see what participants have chosen.

To make the list easier to navigate (especially if you have multiple requests and offers) you can hide the descriptions using the Hide Descriptions button on the top of the screen. To bring them back click Show Descriptions.

If you need to contact a participant for any reason you can click the envelope icon next to their username.

Close up of a particpants name called aworldinside with Edit and Delete links to the left and red envelope icon to the right.

If for any reason you wish to edit or delete a sign-up use the edit and delete links on the left hand side.

You can also download an Excel spreadsheet of the sign-ups. To do this click the Download (Excel) button at the top of the screen.

Close Sign-Ups

Since the dates on the Schedule are provided only for information, you must close sign-ups manually.

To do this go back to the Challenge Settings menu and untick the Signups Open tickbox.

tickbox with sign up open? written beside it

Sign ups are now closed.

Generate potential matches

Now you have closed sign-ups, let's do some matching for your gift exchange.

Depending on the choices you made when you set up the Sign-Up Form this may not be necessary, or you may chose to manage the assignments manually. If so skip through to Adjusting Assignments

To generate matches go to the Matching menu.

There will only be information here once you have closed sign-ups.

Matching menu item selected to the left, with a matching screen to the right. Headings for Pseud, Giving Gift to, Assigned Giver, Potential Gifver, and Write in Pinch Hitters. There are nothing below them.

Click Generate Potential Matches.

If your challenge settings mean that you don't require automatic matching, you will get a warning that the automatically generated matches will be at random. Click OK if you wish to continue.

Grey warning box with Blue circle with a white question mark to the left.

Matching can take a while depending on how big your challenge is and the criteria you have set.

You will receive an email when the matching is complete.

The matching screen should look something like this:

Pink table with partipants names to the left, with names under Giving Gift To, drop down menus under Assigned Giver and a link titled Show 13 under Potential Givers. A field titled Write in Pinch Hitter is on the right.

Adjust assignments

You can adjust the assignments in two ways:

1. Automatically

To automatically adjust the assignments click 'Regenerate assignments' and the matching process will be run again.

White button with black text titled Regenerate Assignments

Note: Depending on your matching settings, this might not make a lot of changes to your assignments. If you alter something on the Challenge Settings Page then this may make more of a difference.

2. Manually

To adjust the assignments use the drop down menus.

Image:Pink table with Assigned Giver drop down expanded.

Note: If you adjust the assignments, they will not readjust automatically so that each participant has another writing for them. You will need to check them manually (or regenerate assignments).

To see all the potential givers for any one participant use the links under the Potential Givers column.

Image: Pink table with two row showing. One has Show 13 link expanded to show a list of participant names.

Clicking on a potential users name brings up their sign-up.

Image: Series of black text summarising a participants sign-up.

Once you have finished click 'Update Assignments'

White button with black text titled Update Assignments

If you have any participants who don't have an assignment, it it will show up under 'Missing recipients'

Assignments screen with extra box at the top under Missing Recipients. Drop down menu with a participant highlighted in blue under Pinch Recepient.

Use the drop down menu to select the recipient and click 'Update assignments' and they will return to the main table.

You can also chose to write in a pinch-hitter in the right-hand field. Pinch hitters do not have to be signed-up for the challenge, but must already have an AO3 account.

Send assignments

Once you are happy with the assignments, to send them to participants click 'Send Assignments.'

White button with black text titled Send Assignments.

All of the challenge maintainers will receive an email when the assignments have been sent to all participants.

Managing Posted Works

Once the assignments have been sent out you should now see this screen when you click Assignments (which has replaced Matching in the side menu).

Light pink table with list of participants on the right, red envelope icons, and then list of who they are writing for. Work info says not posted for all participants. Tick boxes with Default on all rows. Not eelected.

As participants post works this will be shown in this table.


If you are running a moderated challenge, each work will have to be approved by an owner or moderator before it can be added to the collection.

This is managed through Manage Items, which can be found on the profile page of the collection.

White buttons with black text. From left to right: Profile, Membership, Manage Items.

Use the drop-down menu under Collection Approved to either accept or reject the work.

Pink table with a series of entries called 'awesome chalenge agan.' Creator column says aworldinside, Member column is Y, Creator approved column says approved. Collection approved drop down says approved, Unrevealed tick box is selected. On far right are two links, Manage and Delete.

You also have to option to Remove a work, using the option on the right-hand side and to keep a work unrevealed from the rest of the collection using the Unrevealed tickbox.

Works, once they are accepted, will be added to the collection (but will remain hidden until you reveal them) as well as any by users who are Members of the challenge and have therefore been pre-approved to post to it.

If you are not running a moderated challenge, the works will be added to the collection automatically.

Managing Defaulters

If a participant has defaulted, use the tick box beside their name.

Once they have been marked as a defaulter this will appear:

Pink table with three rows under Defaulted Assignements. A pinch hitter field is shown blank. Three rows under Assignments appear below.

To assign a pinch-hitter:

Enter the pinch-hitter's archive username in the pinch-hitter field (again remembering they don't have to be already signed up for the challenge but do have to have an AO3 account). The field will auto-complete to check that the user has an AO3 account and this may take a second.

Once you have done this click 'Assign' and an email with their assignment will be sent to them.

Once a pinch-hitter has been assigned they will not appear on the main table on the Assignments screen, but will rather remain at the top of the screen in the separate pinch-hitters table. By default covered pinch-hits are hidden, and uncovered ones are shown, but to unhide covered ones click 'Show Covered Defaults.'

Note: You can also default all participants who have not posted to the challenge by using the 'Default All Unposted' button at the top of the screen.

White button with black text titled Default All Unposted.

Close Challenge

To close the challenge so no more gifts can be added, go to 'Challenge Settings' and tick the box beside 'Is this collection closed?'

Tickbox with 'Is this collection closed selected. Is this collection currently unrevealed tickbox is unselected.

You can of course chose to leave this open if you'd prefer. :)

Reveal works

It's time to reveal the works!

To do this go to the Settings page for your challenge and untick the box that says 'Is this collection currently unrevealed? '

You can leave the collection closed if you don't wish participants to add any more works.

Tickbox with 'Is this collection closed selected. Is this collection currently unrevealed tickbox is unselected.

You've successfully set up and run a gift exchange challenge on AO3. Congratulations! :)


Post Header

2010-08-09 17:27:19 -0400

This isn't so much a meeting update as a general round-up of news from AD&T, since the writing up of reports, er... got away from me a little. But that means it is an extra tasty update!

Recent updates

We deployed new code to the Archive at the end of May - see the exciting list of new features in the Release 0.7.5. This release includes our new advanced search and a revamp to the HTML parser - this stuff was tricky to test and we're proud that the small amount of support requests suggests our testers did a great job of catching all the bugs!

Coming soon - Skins!

We're currently testing some awesome code on our Test archive. All being well, the next deploy will include the long-promised Archive Skins feature - you'll be able to choose from a range of lovely skins created by Archive staff, and create your own custom CSS. We know that lots of people have been looking forward to the opportunity to make the Archive look exactly the way that they want, and this will soon be possible! We're looking forward to seeing the beautiful designs people come up with. So exciting!

Rails upgrade - Faster! Better! More sparkles!

Our next big code project is to upgrade Rails, the application framework the Archive is built on. The latest version of Rails, v. 3.0, has lots of neat new features which will enable us to write much cleaner, faster code. In preparation for this change we have been writing lots and lots of automated tests, which will help us ensure we haven't broken anything in the move.

Refactoring - Code makeover

As we develop more automated tests and get ready to upgrade our version of Rails, we are also refactoring our code. Refactoring involves rewriting the code to make it much neater, more efficient and more beautiful. It's something which is necessary in all programming, but it's particularly important in a big project like ours with lots of contributors: by refactoring the code to make it more elegant, we make it easier for other people to work on it and smooth out any of the lumps and bumps which may have sprung up. Refactoring also improves the performance of code, and it's an important foundation for the next wave of development on the Archive.

Internationalisation on the Archive

We had a very exciting and productive conversation with the International Outreach Committee about the features the Archive needs in order to serve the fannish community internationally. All the work we have been doing on writing automated tests and refactoring will help a lot with developing our international features - we had to retire our old interface for translating the Archive because it caused some major performance issues, so we want to be sure that the new one we are planning will work smoothly. In addition to translations, we've also been discussing ways of improving our system for indicating the language of a work, browsing for works in particular languages, and setting useful defaults for language options. We're very lucky to have a brilliant International Outreach team who help us to see all the angles for our international membership - it's something we try to consider at all times, but it's very helpful having a team who are dedicated to this aspect of our work.

Introducing the new Tag Wranglers committee!

As most users know, the tags are the Archive are managed and organised by our behind-the-scenes team of dedicated and awesome tag wranglers. Until recently, tag wranglers were a subcommittee of AD&T, but there are now 133 volunteer wranglers working around the world to organise more than 99,666 tags, so it was high time for them to take on a more formal committee role. AD&T are very proud to see new committee chair Renay and her awesome team step out on their own: we'll be working closely with the new committee and we know that this change will help to ensure that Archive users continue to get a great experience.

News from our sub-committees and sister committees

  • Coders are working hard on writing automated tests, refactoring, and getting ready for the Rails 3 upgrade.

  • Testers are working on our new set of code on the Archive, and giving the new Skins option a workout!

  • Tag wranglers have been adjusting to their new identity as a committee in their own right, figuring out some new policies, and generally being awesome.

  • Support continue to do awesome work, answering most requests within a couple of days. They are a small but dedicated team and we value their hard work! (Don't forget that if you need a response from Support, you must leave a contact email address.)

If there are things you'd like to do or say, please share them in comments, via the AO3 support and feedback form, by volunteering, or in whatever medium you feel comfortable with. Everyone is welcome to this party!


Post Header

2010-07-16 05:09:37 -0400

Предлагаем вашему вниманию версию 2846 архива, которая приходит на смену версии 2732. Над этим релизом работали сразу девять человек! \0/ Нам особенно приятно отметить, что некоторые из наших новых программистов уже чувствуют себя достаточно уверенно для того, чтобы браться за все более сложные задачи! Мы также с огромным удовольствием приветствуем новых членов нашей команды бета-тестеров. :D

Ключевые моменты

Переработка кода и улучшение производительности

Наши ведущие программисты по-прежнему упорно трудятся над переработкой некоторых ключевых фрагментов кода архива с целью улучшения его производительности. Этот процесс включает в себя редактирование программного кода для того, чтобы сделать его более простым, более понятным и более эффективным. В целом это можно сравнить с вдумчивой, очень тщательной вычиткой текста. Обновленный код должен обеспечить заметные улучшения в плане скорости работы сайта. Это текущий проект, так что работы над улучшением кода будут продолжены.

Автоматическое тестирование

Наряду со внесением изменений в программный код, мы также работали и над улучшением автоматических тестов, в чью задачу входит проверка корректности работы нашего кода. Они упрощают процесс переработки (очень удобно иметь под рукой быстрый способ проверить, не был ли код испорчен в процессе редактирования) и помогают удостовериться в том, что внесенные изменения не вызывают проблем. В этом отношении нам очень помогли наши новые программисты. Мы используем систему под названием Cucumber, которая дает возможность писать автоматические тесты в более дружелюбном интерфейсе, и мы ради видеть, что ее возможности привлекают все больше новичков.

История просмотров

Мы добавили несколько новых опций в историю просмотров - одну из наших самых замечательных функций, которая позволяет отследить, что именно вы читали в Архиве, чтобы вы могли легко найти тот рассказ с наручниками, который вы читали на прошлой неделе. (Видеть историю можете только вы; в любом случае эту функцию можно полностью отключить в настройках аккаунта.) Теперь появилась возможность полностью очистить вашу историю просмотров. Также был добавлен счетчик, который позволяет вам узнать, сколько раз вы просматривали любую из работ. Если вы все еще не используете историю просмотров, то сейчас самое время начать - в будущем мы планируем существенно расширить эту функцию.

Известные проблемы

Со списком известных проблем вы по-прежнему можете ознакомиться в соответствующем разделе сайта.


Post Header

2010-07-16 05:08:21 -0400

Anmerkung der Übersetzerinnen: Alle Links in diesem Text führen zum Archiv, das zur Zeit nur auf Englisch vorliegt. Für weitere Details siehe die englische Version der Anmerkungen.

Willkommen zur Revision 2846, die auf Revision 2732 folgt. Neun verschiedene ProgrammiererInnen haben an dieser Veröffentlichung gearbeitet. Wir freuen uns besonders, dass einige unserer neueren ProgrammiererInnen an Selbstvertrauen gewinnen und mehr und mehr Bugfixes beisteuern. Außerdem konnten wir neue Leute in unserem Test-Team willkommen heißen. :D


Refaktorierung und Leistungsverbesserung

Unsere erfahrenen ProgrammiererInnen haben schwer geschuftet und wichtige Codeabschnitte refaktoriert, um deren Leistung zu verbessern. Refaktorierung heißt, dass der Code umgestaltet wird, damit er weniger komplex, einfacher zu verstehen, und effizienter wird. (Ein bisschen so, als würde man den Code gründlich betalesen.) Der refaktorierte Code sollte einige deutliche Verbesserungen in punkto Geschwindigkeit bedeuten. Dies ist ein andauerndes Projekt, und wir werden noch einiges am Archiv refaktorieren.

Automatisierte Tests

Neben dem Optimieren von bestehendem Code haben wir auch die automatisierten Tests verbessert, die prüfen, ob der Code auch das tut, was er sollte. Das macht das Refaktorieren wesentlich einfacher (da man schnell prüfen kann, ob Umschreiben den Code vielleicht unbrauchbar macht) und hilft sicherzustellen, dass weitere Änderungen keine Probleme verursachen. Auf diesem Gebiet hatten wir großartige Beiträge von unseren neuen Programmiererinnen – wir benutzen ein System namens „Cucumber“, das das Schreiben von automatisierten Tests viel angenehmer macht, und wir freuen uns dass sich dadurch mehr Leute einbringen.


Wir haben ein paar zusätzliche Optionen zur Chronik hinzugefügt. Dieses schicke Feature verfolgt, was ihr im Archiv lest, damit ihr (zum Beispiel) leicht zurückverfolgen könnt, welches nochmal die Geschichte mit den Handschellen war, die ihr letzte Woche gelesen habt ... (Nur ihr könnt eure Chronik einsehen, oder aber in den Einstellungen komplett ausschalten.) Es ist jetzt möglich, die gesamte Chronik zu löschen, und ein Zähler zeigt, wie häufig ihr ein bestimmtes Werk angeschaut habt. Falls ihr die Chronik bis jetzt noch nicht genutzt habt: es lohnt sich, und wir werden in Zukunft noch mehr Funktionen einbauen.


Post Header

2010-07-16 05:05:16 -0400

Nota de la traducción: Todos los enlaces llevan al Archivo, que por ahora sólo está disponible en inglés. Ver los detalles de la nueva revisión en la versión en inglés.

Bienvenid@ a la Revisión 2846, actualizando la número 2732. ¡Nueve programadoras diferentes trabajaron en esta revisión! \0/ Estamos especialmente emocionados de ver nuestras más nuevas programadoras ganando confianza y realizando más arreglos. Estamos también muy felices de haber recibido unas cuantas nuevas personas a nuestro equipo de pruebas.

Los puntos más destacados de esta entrada están ahora disponibles en English, Deutsch y Русский.

Puntos importantes

Arreglos de refactorización y rendimiento

Nuestras programadoras más experimentadas han estado trabajando mucho para refactorizar algunas secciones claves para mejorar el rendimiento. Refactorizar significa re-escribir el programa para hacerlo menos complicado, más fácil de entender, y más eficiente. Es un poco como darle al programa un buen beteado. El programa refactorizado debería conllevar algunas mejoras notables en la velocidad. Este en un proyecto continuado y vamos a estar refactorizando el Archivo mucho más.

Pruebas automatizadas

Al mismo tiempo que hemos mejorado el programa en sí mismo, hemos estado trabajando en mejorar las pruebas automatizadas que prueban si el programa está haciendo lo que debería. Esto hace que sea mucho más simple refactorizar (es agradable tener una manera rápida de probar que re-escribir el programa no lo rompió) y ayuda a asegurar que otros cambios no han causado problemas. Hemos recibido buenísimas contribuciones de nuestras programadoras más recientes en esta área - estamos usando un sistema llamado Cucumber (NT: pepino) que hace escribir las pruebas automatizadas mucho más amigable, y estamos felices de notar que está atrayendo a más gente.

Historial de lectura

Hemos agregado alguna opciones más al Historial de lectura - una de nuestras características más ingeniosas - que sigue lo que lees en el Archivo para que puedas fácilmente encontrar esa historia que leiste la semana pasada con las esposas. (Sólo tú puedes verlo, y puedes apagarlo en preferencias si prefieres.) Ahora es posible limpiar tu Historial de lectura completo, y hemos agregado el número de veces que haz visto un trabajo en particular. Si no haz estado usando el Historial de lectura hasta ahora, vale la pena hecharle una mirada - vamos a estar añadiéndole algunas nuevas características en el futuro.


Post Header

2010-07-16 04:59:55 -0400

The highlights of these release notes are also available in Deutsch, Español and Русский. Many thanks to our fantastic translation teams!

Welcome to Revision 2846, up from 2732. Nine different coders worked on this release! \0/ We're especially excited to see some of our newer coders growing in confidence and committing more and more fixes! We're also very happy to have welcomed some new folk to our testing team. :D



Refactoring and performance fixes

Our senior coders have been working hard on refactoring some key sections of code to improve performance. Refactoring involves rewriting the code to make it less complicated, easier to understand, and more efficient. It's a bit like giving the code a really good beta. The refactored code should bring some noticeable improvements in terms of speed. This is an ongoing project and we'll be refactoring lots more of the Archive.

Automated tests

Along with improving the actual working code, we've been working on improving the automated tests which test whether the code is doing what it should. This makes it much easier to refactor (it's nice to have a quick way to check that rewriting the code hasn't broken it) and helps ensure that other changes haven't caused problems. We've had some great contributions from our newer coders in this area - we're using a system called Cucumber which makes writing automated tests much friendlier, and we're happy to see it drawing more folk in.

Viewing history

We've added some more options in viewing history - one of our neatest features - which tracks what you read on the Archive so you can easily find that work you read last week with the handcuffs. (Only you can see it, and you can turn it off in preferences if you prefer.) It's now possible to clear your entire viewing history, and we've also added a count of the number of times you have viewed any given work. If you haven't been using viewing history up until now, it's well worth checking out - we'll be adding some more features in the future.

Known Issues

See our Known Issues page.

Release details


  • FAQ - Split FAQ sections onto separate pages for faster loadtimes and easier navigation.

  • FAQ - Added ability for admins to delete and reorder FAQ sections.

  • FAQ - Added validation so that all sections of the FAQ must have a title.

  • Improved search function to work with limited terms, so that it's easier to link to a specific search.

  • Added a list of all fandoms a user has created works in to user home page.

  • Improved the options for chapter edits on multi-chapter works so that work edit shows only the details for the whole work, while editing chapter by chapter shows the details for the chapter.

  • Made many small formatting and cosmetic consistency changes to the TOS and TAS FAQ.

  • Viewing history - added an option to clear entire history.

  • Viewing history - added a counter for the number of times you have viewed a work.

  • Collections - added 'x results found' to search results.

  • Improved URL autocomplete function on external bookmarks.

  • Added a way to add or remove an author from a series as a whole.

  • Added the ability to mark a series as complete.

  • Added a link to the account rename function from the edit profile page.

  • Added lots more automated tests!

  • Added some icons optimised for users with low vision as part of our ongoing preparations for alternative skins.


Bug Fixes

  • Fixed a bug which was preventing the editing of bookmarks created before we upgraded our bookmarking function.

  • Tweaked the wording of gift notification emails to reflect our current functions.

  • Ensured that all automated Archive emails include a link to our Support form.

  • Ensured that unused drafts will be deleted after one week (intended behaviour) - in the future we'll have better draft functionality, but for now this ensures they don't cause problems.

  • Fixed a bug which was causing unrevealed multichapter works to be inadvertantly revealed!

  • Fixed a problem where drafts in a series caused problems with series numbering and reordering.

  • Fixed a bug which caused a 500 error when someone other than the creator tried to access an unposted chapter in a work.

  • Fixed error redirects so that trying to access a page for a non-existent user gives a 404 error instead of a 500 error.

  • Fixed bug causing overlapping navigation on comments - you can reply to comments again!

  • Ensured that gift notification emails do not include an empty slot for the name of a collection if the gift is not part of a gift exhange challenge.

  • Tweaked the wording on our admin settings page to make more sense!

  • Fixed inspiration function to ensure that URLS are properly saved and it's possible to add more than one work as an inspiration.

  • Fixed broken comment links on multichapter works.

  • Added missing p tag in the TOS FAQ.

  • Tweaked work blurbs so that the count for bookmarks only includes publicly posted bookmarks.

  • Performance fix - moved values for hit counters to their own database table.

  • Performance fix - refactored the series blurb for greater efficiency and faster load times.

  • Performance fix - masses of refactoring across the site for cleaner code and much improved performance.

  • Performance fix - improvements to mass wrangling pages to make them much faster and more efficient.

  • Performance fix - refactoring on people page to make it load faster and be usable.


Post Header

2010-06-09 18:11:05 -0400

This was a landmark meeting for us - we got through the entire agenda! Several members of the committee were absent because it was a holiday weekend, and those who remained were slightly distracted by the Eurovision Song Contest, but apparently we were borne upwards on butterfly wings!


  • We discussed our volunteers process and ways of making it easier for more people to get involved. We have a lot of awesome and dedicated people on this project, but we would like to make it easier for new people to get involved and to spread the workload a bit! If you know of examples of good practice, we'd love to hear about them.

  • We signed off on a whole bunch of small coding issues which have been waiting for a final bit of design. Coming soon - more control over visibility to search engines, a way of removing a co-author from a series, and a fix for the editing of some old and buggy bookmarks.

Recent updates

We deployed new code to the Archive at the end of May - see the exciting list of new features in the Release 0.7.5. This release includes our new advanced search and a revamp to the HTML parser - this stuff was tricky to test and we're proud that the small amount of support requests suggests our testers did a great job of catching all the bugs!

Archive Roadmap

We've just released an updated version of our Archive Roadmap, which gives an overview of all the amazing work which has been done so far and all the cool things we have planned in the future. We're really proud of what we've achieved - fandom power is awesome! Thanks to our brilliant translations team you can also read the Roadmap in Deutsch or Español.

If there are features you'd like to see in the Archive, then we'd love to hear about them! Please contribute your thoughts to our post on the future of the Archive!

News from our sub-committees and sister committees

  • Coders are gearing up to work on a new round of projects. We're about to revamp our translations code so that it can be used, making improvements on advanced search, and thinking about priorities for new projects.

  • Testers did a great job getting everything ready for the last release, and are now working through the new code on the Beta Archive to verify that it's still working well.

  • Tag wranglers did an awesome job of keeping up with the wealth of new tags introduced onto the Archive during two big challenges - Final Fantasy Exchange and Remix.

  • Support continue to do a great job keeping up with support requests - for one golden moment there were no unclaimed issues! They also did a great job of swinging into action when our Support form had a momentary hiccup. :D

If there are things you'd like to do or say, please share them in comments, via the AO3 support and feedback form, by volunteering, or in whatever medium you feel comfortable with. Everyone is welcome to this party!


Post Header

2010-06-09 05:36:36 -0400

Edit 18.37 UTC, 9 June 2010: The issue has been resolved and the Archive Support and Feedback form is now open for business again! Please submit your feedback and support requests via this form. Many thanks to our lovely users for your patience, and to the wonderful people on our teams who resolved this so quickly.


Due to an issue with the tool we use to host Support bugs, the Support form on the Archive is currently broken. We hope to have the problem resolved very soon, but in the meantime you can get in contact with our Support team via the temporary form on our website. If you would like to leave more general feedback, please feel free to do so via email or by leaving a comment on this post.

Responses may be slower than usual, and requests that came in before our form went down may also be subject to delays. Our awesome Support team will be doing their best to keep up - please bear with us.

We'll update again when the problem is resolved - thank you for your patience in the meantime!


Pages Navigation