AO3 News

Release 0.9.15 (Part 9): Change Log

Published: 2014-07-28 23:53:14 -0400

Credits

  • Coders: Ariana, Elz, Enigel, Sarken, Scott, Stephanie Smith
  • Code reviewers: Enigel, james_
  • Testers: Lady Oscar, mumble, Sarken

Details

  • Subscriptions
    • Users' subscription pages previously listed all subscriptions on a single page, regardless of subscription type. Now series, work, and user subscriptions can be listed separately, and the lists are separated into pages of 20 items to improve performance for users with hundreds or thousands of subscriptions.
  • Tag Sets
    • When a user nominates tags for a tag set, we provide tooltips to let them know when they've nominated a tag that is brand new to the Archive or a tag that exists but is neither a canonical tag nor a synonym of one. Now we also provide tooltips so users will know when they have nominated a canonical tag, a synonym of a canonical tag, or a canonical character or relationship tag that doesn't match the fandom tag they've nominated.
    • The list of tags a user has nominated in a tag set received some minor cosmetic changes to make it neater and more consistent with other areas of the site.
    • When a challenge's tag set included a very long tag (e.g. "Stephen Colbert's Alpha Squad 7: Lady Nocturne: A Tek Jansen Adventure - Stephen Colbert"), Firefox users were unable to see the full name of the tag on the challenge sign-up form. Now they can scroll horizontally to see the full tag.
    • It is now possible to delete a tag set nomination, clear all nominations for a tag set, or delete the tag set itself without having JavaScript enabled.
  • Challenges
    • The error message warning that required information was missing from a gift exchange or prompt meme sign-up previously did not specify which request(s) or offer(s) were missing information. Now a message will also appear above the specific request or offer with the problem.
    • Previously, it was impossible for the moderator of a prompt meme to delete the last prompt of a user's sign-up. Moderators can now remove the entire sign-up, making it easier to keep bogus prompts out of a challenge.
  • Misc.
    • When a creator removed the only work in a series by editing the work and choosing the "Remove" button, they were redirected to the now nonexistent series page, resulting in an error. This has been fixed to redirect the creator to their dashboard.

Known Issues

See our Known Issues page for current issues.

Comment

A word about userscripts and add-ons

Published: 2014-07-21 12:22:14 -0400

As you may already know, we collect links to userscripts and other third-party tools for use with the Archive in our Cool Stuff FAQ. It's a fairly hidden page, and we have plans to create a dedicated space for it, but until then, this is where you find links to scripts and add-ons like AO3 Savior.

Unfortunately, the most popular script repository (userscripts.org) has been down for a while and will probably not come back. As a result, some of our links are broken right now, and while some workarounds exist, we'd prefer to update our links to point to new, hopefully more stable locations.

If you've previously uploaded an AO3-related script to userscripts.org, you might want to consider Greasy Fork (review) to re-upload your script, or host it on GitHub, Pastebin or similar. If you do, please let us know through our Support form or as a comment on this post. We'll update the list as soon as we can!

We also have some new tools waiting to be added, and we'll be sure to highlight some nifty additions when we've made sure all links are working again. If you have built a tool that's not on the list yet, please feel free to let us know!

Comment

AO3 Unlocked: Round-Up #1

Published: 2014-07-20 15:26:17 -0400

Banner (by Rachel) displaying the title 'AO3 Unlocked' with an open padlock in the background

We sometimes post little tips & tricks to our official Tumblr to highlight some of the many things you can do with your AO3 account, some of them a little more hidden than others. This is a round-up of some recent posts.

Mini-Tutorials

Other Tips & Tricks

Comment

Volunteer Recruitment for Web Developers and Elections

Published: 2014-07-14 13:11:44 -0400

Banner by Erin of a close-up of Rosie the Riveter's arm with an OTW logo on it and the words 'OTW Recruitment'

We would like to thank everyone who responded to our previous call for Tag Wranglers and Wiki Staff.

Today, we're excited to announce the opening of applications for:

  • Elections Workgroup Volunteer: Candidate Liaison - closing 21 July 2014 UTC
  • Elections Workgroup Volunteer: Communication Specialist - closing 21 July 2014 UTC
  • Elections Workgroup Volunteer: Voting Process Architect - closing 21 July 2014 UTC
  • Web Strategy, Design & Development Staffer: Web Developer - closing 21 July 2014 UTC

We have included more information on each role below. Open roles and applications will always be available at the volunteering page. If you don't see a role that fits with your skills and interests now, keep an eye on the listings. We plan to put up new applications every few weeks, and we will also publicize new roles as they become available.

All applications generate a confirmation page and an auto-reply to your e-mail address. We encourage you to read the confirmation page and to whitelist volunteers -(at)- transformativeworks -(dot)- org in your e-mail client. If you do not receive the auto-reply within 24 hours, please check your spam filters and then contact us.

If you have questions regarding volunteering for the OTW, check out our Volunteering FAQ.

Elections Workgroup Volunteers The Elections Workgroup is responsible for running OTW Board elections. We ensure the fairness, timeliness, and confidentiality of the process. As a team we will update the elections process, communicate with members and other committees about the process, help candidates prepare for and carry out their tasks, and run the election itself.

We have 3 specializations available, though all members of the workgroup will join in shared tasks and work together on projects. If none of the specializations perfectly match your abilities but you still think you could be an asset to the workgroup, please pick the closest match and explain in the optional details section.

Applications are due 21 July 2014 UTC

Web Developer Do you have experience with Drupal and website management? Join our team of Web Developers! Web Developers are responsible for improvements to and maintenance of the primary OTW web properties. You will participate in an on-call rotation with other Web Developers, design and implement new features and fixes for the websites, and help to determine priorities for future web development efforts.

Applications are due 21 July 2014 UTC

Comment

Release 0.9.15 (Part 8): Change Log

Published: 2014-07-13 12:45:00 -0400

Credits

  • Coders: Enigel, james_, sarken, Scott, Stephanie Smith
  • Code reviewers: Enigel, james_, sarken
  • Testers: Ariana, Enigel, Etharei, james_, Lady Oscar, mumble

Details

Important: We've been battling problems with our indexing process, which updates the search index for works and bookmarks when things are posted, updated, or otherwise changed in significant ways. While no actual data has been lost, we've been receiving reports of works or bookmarks not showing up where they should (e.g. work listings) or only after long delays.

As of this deploy, we've made some changes that should update the work index immediately upon a change, and refresh the bookmark index in batches (currently, once every 24 hours). This should help keep bookmark lists from being completely out of order, but does mean that some updates still won't show right away. We're working on more permanent improvements!

  • Works & Tags
    • Previously, "Choose Not To Use Archive Warnings" was selected by default in the posting form. We removed the default selection, to prevent unintended warning combinations when selecting additional warnings.
    • We also made sure the tag says "Creator Chose Not To Use Archive Warnings" everywhere else on the site, e.g. in the Sort & Filter sidebar. (We switched from "Author" to be more inclusive of non-text fanworks.)
    • Following a link to a deleted chapter would throw an error if the work it belonged to had also been deleted. Now it redirects either to the main Works index (with an error message), or to the work's first chapter if the work still exists.
    • Added a missing CSS class to the HTML mark-up for tag pages.
    • Cleaned up duplicate indexes in our database.
  • Collections & Tag Sets
    • A few years ago, we set up static pages for Collections to battle heavy load on our servers, e.g. during Yuletide reveal. Now that we regularly handle a lot more traffic than in 2011, the code for static versions of Collections has been removed.
    • An unapproved work would appear on a moderated Collection's dashboard (but not actually in the work listing) if it was also added to an unmoderated collection. This has been fixed.
    • When editing a work in an unmoderated collection to add it to another, moderated collection, there would be no message to the work creator that the work still needed to be approved by the collection mod. This has been fixed.
    • A user's Assignments page had a button that would allow them to send an email to their recipient as the Collection maintainer. This has been removed.
    • In Tag Sets with Ratings, Warnings, or Categories, the respective options (e.g. F/F, F/M, Gen) would be listed without any commas between them. This has been fixed.
    • On Tag Set nominations pages, the hover text for the ?! icon on unreviewed tags claimed they could be edited even after nominations were closed. It now just says they still need to be reviewed.
    • Cleaned up several HTML mark-up problems on Tag Set pages.

Known Issues

See our Known Issues page for current issues.

Comment

Heads up about a change to the posting form!

Published: 2014-07-09 07:12:01 -0400

Our upcoming code deploy will include a change to the default setting for Archive Warnings when posting a new work. Warnings are added to a work by selecting the relevant checkboxes in the "Archive Warnings" section of the form, either when creating or editing a work.

It is mandatory to choose at least one of the options, even if it's just to indicate that you do not wish to warn. Currently, the checkbox "Choose Not To Use Archive Warnings" is checked by default, allowing users who do not want to use warnings to skip straight to subsequent sections of the form. Unfortunately, this means that users who want to add warnings (or indicate that no warnings apply) must also remember to de-select "Choose Not To Use Archive Warnings." Because this isn't entirely obvious, a lot of works were unintentionally set to both "Choose Not To Use Archive Warnings" and "No Archive Warnings Apply".

After our code update, however, "Choose Not To Use Archive Warnings" will no longer be checked by default, requiring users to actively select it (or another option) in order to proceed. We hope this change will encourage creators to interact more meaningfully with the Archive warnings field, and ensure "Choose Not To Use Archive Warnings" is only ever applied to a fanwork deliberately.

Please note that other combinations that are seemingly contradictory are actually allowed by our Terms of Service. For example, you can tick both "Underage" and "Choose Not To Use Archive Warnings" if you want to warn for situations involving characters under 18, but not for other aspects of the work. You are always free to include more details about the content of your work in the Additional Tags, or in your Notes.

For more information about our Archive Warnings, please check the Warnings and Archive Warnings section of the ToS.

Comment

June 2014 Newsletter, Volume 81

Published: 2014-07-05 13:14:30 -0400

Banner by caitie of a newspaper with the name and logos of the OTW and its projects on the pages.

For more information about the purview of our committees, please see the committee listing on our website.

I. FANLORE PASSES 30,000 ARTICLES

On June 8, Fanlore reached the 30,000 article milestone with a post by Sparcicle on Nox et Lumos! The Wiki committee last celebrated a milestone in February when it reached the 500,000th edit on the site. Many thanks to all the gardeners and editors who have made this kind of progress possible!

II. MORE PROJECT NEWS

Legal has welcomed three new staffers, Diane Girard, Elizabeth Gray and Kalli, who bring diverse expertise to the committee. Legal has had another active month as they have continued to represent the OTW in the USPTO and NTIA’s multi-stakeholder process for improving the DMCA notice and takedown procedure. As part of that process, Legal has participated in several working group meetings and conference calls. Legal has also created two posts about legal issues of interest to fans, one on fair use and the other on the U.S. Court of Appeals’ ruling in the “Free Sherlock” case. As always, Legal welcomes your questions!

Open Doors has been tying up loose ends from the Yuletide archive import, and is working on preparing two other archives for a manual import.

Journal's issue No. 16, a guest-edited issue on material fan culture, came out bang on time. Thanks to the editorial and production team members for their great work, particularly Rrain Prior for her work as production editor. The next issue comes out on September 15. Co-chair Karen Hellekson will be attending Worldcon and is giving a talk on Doctor Who fan videos there.

III. OVER AT THE AO3

With the help of their new recruits, the Abuse Committee has successfully closed over 150 reports in the last month! Many of these were long-standing and complicated issues requiring cross-committee work and internal policy debates. As of now, the Abuse Committee only has about 30 pending reports. Because of this, their response time and productivity have dramatically improved. Meanwhile Content Policy made a few FAQ tweaks to address some common questions.

Accessibility, Design and Technology is continuing to work through our backlog of bug fixes, with five deploys and 52 issues closed in our bug tracker in June alone. AD&T were looking at a pile of almost 200 pull requests (code submissions) at one point earlier this year, some of which were over two years old, and they're now down to under 50! This has been a very satisfying and very exhausting process for the committee and our coders. They're now looking forward to digging into bigger projects and making plans for the rest of the year once more of the code mountain has been defeated.

Support held another chat to assist AO3 users, and in conjunction with Translation, was able to do so in multiple languages. Support's chair, Sam, extended thanks to all the longtime Support staffers who have made both their daily work and special events possible.

Tag Wrangling has had a month of working together on many, many tag-related Support tickets, and AD&T's latest code push included some excellent tag-related fixes. Tag Wrangling got a great response to their latest recruitment and is welcoming in the new volunteers. The Wrangling Staff hosted some staff-led training sessions for new and current wranglers in June. They were a rousing success and more are being planned for the future.

IV. INTERNAL DEVELOPMENT

Development & Membership is undergoing a leadership transition. The committee is saying goodbye to long-time chair Kristen Murphy, who is taking on a more silent role in premiums and CiviCRM support, but is appreciative of all that she brought to the OTW and everything she taught her staff. DevMem has begun working with other committees to start up the Visual Identity Group, which will focus on the OTW's visual branding. Meanwhile, convention outreach is undergoing an overhaul, with a current focus on Nine Worlds and Loncon.

Strategic Planning is in the process of surveying Legal, Finance, Category Change, Translation, Fan Video, Journal, and Fanhackers, and is making good progress on the reports for Support, Communications, Abuse, DevMem, and I&O. Their two newest staffers have finished their training and are starting to take lead on their own surveying projects! They have also started the succession planning process for committee chair, Hana, and are working on developing procedures for chair training.

Translation has welcomed 8 new staffers. With this increase in staff, they are working on strengthening internal procedures and making progress on new projects and ideas. Last month they were able to release the OTW video with subtitles in 16 languages! Huge thanks to all of the language teams who put in so much work on this project.

V. IT’S ALL ABOUT THE PEEPS

Volunteers & Recruiting has been recruiting for Tag Wrangling Volunteers and Wiki Committee Staff in June resulting in a slew of new names around the OTW!

New Committee Staff: Kiri Van Santen (Communications), MyraM (Communications) Katarina Harju (Translation), LilyC (Translation) Elizabeth Gray (Legal), Kalli (Legal), Girard (Legal), 2 other Communications Staffers, 1 Internationalization & Outreach Staffer, and 6 other Translation Staffers

New Tag Wrangler Volunteers: sarken, Night, Allons-y, Jamie Marie, bbcatemysoul, Elizabeth H, cadkitten, starrwinter, BearHatter, Gesundheit, Fredericks, justlikeheaven, Katarina Harju, defe, and 1 other Tag Wrangler volunteer
New Translator Volunteers: Anne-Katrin Koch and 3 others

Departing Committee Chairs: Kristen Murphy (Development & Membership)
Departing Committee Staff: 6 Abuse staffers; 1 Translation staffer
Departing Workgroup Members: 2 AO3 Documentation volunteers
Departing Tag Wrangler Volunteers: KeevaCaereni and 2 others

Comment

Release 0.9.15 (Part 7): Change Log

Published: 2014-07-01 12:33:37 -0400

Credits

  • Coders: james_, Lady Oscar, sarken
  • Code reviewers: Enigel, james_
  • Testers: Ariana, Enigel, james_, Lady Oscar, Runt

This deploy includes some updates to the Terms of Service FAQ. The question "May I post someone else's fanworks, giving them credit?" has been updated and the question "What about character playlists or fanmixes?" was added.

Details

  • Works
    • We have created a clearer and more detailed description of orphaning to be shown on the Orphan Works confirmation page. Hopefully this will make it less likely for users to orphan works in error.
    • .MOBI downloads of single and multi-chaptered works had different margin sizes. We have corrected this issue, and all works should have the same size margin.
    • When a user without any posted works looked at their Statistics page a message was displayed listing the types of information that would be displayed for any future works, including download statistics. Download statistics are not something we track, so that information has been removed.
  • Front-End Fixes
    • There was some incorrect HTML on the Sign-Ups page of challenges. Requests/Offers buttons are now properly coded as list items.
    • We also made some HTML changes to the Statistics page that won't alter anything visibly but which will bring it into line with our standard front end design.
    • Hovering over the ?! or ✔ or ✖ icons on the 'My Nominations' page shows a tooltip explaining what each respective icon means. The background color behind the text is now blue, in keeping with our standard informational messages, rather than yellow, which would indicate a warning message.
    • Previously, when a user viewed their nominations for a Tag Set, the "Status" message on the page always claimed that it was possible to edit or delete the nominations. Once a Tag Set is closed for nominations, however, the nominator can no longer edit or delete. The message will now change to accurately reflect the current state of the Tag Set.
    • There was some unnecessary HTML on the Works and Bookmarks index pages that created an empty navigation element. It has been removed.
    • Work blurbs on user and Collection Dashboard pages were getting extra padding between the title/author line and the fandom tag(s). They should now look the same as the blurbs on work listing pages.
    • There was a redundant reference and an unused selector in our stylesheets; both have been removed.

Known Issues

See our Known Issues page for current issues.

Comment


Pages Navigation