Eg: https://archiveofourown.org/collections/HDWireless2021/works/new

From a review of the Firefox version https://addons.mozilla.org/en-US/android/addon/ao3-podfic-posting-helper/reviews/1722986/

"Only problem that I've found, if the original author has no work summary, it throws an error and won't import anything."

From a user request:

At the moment I'm changing this manually, but would it be possible to implement another standard title format? I know some people do 'podfic of' or some variation. For myself, I just want the p in [Podfic] to be lowercase, which is an easy change. I'm just curious because I find this extension so well built and helpful thus far.

Some people like to use an audio format tag like "Audio Format: MP3". Technically this could be done as another dropdown like the length one, but if we consider only canonical audio format tags we won't include "Audio Format: Download", which at 590 uses is more widely used than the canonical tag "Audio Format: M4A" ‎(325). Also, it's a little trickier because e.g. "Audio Format: Streaming" and "Audio Format: MP3" aren't mutually exclusive, so a lot of people will use both (14061 works as of right now, apparently.

Technically the audio format tags were the only ones specifically requested by the extension users I talked to, beyond a misunderstanding about the "Podfic & Podficced Works" tag, but I'm also wondering if simply allowing a free-form comma-separated list of custom tags would also help for the non-podfic use case, where someone wants to make filling in metadata easier by pulling from a similar work, but might be posting fanfiction or fanart rather than a podfic. They wouldn't need the "Podfic" or "Podfic Length: X" tags, but might want something else instead, like "Fanart".

There's a url parameter that can be added to AO3 links (e.g. https://archiveofourown.org/works/28542726/chapters/69946179?view_adult=true) that I suspect would let us avoid the special-casing around whether works are mature or not when we import metadata from them. I think that would mean less maintenance burden for that specific piece, and would also make refactoring less error-prone if we ever have any ideas for improving that part.

@irrationalpie7 says that we should support importing from collections URLs

As long as the URL is from ao3 and has "/works/[0-9]+" in it, if it's valid I'm pretty sure it'll be pointing at a work page. Relaxing validation will be useful for people just pasting in a url, because depending how you got to the page it may have some url parameters (view adult, or view full work) or end in "#someid" (in particular the previous/next chapter buttons on ao3 will send you to a link like this). This new matching scheme would accept all currently accepted urls. I don't know if we'd want to say trim trailing spaces? But also work urls shouldn't have spaces in them, so we could just have the final regex be something like "<ao3 base>/(.*/)?works/[0-9]+[^ ]*" to make sure there aren't trailing spaces

*Can't remember right now is it's supposed to be "works" or "work", but same dealio either way

A request that came in today from gee_dee:
"My only remaining wish is that I could fill in a template for end notes, but I'm guessing that's not possible? Other than that, THANK YOU SO MUCH bc it really is an incredible time saver!!!"

Thoughts:
Pop-up's getting a little crowded (my laptop screen is so small 😭) so we'd need to think how we present this to people if we decide to add it, and whether we let people pick whether they want notes to be at the beginning or end or offer both, but on the implementation side the template replacement would work similar to the summary

The site at https://lazycats.dev/ seems to have some issues on the bottom left, as I'm looking at it on chrome today:

Simple filtering that will improve things for the vast majority of users

User reported bug:

Hi! I love this extension and I use it CONSTANTLY, thank you for creating it. I noticed something last night that I thought I should let you know about. I imported a work that had been a gift work to someone else, and both the author's name and the recipient's name were imported into the new summary so that my new work summary read 'podfic of [title] by [author],[gift recipient]'. I have now removed the giftee's name from my summary, since they didn't write the thing, but I thought you should know.

The options page is getting kind of long, so I think it would be helpful to have a sidebar that highlights what section you're scrolled to/lets you jump to a specific other section

From a user request:

This is a bit of a long shot and isn’t part of the exact focus of the extension, but I’ve found the extension to be really helpful for posting a lot of similar drabbles (put a previous post as the source, to copy all the meta, then removing the podfic-specific elements and changing the title and summary). So a potential wish list item would be a checkbox to “copy tags only” (i.e. rating, warnings, fandom, tags, and the body html autofill). Again, totally realize this is out of scope but it’s been an interesting use case.

The preview complains that <iframe src="https://archive.org/embed/litany_202209/litany.mp3" height="30" width="500"></iframe> isn't supported by AO3, but all my podfic works use it.

Only if possible and do some in a very minimal way

Allow users to import from a series URL, importing tags (in the various categories such as fandom, relationship, etc) from all the works in that series.

Some things to consider:

• Some metadata (e.g. language and rating) are only allowed to have one value, but within a series might have multiple values. For rating, AO3 picks and shows the max (not sure how unrated works influence this). I'm not sure what to do about language--I guess we could just leave it blank if not everything in the series is the same, and then ao3 would complain when the user tried to save the work if they didn't pick anything themselves
• Pulling this info from each individual work in the series by going to its work page (which we already know how to parse) would quickly run into AO3's rate-limiting, so we should not do that
• The dom on a series page does seem to mark up the different kinds of tags with what category they belong to (e.g. character, freeform)
• Some info is only available on the works page, as far as I know (e.g., AO3 shows at most one "category" tag per work on a series page--F/F, M/M, Gen, Multi, etc)
• There's limits to the number of tags per work, that do not apply to tags for a series as a whole. If you go over the limit when trying to post a new work, AO3 won't let you save your draft until you're back under the limit. If there's a lot of tags, it could be very annoying to the user to manually get rid of the extras. Possibly we could show users an extra warning if they're going over the limit and tell them by how much?
• AO3 (a) doesn't allow you to set a series as the work that inspired you and (b) only lets you add one inspirational work per time you submit the new work form. I suggest listing the first work in the series as an inspiration and calling it a day

URLs like "https://archiveofourown.org/works/27305734/" are marked as invalid, but they are perfectly valid and should be accepted

Today I learned that you can omit works/(id)/ from the works/(id)/chapters/(id) portion of a chaptered work url. Since the resulting page still has all the metadata and such on it, and at least looks the same so hopefully is the same, we should be able to just add this as a supported format to the url regex.

Here's an example of such a url: https://archiveofourown.org/chapters/70248750 (the page it points to looks visually identical to https://archiveofourown.org/works/28656861/chapters/70248750 to me)

jocsykes reported that https://archiveofourown.org/works/1129500 threw an error: https://cdn.discordapp.com/attachments/750437912729878578/853306644863516742/Screenshot_2021-06-12_at_17.15.27.png