-
Notifications
You must be signed in to change notification settings - Fork 3
Collections Design v1.0
NB: Haven't moved images over yet
Content Policy are quite clear on this being called 'Collections' rather than 'Communities'
A Collection essentially consists of one or more maintainers (via the authorization plugin) and one or more Collection tags which the maintainers have control over, with a profile and some preferences. The overall purpose of Collections is to allow for groupings of stories with moderator control over the included works (like an edited anthology or curated museum collection.) Challenges are a sub-type of Collection, with more advanced features providing additional functionality for things like prompts/assignments, due dates, and author reveals.
These use cases have been collected from the OTW-Website, Livejournal and Dreamwidth.
Samvara is a keen fan of the Supernatural fandom and is particularly stuck on stories where Sam Winchester grows wings, she has an account on the AO3 and creates a Collection called SamOnHigh. She writes the blurb for the Collection giving guidelines on joining the Collection explaining she loves, loves loves Sam with wings but is willing to accept stories where any other Winchester has wings so long as Sam does too. Samvara messages every author on the AO3 with a winged Sam story that she can find, inviting them to join the Collection and promotes it shamelessly on the interwebs. One day someone tries to add a story where Sam grows tentacles but Samvara removes it from the Collection and messages the author explaining that even if he can fly, it's still not really WINGS now is it. They never speak again :( Eventually Samvara gets a debilitating disease and decides to put her energies into something else and makes one of her co-moderators of the community do all the work as she vanishes off to learn rock polishing in the desert.
ghostwriter is a Wally West (Flash, DC comics) fan that doesn't get tired of reading the same Wally West stories again and again. Except when she does. Eventually, she finds a collection of Wally West dark!fics, but sadly it has been all but abandoned by its creator. After overcoming her shyness, ghostwriter contacts said collection's owner to pimp a list of stories she believes should be included, and ends being granted moderation privileges, which makes her incredibly happy and scared as well. She's never moderated anything, not even her own expenses, and there are not rules or guidelines of any sort. She decides to make things up as problems/opportunities arise, and it works. Except when it doesn't. It takes a heated discussion (which lands the collection's subscribers in FandomWank, because of the astounding amount of macros linked to in less than 24 hours) about Wally West either being the third Flash, the only Flash ever existed, or Kid Flash, for her to decide that the fics have to be identified by source material, be it Live TV show, comics, JL:TAS, TT:TAS (or a combination of those), among others. Massive un-subscribing to the collection follows by those disagreeing with the new rule, but it is barely noticeable given the massive influx of new writers/readers thanks to the release of the Justice League movie. Things go smoothly for a few days, until some of the old subscribers start complain about the movie!fics being 99% of the new fics, which wouldn't be such a horrible thing if not for the terrible, terrible character-butchering the movie writers/actor are guilty of. After lots of name-calling and hissy fights, two new collections for movie!fic only and pre-movie!fic only are created, and the rats ... err, subscribers abandon the original ship collection. ghostwriter, by then only moderator/owner of the collection, decides to abandon it, as the amount of fic being posted is too much for her to read and add.
... until another fan of Wally West dark!fics appears, and the story repeats itself (this time with the release of the new Flash Live Action movie) ;P.
Zines!
Prudence wants to publish a zine. She wants to use the AOOO as a hub for all zine happenings, both behind the scenes and for public consumption stuff:
- Announcing a call for submissions - Accepting submissions (these would have to be for Prudence's eyes only) - Sharing information as to where/how readers can get hold of this zine.
Prudence also wants to archive the stories on the AOOO, but of course hers is the kind of zine that doesn't allow publishing of its stories online until 18 months after the hard copy publication. Therefore, Prudence wants her authors to be able to submit their stories to her zine in their final form (or submit them herself and give them author credit) at the same time she's publishing the hard copy, but set a timer on them - they are private until X date (ostensibly, 18 months after publication), at which point they'll be publicly available online through her zine's hub.
And the other thing I keep thinking of is:
Duplication!
When a participant posts a story for a challenge/exchange/zine/whatever, where is this story actually posted? If the author wants to archive their story in their own AOOO account as well, is it duplicated in the challenge's account/area? Or does the challenge simply refer back to the story where it is within the user's account, making what strings together the stories submitted probably a unique tag...?
Obv I have no idea what you have in mind already, but this intrigues me nonetheless. One of the reasons I'm all for the AOOO is that it's giving me an alternative to reposting/duplication (yay!), so I'd want to avoid that within the archive too!
Rich had a small website dedicated to Jonathan Strange and Mr Norrell, to which a few people contributed a couple wips. Unfortunately, the fandom was too small to hold Rich's interest for very long, and he wanted to shut down the website, but the authors of the fics were nowhere to be found, and he was left as the only caretaker of the few forgotten little stories. He never asked permission to archive the stories elsewhere, but otherwise they'll be lost, so he does it anyway, listing "anonymous" as the archive maintainer and the collection as "closed".
Over time, more and more people find the collection on AOOO, and send emails to anonymous, asking if he knows of any other collection of JS&MN fic, because the fandom is tiny and scattered and it's hard to find anything at all. Rich thinks about it, then changes the archive to "open" and adds links to every other JS&MN fic he can find, and changes privileges so that anyone else can as well. Some authors of the linked stories find out and add their stories to the collection on AO3. Some object and those links are removed and added to a blacklist so they won't be added again. Rich's interest is rekindled! He changes the maintainer to his own username and all is well.
The collection grows slowly, until a major movie studio announces they are making a movie of the book. Activity begins to pick up rapidly. Months later, the movie is released and the fandom explodes. There is drama and wank and all sorts of good things, and Rich is overwhelmed. He splits the collection along the movie release date, and requires any new submissions to check either movie or book 'verse radio buttons. Book 'verse stories go to the old collection, and movie 'verse stories go to the new one. He removes himself entirely from the drastically changed fandom, leaving Deb (book 'verse) and CJ (movie 'verse) to deal with all the crazies.
collection: zines. Ces is a zine editor who wants to backup a zine she edited in the AO3. The collection would run under the name of the zine, but each individual author would also have the right to claim the story for their user page. If the individual author isn't on the AO3, Ces still wants to have the story in the AO3 (many zine editors--particularly online zine editors--host their zines as a group on their sites or on a site dedicated to the zine, so this isn't odd). If the author later becomes a member of the AO3, she should have a way of claiming the story after the fact.
Betsy falls in love with a tiny baby fandom that overlaps at the edges with a larger fandom. Because that is how comic book fandoms usually work. Some people even call her fandom a sub-fandom, though Betsy would not agree.
Betsy's fandom, Genius Girls, is legitimately part of the comics megafandom Amazing Comics, because the Genius Girls comic is published by Amazing Comics and takes place in their shared universe. Also, three of the main characters of Genius Girls sometimes belong to the superhero team (and comic) Amazing People.
So the fandom tag on stories in Betsy's fandom is always Amazing Comics. But most Amazing Comics fic is about characters from the Superintelligent Dog People comics.
Betsy doesn't *care* about Superintelligent Dog People, and she doesn't want possible new Genius Girls fans to have to browse through pages of Superintelligent Dog People titles to find the Genius Girls stuff.
She also doesn't want people to have to individually search through all the Amazing Comics listings by character name for characters from Genius Girls in order to find Genius Girls fic, because while people will still probably find the fic starring Firequeen and Page, they probably wouldn't bother to search for fic about Marta or Janine who are more minor Genius Girl characters but totally a big part of the fandom and also awesome.
Over the course of several months, she creates a Collection and links every single fic, vid or fancomic she can find that features the characters of Genius Girls, even if it *also* features Superintelligent Dog People characters or other Amazing Comics characters in general.
She also includes Amazing People fic in the Genius Girls Collection, but only if it features the characters from Genius Girls in more than a cameo role.
Is it Amazing People fic? Yes. But since it features the Genius Girls characters, Betsy figures it is *also* Genius Girls fic as well as Amazing People fic. Even though technically it isn't a crossover since the characters canonically appear in both titles sometimes.
PART 2
Betsy thinks that the Amazing People tag isn't really sufficient, because Genius Girls were only in the Amazing people comic in 1998, 2004 and 2007-present, so the Genius Girls tag is really important if you want to only see Amazing People fic that stars Genius Girls characters and not random other Amazing People.
She also tags the fanworks by author, femslash slash het or gen, rating, individual characters, codenames of characters, WIP or completed and pairings if they have not already been tagged thus because she is anal retentive like that.
But then Betsy's tiny fandom isn't tiny anymore! It's suddenly ten times bigger! Aaaah! There aren't enough hours in the day, and Betsy has a life.
But luckily, other people can add to the Collection too, so that there is one coherent Collection instead of a bunch of Collections of pretty much the same thing, only all of them fairly incomplete. YAY!
So people who are browsing the Genius Girl Collection and decide they want Firequeen/Page slash and nothing else can click that tag. But people who want *anything* about both Firequeen and Page can click on the Firequeen tag and the Page tag while they are browsing the Genius Girl collection. People who want only Genius Girl fic by the author AmazingAmanda just click the AmazingAmanda tag and get that. People who want only PG rated Genius Girl fic that is also slash, regardless of *which* Genius Girl characters are being slashed click the slash tag and the PG tag along with the Genius Girl collection tag.
Betsy gets a five or six other fans to help her moderate the Collection. They're co-owners or subcontractors or something. Betsy really needs them and they're glad to help. That way when someone wants to put a Zod the Magnificent fic into the collection that doesn't even star any of the characters from Genius Girl, Betsy's co-mod Jane can remove the link, message the person who added the link and tell her that Zod the Magnificent doesn't count if it doesn't feature any Genius Girl characters. The argument by the linker that Zod gets crossed over so much that he is practically an *honorary* character in the Genius Girl cuts no ice with Jane, and the link is out. This is good because Betsy is busy writing fic in a different fandom and didn't even notice. Yay Jane!
PART 3
Er, and to clarify why this is a Collection in the first place, it is because it is a fandom that is not a fandom yes it is a fandom no it is not a fandom in those fluid boundary ways that comics tend to be.
Of course, perhaps someone at AO3 will come up with a better way of dealing with such
Collections: User RecStalker wants to set up a collection of fic recommended by them and others, so that the collection automatically includes all stories user A tags "recommended", user B tags "recs" and user C tags "gold star", but RecStalker still has the option to remove any of those stories from the collection and add other stories someone else may have recommended, without RecStalker having to tag those stories themself.
Collections: A fandom-specific comm called We Like Fic! runs a project called Ultimate Fandom-Specific Fic Rec List. Potential fics to add to the list are nominated at the We Like Fic! comm. Nominations link back to the fic on a specified web page, which may be a personal LJ, LJ comm, fandom archive, personal site, etc. Mods ask the respective fic authors if they want their nominated fics discussed and voted upon.
When author says 'yes,' fics are presented to the comm for open and critical discussion over a specified time frame (one week). Authors may choose to participate in the discussion if they wish. Discussions center on the merits of the story, and can get lively.
After the discussion period is over, the mod posts the poll, and comm members vote on whether the nominated fic should be added to the list. The mod tabulates the results, and adds the fic link to the Ultimate Fandom Fic Rec List, along with a link to the comm discussion post.
Time passes and a few fic links die. LJs are locked or deleted, sites disappear, etc. So mods would like to host a stable and centralized Ultimate Fandom-Specific Fic Rec Collection, with authors' permission of course. Hopefully each fic in the collection will link back to the relevant discussion post on the We Like Fic! comm; or, possibly, fic discussions can be archived in the collection as well.
Collections: If I've already posted, say, a fic from a challenge to AOOO, and later on someone creates a collection for that challenge, I'd like to easily be able to add mine.
zvi wants to start a Characters of Color collection. She wants to set it up so that any fic which lists a character she knows is a character of color comes to her or her co-collectors' attention, but is not added to the collection until they have read it and made sure that (a) the coc is the main character and (b) the story is not full of fail. She wants these subscriptions to be shared by the collection moderators (so if any one of the mods reads it, they (a) know that it is a potential for the collection (b) which character and (c) it gets marked read for all of the maintainers).
DrabbleLover creates a collection for Harry Potter drabbles. She is a drabble purist, and sets the collection so that only works of exactly 100 words can be added. When DifferentDrabbleDefinitionist tries to add her 430-word work, she receives a message that it does not meet the requirements of the collection. Over time, DrabbleLover decides that perhaps she's being slightly too strict, and allows works with a wordcount within a range from 98 to 102.
Samvara also TAGS her collection (wings, wingfic, supernatural wingfic, Sam Winchester, Winged!Sam) so that people looking by those keywords will find not only fics but also the collected list. RIGHT?!
Norah wants to run a challenge based on fanfiction based only on sources that are in the public domain. She does it pretty much like Samvara does, but because she is working with EENSY WEENSY FANDOMS she has to have triple the number of prompts and allow people to pick from among them (or at least indicate what fandoms they can write.)
...I think authors are almost always kept anonymous for an EXCHANGE, not a challenge. I'd love to be able to run an exchange off the archive, but I imagine that's several magnitudes more complex.
Norah wants to create a collection of every piece of Great Gatsby fic ever written. The problem is that most of them are not archived on AOOOO. Can she use AOOO to bookmark other sites?
Norah wants to be able to start several collections but not have them go public until they have, you know, enough stories in them to be worthwhile and not just sad empty shells that she Meant To Do Something With Someday. Can she keep them private while she adds to them and release them at a later date?
What if Thefourthvine finds a shiny Great Gatsby fic on AOOO that Norah doesn't have in the collection. Norah intentionally did not add this fic because it hits her food sex squick and she had to backbutton out of it. Norah's name is on the collection, and she does not want Foodsex!Gatsby in there. Is there an option for Norah to either allow or disallow other peoples' additions to the collection preemptively, so as to avoid Samvara's tentacle debacle? (And oh my God, that's so what thefourthvine and I should have called The Cetacean Situation - The Tentacle Debacle.)
...that's all I can think of for now.
I'm not really up to writing stories about myself in third person, but I second the posters above that for collections the inclusion of off-site fic would be very important to me. I don't anticipate AOOO taking over all of fandom any time soon (or ever), and while I'd love if it was easier to maintain my thematic lists than to have them on my own website, I wouldn't bother using an archive's function for collections if it was just for that archive. I mean, I don't do that on ff.net for the stories that fit my thematic lists there, because it really misses the point of a comprehensive list if just stories in one place are on it.
These are my original implementation notes that include a bit about collections for fic universes: Authors (or maybe just one) might want to use their collection to give easy access to a fic universe, which would require the ability to sort the fic (chronologically, but also with possible side arcs). A nicely complex example is here: Pegasus B Story Guide (refined)
- Collectors want to be able add AO3 stories to their collection
- Collectors want to be able to publish guidelines on joining the collection, and submitting works.
- Collectors want to act in a modly fashion: messaging potential authors, removing works from the collection (with explanations). They want the ability to have co-moderators, too.
- Collectors want to be able to tag works with Collection-specific tags
- Collectors want to be able to add works external to the AO3
- Collectors want to be able to hide/reveal works (possibly on specific dates)
- Collectors want to be able to import their collections from offsite and deal with the resulting ownership problems
- Collectors want to be able to open/close collections (mod retires, no-one takes over or time-specific Collection etc.)
- Collectors want to be able to split a Collection if the nature of the Collection changes (splits into movie'verse and book'verse)
- Collectors want to be able to let an author 'claim' a work in a Collection when they create an AO3 account (could be an external work or could be uploaded via an imported Collection)
- Collectors want to be able to take advantage of the existing AO3 tags and have them display in the Collection
- Collectors want to be able to let people submit works for inclusion in their collection
- Collectors want to be able to message people with AO3 accounts (and not just comment on works)
- Collectors want to be able to automatically add items to a collection based on a username+rec_tag combination
- Collectors want to be able to flag submissions for a collection so they can hold vigorous discussion before making them official
- Collectors want to be able to mark as Collection as 'Private/Hidden' so they can make it beautiful before they launch it
- Collectors want to be able to be able to pre-emptively blacklist certain works from being added to their Collection
- Authors want to be able to have an easy way to retrospectively add works to a collection when they get around to uploading them
- Authors want to be to able to mark universes in their collection, and note (and upload) side plots/stories.
- make Collection bookmarkable?
- does Collection description suffice or also add a Collection rules field?
- my feeling is we don't need an extra field, but description could get long considering how strong some maintainers regulate their community/collection
- make Collection description a required field?
- are tags required?
- I am voting yes, since it's such an important part of the design and many parts simply won't work without tags
- Do we have an addition Collection settings screen in the creation process or do we enforce standard settings that can later be changed?
- I'd be in favour of enforcing standard settings.
- allow External works or not
- Adding of external works is a manual process, the automated search doesn't work for it, for obvious reasons. * When creating a Collection the user must specify if they want to add an external archive (which would inlcude Zines) or do a Collection from stories in the AO3. Since story search and suchlike would obviously not be needed in that case.
- We don't want the big Archives to be imported at the same time and especially not without knowing that they are coming. So it would probably be a good idea to add a limit to the importer and also labeling it with that limit, so people know up front that only Archives up to a specific size can be imported.
- We should also add a link to contact OpenDoors in case their Archive is a bigger one.
- Adding an external work should be as prominently for the mods/maintainer as adding an internal work.
- The same goes for users, if users are allowed to add Archive works to the Collection, they should also be allowed to add External Works.
- Batch adding should be default as part of the Collection creation, whereas later on individual adding should be default, to reflect the user's needs.
- the Collection maintainer has the right to edit metadata/(edit story ?)/delete story/(orphan story ?) as long as the original author doesn't have an account
- this applies to Archivists who import external Archives and already have those rights
- Work page lists Collections it is part of
- also has a remove link if viewed by author/Collection maintainer/moderator
- Allow Collection Subscribers to turn off Collection Notifications (like change of maintainer, change of settings, change of status, maintainer messages)
- on a Collection to Collection basis?
- or on a one for all basis?
- Later Features
- Manage Zines (as in making new ones)
- If story is hidden because it was submitted for a Zine, will it only show up in the Collection (visible only to Collection maintainer and author) or will the author also be able to see it in their Dashboard (grayed out and with a notice that no one can see it because Zine, 11 more months)?
- split Collections
- message authors
- make Collection commentable
- Manage Zines (as in making new ones)
Collections can be divided into three subcategories (four if you add Challenges):
- whole existing external archives that have been hoovered into the Archive of our Own
- Zines
- thematic Collections of works already in the AO3
- Naomi will take care of the Hovering process, I just recommend that the Archivist should get a list of stories and some stats and should have to once more agree before actually adding stories to the archive.
- There should also be an indication of how many steps there are in the process, what those steps are and at what step the Archivist is right now
- What if there's an error and hovering fails?
- Will only parts of the archive get added (those up until the error)?
- Or will it roll back to the beginning?
- Will tagging and the likes be set back as well?
- When stories are imported into the archive by a user with the "archivist" role which is like the "tag wrangler" role, those stories have to be owned by the user who does the importing, because they otherwise have no other owner.
- We then go through various contortions to get the actual author to claim those stories but until that happens the archivist owns them in loco authoris.
- The collection itself is a separate thing. A collection itself is owned by a user but that user only has the right to determine whether a work is in the collection or not and does not own the stories in the collection.
- When hoovering an entire archive into a collection, 1 & 2 coincide.
- ExternalAuthorName
- external_author_id
- name
- ExternalAuthor
- id
- email (unique)
- user_id
- is_claimed
- do_not_email
- do_not_import
Then, when we create the work, the archivist is its owner, but we also create an object called ExternalCreatorship:
- ExternalCreatorship
- work_id
- external_author_id
- case 1: There is a registered user with this email address in the archive
- action 1: we add all the works owned by the ExternalCreatorships owned by this ExternalAuthor object to the registered user
- if the user has a pseud that also matches the name, awesome, we add them to that pseud
- if the user doesn't have a matching pseud and we did get an author name off the work, we either (this is a question what we should do)
- add the work to the user's default pseud
- or create a new pseud for the user with the author name
- as fallback we add it to the user's default pseud
- and then we send the reg user an email & inbox note saying "hey we are pretty sure these are yours, they were imported by archivist; if they are not yours, let us know here"
- and we mark the ExternalAuthor as claimed and assign it to that user
- action 1: we add all the works owned by the ExternalCreatorships owned by this ExternalAuthor object to the registered user
- case 2: there is no user with that email in the archive
- we send an email to the address saying "hey, archivist X has imported your story/stories into the archive. if you would like to claim them, here, have an invitation to create an account with us"
- it also says "if you already have an account with us under a different email address, please come here to claim them"
- and invitation objects will be linked to external author objects
- so that if someone creates an account using that invitation, they will be given all the stories automatically, even if they use an email address other than the one we sent the invite to
- case 3 is, we have no email for the author but we do have an author name
- Initially we will skip this because it adds complexity and also could be annoying, but one option eventually will be to send a note to registered users of the archive who have matching or similar pseuds and ask them "is this you?"
- case 4: we have no clue who wrote this thing
- action: depends on the archivist's settings on import.
- archivist can choose to:
- import it as a draft (to be deleted in a week if not posted)
- import it locked to reg users
- There could be a manual archive with no emails on the stories. We rely on the archivist's judgment. The archivist may very well know and add manually.
Since Zines are a mostly smaller number of works, as opposed to the usual multi-user archive this is closer to Thematic Collections than the big Archives we will take in. So it is envisioned as sharing a content module with Thematic Collections.
The managing of Zines (as in managing the creation of new ones) is a functionality that I haven't worked out yet, since I don't think it's crucial and I'll add it later after I have done all the basics.
- When adding storie for a Zine, posting must be done through Collection not through Post New, which we have to make clear. Since the work must be hidden for 12/18/whatever months.
There was some consideration if maybe building thematic collections might be more like moderated rec lists than Collections and therefor should become part of bookmarks. But interviewing some fellow fen (well, two) and looking at the scenarios added by people on tw.org/LJ/DW showed that the user expectations are quite clear in that they are seen as Collections and not as rec lists. When they think of a Collection, they think it is every story on that specific topic; it is about quantity, not quality. We could of course also add the functionality of moderated rec lists, but this is a topic for a different time and people can already do something like that right now with bookmark tags.
- link to create new Collection
- paginated, 25 entries per page (same as work page)
- sorted by date, newest on top
- also sortable by title
- Collection blurb
- display name (links to Collection view)
- title
- maintainer
- links to user profile
- says "this Collection is closed/orphaned" if Collection closed/orphaned and therefor no maintainer
- mods (if any)
- links to user profile
- description (limited to a specific length with a link to read the complete description if maintainers turn out to ramble on and therefor make the Collections page unbearably long)
- tags
- linking to tag page for Collections with that tag, if possible. If the page for the tag would also include Collections with the tag, then that's not necessary.
- display name
- title
- Collection status
- only if Collection is closed/orphaned or if it is a moderated Collection
- options to
- bookmark
- subscribe
- message the maintainer
- add content
- manage
- only visible to mods and maintainer
- Collection header
- maintainer
- mods (if any)
- description
- additional field for rules?
- items in Collection
- divided by bookmarks, works, (external works)
- tags
- option to edit (only for maintainer)
- pagination
- items in Collection
- sorted by date, newest on top
- except if a Collection has categories, then it's sorted by categories and the items in the category are sorted by date
- also sortable by title
- category header (where available)
- filter
- work/bookmark/(external work) blurb
- option to remove item
- for maintainer, mods and author
- sorted by date, newest on top
create Collection (step 1) wireframe
- from user dashboard, "My Collections" and listing Collections page
- enter title
- required
- at least 1 character long
- no special characters
- no spaces
- no longer than 25(?) characters
- enter display name
- required
- inform that display name can be changed at any time
- at least 1 character long
- no longer than 25(?) characters
- enter description
- required (?)
- at least 5(?) characters long
- no longer than 1000(?) characters
- Tags
- a Collection is tagable
- required(?)
- only freeform tags, since Collections don't have to be specific to one fandom and the list of tags can easily get too long
- minimum of 2 tags
- no maximum (?)
- The Collection uses tags to make the interests and category of it obvious at first glance, without having to read the complete Collection description.
- comparable to the User/Community interests in LJ/DW
- takes it possible to search for duplicate Collections before creation.
- the tags the Collection uses is checked against the tags other Collections use
- plus title comparison (?)
- cancel button
- redirects to Collections
- next button
- brings user to next screen
create Collection (step 2) wireframe
- search for similar Collections
- list of Collections that match tags (more than two tags?) with the Collection the user tries to create
- informing the user of possibly creating a duplicate
- user has to agree to create Collection anyway
- if no matching tags, this screen will be skipped entirely
- back button
- brings user to step 1, with all data still there
- cancel button
- redirects to Collections
- next button
- brings user to next screen
- add first content
- An automated search that can be run after Collection creation.
- uses the Collection tags to find possible content
- If a Collection is abut Sam Winchester wingfic and the tags are "Sam Winchester" and "wingfic, they will get all stories featuring Sam Winchester and a lot of wingfic across all fandoms, but will give the maintainer a hard time picking out the correlation between the two. And they don't need a search if they have to wade through the whole Archive anyways.
- But there will be times were the tags will be so random that connecting them will give less results than there actually are.
- So this is just an insane idea of mine and you coders have to tell me if something like this would work well enough to qualify the time developing it and to make the extra time the user has to spend on this worthwile. If the search will be unprecise this will without doubt annoy the user more than it will help
- Has the option for the user to search for works and/or external works and/or bookmarks+recs.
- We could tie this to what things the maintainer allows in the Collection settings.
- results are sorted by number of matching tags
- paginated, with 25 results on one page
- most matches on top
- results only matching one tag are ommited, but can also be displayed on demand ("show all" link)
- is automatically saved to Recent Activity page, so that the user doesn't have to go through all results at this very moment but can take her time
- can be skipped entirely
- checkboxes to select fitting works
- "add" button
- user stays on page after clicking, simply the added works disappear from the list
- "return to Collection" button
Add content from work page Add content from Collection wireframe
- from Collection
- users can add works from their own works, select the one they want to add from a dropdown menu
- users can add works/bookmarks from their own bookmarks, because there is a good chance that they have already bookmarked relevant works.
- option to add the bookmark or the work the bookmark was made for, if that is possible from a coding pov
- users can also add any other work either by entering the url or the title in the input field
- should identify if url is an ao3 url
- should display all works with radio buttons if there is more than one match for a title
- should only display complete matches, so if the user enters "and" only display works that are titled "and" not all works that have "and" in the title.
- cancel button
- redirects to Collection view
- add button
- adds items, redirects to Collection view and displays success message
- from work page
- "add to a Collection" link opens popup (just like bookmark popup)
- dropdown: add to a Collection in My Collections
- dropdown: add to a Collection user has subscribed to
- input field: add to a different Collection
- close closes popup
- Later shiny enhancement for another time: Users can simply add stories by drag&dropping them into a "Collection container".
- "add to a Collection" link opens popup (just like bookmark popup)
- from bookmark page
- same as work page
- after work creation
- tags are again used to produce a list of possible Collections this story could fit in
- user can check the ones that fit and add them or skip this step
- user can also disable this option (and re-enable it in their user preferences)
- as author, moderator or maintainer
- clicking remove opens new page, displaying the work/bookmark blurb
- user has to enter reason for removal
- cancel button redirects back to the page they came from
- remove button removes content and redirects to
- linked from "Manage"
- Maintainer settings are only visible to the maintainer, obviously.
- option available to maintainer and mods
- a Collection can contain and be sorted by categories
- This way a Collection for Hellboy fanfic could be seperated by movie and comic 'verse, for example.
- Or if it's a shared Universe it could be categorized by storyarchs.
- This would also make it easy to split the Collection later on (this will be a future enhancement).
- add category: title + add works
- add: add works + remove works
- edit: edit title
- delete: deletes category, option to also remove content in category from the Collection
- sort: manually change order of categories, standard is date created, newest on top
- order can be changed through drag&drop
- standard: on
- info text "Automated search is currently turned <status></status>"
- button: turn <other></other>
- alternatively: active/close Collection
- standard = open/active
- can only be done by maintainer
- button: close Collection
- redirects to new screen
- informs about consequences
- links to change Owner
- cancel button: redirect back to Settings
- close Collection button:
- closes Collection
- redirects to Collection Settings
- disables (grayed out) all options except open Collection and message maintainer
- As long as a Collection is open, the Collection is active and content can be added.
- If the maintainer doesn't want to update the Collection any longer, but also doesn't want to give it to someone else they can close the Collection.
- The info that this Collection is closed will appear on the Collection info.
- A notification to all Subscribers will be sent.
- This option will mostly be useful for Zines, since they have a fixed table of content.
- Only the maintainer can close a Colelction, they are also the only ones who can open it again.
- When a Collection is closed it can be opened again at any time.
- Admins should also have the right to open them again.
- This is an alternative for orphaning a Collection.
- If AD&T thinks orphaning is a better solution, then the process would be much the same. Only the Collection creator wouldn't have any access to the Collection and changing ownership would be handled through AO3 admins.
- can only be done by maintainer
- When a Collection is deleted, none of the works, bookmarks/recs or external works get deleted.
- The author of the works get a notification that the Collection was deleted
- The subscribers get a notification that the Collection was deleted
- Just as with work deletion the user will be asked more than once if they really want to do this and be informed about what it entails.
- button: delete Collection
- redirects to new screen
- informs about consequences
- links to change Owner
- links to close Collection
- cancel button: redirect back to Settings
- delete Collection button:
- asks "are you sure?"
- deletes Collection
- redirects to Collections listing with success message
- alternatively: moderated/public
- standard = open
- can only be set by maintainer
- checkbox "moderate Collection", standard is not checked
- save settings button
- If a Collection is open everyone can add works, even normal users that aren't the author. Everything will be added directly, there is no screening process. The maintainer/mods can remove works from the Collection again, but they do have to give a reason that will be mailed to to the person who added the work and the author (if that's someone else than the author).
- different cases:
- author adds story, nothing else happens, everyone is happy
- user/maintainer/mod adds a story, author gets notified that userX/maintainer/mod added storyY to CollectionZ.
- author adds story, maintainer/mod removes it, gives reason, author gets notified that story was removed for that reason
- user adds someone else's story, author gets notified, mod/maintainer removes it, user and author get notified
- If the Collection is moderated, then only maintainer/mods (and authors ?) can add stories.
- If an author adds a work it goes through a screening process and maintainer/mods have to approve the work before it's added.
- They have an additional "do not ask again" option, so if they select yes, the user can from then on directly add works wihout having to be approved. The same goes for the "no" option. If it's a troll or a spambot, the user will be added to a list of blocked users and can't add anything anymore.
- Users can also be manually added and removed from the blocked users list.
- We should probably log every user blockage in the user history in Admin:Abuse
- More about approved/blocked users in Blacklist/Approved users. If they don't want anybody else to add stuf, they can say so in the Collection details, which will at least stop the portion of users who read that kind of thing before doing something.
- standard: all allowed
- can only be changed by maintainer
- checkbox for every option
- The options are
- Works
- Bookmarks/Recs
- no differentiation between bookmark and recs
- External Works
This is a way for the maintainer/mods to see how the Collection develops and what they need to pay attention to. If the automated work search is turned on, the possible stories for the Collection will appear there. This is mostly a list to keep track of which stories where added by whom, which stories were removed by the author, which users added works... If the Collection is moderated, this is the place where work adding is approved or declined.
- There is no need for an approved stories list, since the Collection itself is obviously that already.
- Approved users are the ones that can add stories to the Collection without being screened by the mods/maintainers.
- In case of a private Collection that is only the maintainer.
- In case of a public Collection, that is the complete userbase, minus the ones on the blocked list.
- In case of a moderated Collection, that's the maintainer and the mods.
- The can set that no one else can be added to the list
- Or screen potential users and add the ones they like.
- The Approved Users list can be reset by the maintainer (should have to affirm at least once).
- The list is fixed according to the settings in the preferences.
- Individual users can be added and removed manually, but in general this is an automated process.
- Would only be visible to maintainer (and maybe mods). But could be visible to all users, if anyone thinks there would be demand for it.
- The approved list is strictly for users, the blocked list is mainly for stories.
- Stories that have wrongly been added to the Collection or stories the maintainer/mods have read and deemed unfit are on this list.
- If a work is added to a Collection, it is checked against this list and directly denied if it is a match.
- A reason must always be given for turning down a work, so this reason must also be saved in the blocked list.
- The reason must be editable.
- The list can be reset by the maintainer.
- Generally stories will be added automatically, but pre-emptive manual adding, as well as deleting, is possible.
- Also allow external works to go on the list?
- Would only be visible to maintainer (and maybe mods).
- Blocked users is hopefully something we won't need. If it's a spambot or suchlike, the maintainer should contact Abute to get the user deleted instead of simply adding it to the blocked list.
- Blocked users is something that can be abused by the Collection maintainer and lead to a whole lotta wank.
- I would be interested in what ContPol thinks of it, do we need a blocked users list?
- If we have a blocked users list, it would have the same options as the other lists:
- reset
- add individual
- delete individual
- Would only be visible to maintainer (and maybe mods).
- Stories belong to Pseud, only referenced in Collection, but visibility of story regulated through Collection
- Automated search
- can be switched on and off by the maintainer
- search results don't get automatically added, just presented to the maintainer who can then add the ones that fit
- Related to the Search for possible works, the user can set up a regular automated search for the Collection. It automatically adds all new search results since the last search to Recent Activity. The maintainer/mod can then go through the results and add the ones that fit and discard the ones that don't.
- This option can be turned off and on in the Collection settings.
- They can still add works manually, if it is turned off all stories have to be added manually.
- This search also has the option to distinguish between Works, External Works and Bookmarks+Recs.
- We have to decide if every result is an individual item in the Recent list or if the search result is one item which links to a new page with all the results.
- The first time a search is run (when creating the archive), it does a full search through all stories. This is too much for every search (right?). So after that, it should only search stories that have been published after the last search.
- But how would we handle works that are backdated? Do works have a created_at as well as a published_at field?
- Should we allow the maintainer to manually start a complete search on top of the automated search?
- Should the automated search be customizable if it runs every day/two days/week/month?
- Customize the date/time when it runs?
This could be enhanced later on, but at the very least there should be a way for the maintainer and mods to communicate with each other. Either through Private Messages or a sort of discussion board in the maintainer area.
There should also be an option for users to contact the Collection maintainer. To offer their services as Mod, for example.
- Maintainer to Mods
- Mod to Mods + Maintainer
- User to Maintainer + Mods
- Maintainer to authors in Collection
- Maintainer to approved users
- Maintainer to specific user
- Maintainer to Subscribers
Notifications are send
- to maintainer/mods when user adds story (appears in Recent Activity)
- to author when maintainer/mod/user adds a story of theirs
- to author + user wo added story (if different from author) if work is removed + reason for removal
- to maintainer/mod when author removes story (appears in Recent Activity)
- Maintainer
- Creator and/or owner of a Collection
- Moderator
- helps Maintainer, has certain rights, but not all
- Author
- User who has a work of theirs in the Collection
- Subscriber
- User who has a Subscription to the Collection
- User
- duh
- Archivist
- Maintainer of an off-site Archive that gets imported into the AO3
Okay, usually all of this would have to go into one Contentogram. But that would have become way too complex and no one could have read anything. So I split it up into different roles/processes. No idea if that is allowed, but it makes way more sense. maintainer/mods browse Collections create Collection
Media:Otw Collection-Wireframes.pdf
| User | System |
|---|---|
| 1) click create Collection | display "create Collection" |
| 2) fill in title, display name, description and tags | |
| 3) click next | check if input correct |
| compare tags with those of existing Collections | |
| if more than two matching tags: display list of similar Collections | |
| 4a) click "cancel" | discard data, redirect to user's dashboard |
| 4b) click "create" |
|
| 5a) add bookmarks/sources of bookmarks |
|
| 5b) run automated search |
|
| list works blurbs/bookmarks with checkbox, plus select all/select none | |
| 6) check fitting works and click "add" |
|
| User | System |
|---|---|
| 1) click "Collections" |
|
| 2) scroll through list | |
| 3) click on a Collection |
|
| User | System |
|---|---|
| 1) click "Manage" | load Manage Collection page |
| 2) click "Settings" | load Settings page |
| 3) click "delete Collection" | displays delete Collection page, explaining the consequences, links to change Owner and close Collection, with a delete and cancel button |
| 4a) click "delete Collection" | asks "Are you sure?" |
| 5a) click "yes" |
|
| 5b) click "no" | return to delete Collection page |
| 4b) click "cancel" | return to Collection settings |
| User | System |
|---|---|
| 1) scroll through list of items in Collection | |
| 2) click on title of specific item | redirect to work page |
| 3) read work | |
| 4) click browser back button | redirect to Collection home |
| 5) scroll to specific work again | |
| 6) click "remove" | popup "Are you sure you want to remove the work/bookmark from the Collection?" |
| 7) click "yes" |
|
| User | System |
|---|---|
| 1) click "add content" | show "add content" page |
| 2a) enter story title in input field, click "add" | display search results for title with radio button |
| (if more than one result) 3) select work | |
| (if more than one result) 4) click "add" |
|
| 2b) copy&paste URL into input field |
|
| 3) click "add" |
|
| 2c) select bookmarks | load user's bookmarks, newest on top |
| 3) select 1..n bookmarks | |
| 4) check "add original work instead of bookmark" | |
| 5) click "add" |
|
| 2d) select bookmarks | load user's bookmarks, newest on top |
| 3) select 1..n bookmarks | |
| 4) click "add" |
|
| 2e) select works | load user's 25 most recent works, newest on top |
| 3) select 1..n works | |
| if more than 25 works: 4) click expand | load all remaining works |
| 5) check more works | |
| 6) click "add" |
|
| User | System |
|---|---|
| 1) click "add to a Collection" | load Collection popup |
| 2a) select "My Collections" | load dropdown menu with all Collections user is maintainer/mod of |
| 3) select a Collection from the dropdown menu | |
| 4) click "add" |
|
| 2b) select "subscribed Collections" | load dropdown menu with all Collections the user has subscribed to and has posting rights to |
| 3) select a Collection | |
| 4) click "add" |
|
| 2c) select "other Collection" | load empty input field |
| 3) write the Collection title into the input field | |
| 4) click "add" |
|
| User | System |
|---|---|
| 1) click "view all bookmarks" for a work | load all bookmarks for a work |
| 2) click "add to a Collection" on one of the bookmark blurbs | load Add to a Collection popup |
| (see "add from a specific work page" use case for options on the Collection popup window, this has the same options, plus an "add work instead of bookmark of work" checkbox) | |
| 4a) check "add work instead of bookmark of work to Collection" | |
| 5) click "add" |
|
| 4b) don't check "add work instead of bookmark of work to Collection" | |
| 5) click "add" |
|
| User | System |
|---|---|
| 1) (on work preview) click "post" |
|
| 2a) check the ones that fit | |
| 2b) check "do not ask again" checkbox | |
| 3a) click "add" |
|
|
|
| 3b) click "skip" without selecting any Collections | redirect to work page |
| 4) go to My Preferences | load user preferences |
| 5) check "show Collection suggestions after work creation" | |
| 6) save changes | turn suggestions back on |
| User | System |
|---|---|
| 1) click "Manage" | load Manage Collection page |
| 2) click "Settings" | load Settings page |
| 3) scroll to "Manage Moderators" | |
| 4) click "add moderator" | expands input field with "add" and "cancel" button |
| 5) enter username | |
| 6) click "add" |
|
| 7) click "remove" next to a Mod | display popup "Are you sure?" |
| 8a) select "yes" |
|
| 8b) select "no" | return to Settings |
| User1 (current Maintainer) | User2 (possible new Maintainer) | System |
|---|---|---|
| 1) click "Manage" | load Manage Collection page | |
| 2) click "Settings" | load Settings page | |
| 3) enter Username of new owner | ||
| 4) click "change Owner" |
|
|
| 5a) click "change owner" |
|
|
| 1a) click affirmation link |
|
|
| 5b) click "cancel" | redirect to Settings page | |
| 1b) turn mod change down |
|
| User | System |
|---|---|
| 1) click "Manage" | display "Manage Collection" |
| 2) click "Settings" | display Collection settings |
| 3) scroll to Categories | |
| 4) click "add category" | expand input field with "add" button |
| 5) enter category name | |
| 6) click "add" |
|
| 7) click "rename" | turn category name into input field with rename and cancel button |
| 8) change name | |
| 9) click "rename" |
|
| 10) click "add" | load sort content page, display all items in Collection |
| 11) select items to add to category | |
| 12) click "add to category <x></x>" |
|
| 13) click "remove" | display popup "You are about to delete a category from the Collection. Are you sure?" with option to also remove the items in the category from the Collection |
| 14a) check "also remove" checkbox and click "yes" |
|
| 14b) don't check remove option and click "yes" |
|
| 14c) click "no" | redirect to settings |
| User | System |
|---|---|
| click "Manage" | load "Manage Collection" |
| click "Settings" | load "Collection settings" |
| scroll to close Collection section | |
| click "close Collection" button | display "You are about to close this Collection. Do you really want to do this?" popup |
| click "yes" |
|
| click "no" | return to Settings page |
- standard = public
There are a few options how to handle cases where full bloom public Collections are made private.
- Upon trying: Let them know that it can't be made private for these reasons and let them do all these things manually to give them the impression of a Big Thing that should be well-considered.
- Upon trying: Let them know that it can't be made private for these reasons, ask them if they really really really want to do this and if they agree the moderators and approved users will be removed automatically.
- Simply define that private Collections can be made public, but public Collections can't be made private again.