Thread: Different Stories - Same Series Name

StaticHD
posted on
16:25 on 26 November

I came across two different series - but of the same title. I enjoyed one, and disliked the other. I saw or thought there was an update for that series, but it turned out to be another series.

World Seed - https://www.wlnupdates.com/series-id/2844

This site currently (at least for now) updates the same series profile as if they're of the same story of chapters. This is understandable if it were a series that was being translated by two or more different translation groups - but it doesn't work well with Original English Linguistic story titles.

My only suggestion is that you separate the titles using the same method that MangaUpdates.com uses. For example, these three series share the name - but, they are separated with their author/artist name in parenthesis.

Impulse (JUNG Min-Yong) - https://www.mangaupdates.com/series.html?id=128490

Impulse (Maami) - https://www.mangaupdates.com/series.html?id=77075

Impulse (Brazil) - https://www.mangaupdates.com/series.html?id=73283

So, it should be like this:

World Seed (Viken) - The story I prefer.

World Seed (Karami92) - The story I do not prefer.

This is just a suggestion. If you want to do something different that makes more sense, then please do. I just found it extremely annoying that I had to guess which story I was reading when I only preferred one of them. So if you can re-program your bots to detect different authors of the same title & have them respond accordingly, that would be great.

Thanks for reading. I hope my English was understandable.

fake-name
posted on
21:27 on 29 November

Your english is fine.

Huh, I had assumed RoyalRoad didn't allow duplicate series. That's very annoying.

Let me see if I can think of a way to disambiguate.

fake-name
posted on
00:51 on 30 November

Ok, I put together a system that tries to match selected update sources (basically, all the OEL content) by both title and author.

The first item under a name gets to be the eponymous series, and anyone who uses it afterwards gets coerced to {Series name} ({Author name}).

For example, see: https://www.wlnupdates.com/series-id/2844/ and the (new) https://www.wlnupdates.com/series-id/33459/.

It's not applied to the RSS feeds, but that may change. The issue there is different groups working on the same series.

It also doesn't allow OEL and translated releases to be sorted together, which should also help some other name collisions I had fixed manually in the past.

If you find anything with broken releases, let me know, and I can reset the release list for the item.

Alternatively, I could just give you mod access, if you're interested.

fake-name
posted on
00:53 on 30 November

Oh, also potentially interesting to you.

You brought up the idea of having a wiki that interacts with the site, and I've been working on implementing something like that. I still need to finish significant chunks of it, but it's very definitely on the TODO list.

StaticHD
posted on
00:40 on 5 December

Wow, I haven't visited the Internet since I posted that. Been studying for exam. Anyways, sure - I'd love access to help out, if possible - (who wouldn't).

The fix isn't perfect, since it seems like a manually done fix and I doubt you know how to make the system correct itself. According to Google, coding an Ai is possible, it's just extremely difficult depending on which method you choose to follow.

fake-name
posted on
02:33 on 8 December
 The fix isn't perfect, since it seems like a manually done fix and I doubt you know how to make the system correct itself. According to Google, coding an Ai is possible, it's just extremely difficult depending on which method you choose to follow.

Actually, the changes you see are automatically generated. I did have to flush the bad, merged series page, but the generation of the additional series page, and proper filtering of any later updates is automated.

fake-name
posted on
02:52 on 8 December

Ok, I flipped the moderator switch on your account.

Principally, this means you can now delete releases and series-pages, as well as modify the "countability" state of releases. You can also merge series pages if there are duplicate series.

Release management is available via right-click menu on the 4 right-hand columns of the release table (the two left-hand columns don't override the menu, so right-click->open-in-new-window isn't broken).

Toggling "Countability" takes a release item out of the "Latest release" determination mechanism. It's useful for situations where chapters are not released in-order. Additionally, the right-most column indicates the state. ◯ means counted, ✖ means not counted. The right-click menu also has upload-times and info on who uploaded an item.

Merging an item is done by item-id, which are part of the URL: <https://www.wlnupdates.com/series-id/33626/> has an item-ID of 33626. If you want to merge that page into another, you go to the other page, and put 33626 in the Merge into series ID box.
The two pages will be merged, and the one with the smaller item-id number will be the new aggregate item. This process will update any reading-lists, and properly merge all multiple-item fields, though for things like the description, the lower-id page wins.

Other then that, there isn't much in the way of exposed admin functionality. I'm bad and tend to just use the command line to fix things in the DB if I need to.

The "Delete Auto-Releases:" button deletes all the entries generated by the automatic system, while leaving any manually added releases. This is principally useful for situations where the feeder has screwed up and generated a lot of garbage releases - the next time the page is walked, it deleted items will be re-added in their current state.

It's worth noting that deleting auto-generated releases that are still present on the remote site is something of a losing proposition, as they'll simply come back the next time the page is walked. If they're being generated wrong, let me know and I can patch.