In my experience Just Watch is usually pretty accurate. Though I’m not sure if it works in a fully automated way or if manual feedback is sometimes relied on.
2 Likes
Did you actually check on JustWatch or was it only inaccurate on Natively? Sorry, I haven’t been good about syncing them regularly, planning on implementing that soon.
2 Likes
Ah, I didn’t realize they could be out of sync. No, I just checked Natively; I’ll check both in the future, though.
1 Like
FWIW I just built an autosyncer to keep them in sync… at least every month I’ll check.
I’m going through right now and doing another sync, so give it a check in a few hours and see if it’s fixed 
Edit: The sync is now finished.
2 Likes
How early is too early to request a book/volume? >-< What details do you need on Amazon?
2 Likes
I usually wait until at least there’s a cover and the page information, so @brandon doesn’t have to go fix it manually later.
I think he’s working on automating it, maybe it will eventually have a sync thing like movies and that solves most of the missing information.
3 Likes
I usually do the same as Megumin personally. Technically all you need is for the Amazon page to exist, but it won’t be update down the line unless someone specifically requests it.
2 Likes
While a cover is nice, if it’s a real book you can order, feel free to request. The only ones which I prefer not to add are future books without a cover listed for preorder on Amazon. If that’s the case, like @Megumin said, let’s wait.
Yeah, I actually had to implement an automated ISBN process for Korean actually (not for amazon, but another bookseller Yes24… amazon has terrible Korean coverage).
However, it really doesn’t work well without edition handling… book editions are such a mess as we all know. We will see how the automated process goes for Korean, but it’ll be very bumpy I suspect… and will require a lot of tools to help us link multiple editions.
Granted, this is just a problem we’ll need to solve. It’s probably the biggest hurdle to overcome when it comes to scaling the platform. I think it should be solvable… but it may need some help from the community! 
2 Likes
The latest JoJo volume has gotten a release date. In that case, I’ll stalk the listing once they make it until those things are up.
2 Likes
I’ve done that before. The book was released long enough ago that the Amazon page is some barebones thing some third party requested, so all you’ve basically got is the title and a cover placeholder image. Nasty stuff. I’m hoping as part of a future update we’ll be allowed to source the cover from elsewhere.
Yeah, even I balk at trying to organize book editions. :\ It’s going to be bulky and messy any way you do it, it feels like… I wonder if we could come up with a way to “opt-in” to specifying a book’s edition? Like, the default you would add would be something like what we have on Natively now, so it’s still an easy one-click system, but if you wanted to specify a certain edition you could dig through some menus or something to specify then.
Of course, with editions I’d also like to be able to add each edition as a separate book in my library…
Too many things to think about. 
2 Likes
Yes, absolutely. There will be a ‘main’ edition for every book with an option to specify an edition. So, there’d be an edition portion of the ‘book page’ where you could see alternates.
The real issues come in though when there are editions which don’t link up in volume number, or are different in some significant way. These would need a separate listing for the series, but still be tied together with the main series for grading. I think they’d also appear as links on each other’s pages, perhaps with a note.
I think if we had those two bits of functionality (a way to show editions underneath one book page and then a way to link separate series into edition bundles) that would cover basically every use case?
Secondarily, getting solid updating tools to allow us to combine two separate books into editions of each other and vice versa is another challenge. Updating user items (gradings / libraries ) can be a headache.
Ugh, if we get all that figured out it would bring me tears of joy… hacking edition book requests into the current system is the least favorite part of my job 
3 Likes
Speaking of Korean a few posts up @brandon, what outstanding tasks do you have left to do on the audiovisual stuff?
1 Like
Really just finishing up one or two stats things (mostly finished locally) and fixing a bug i found in the data manager. I’m also opening up a thread on Movie vs TV Show ratings to discuss how we feel about the current equivalency. If that goes well, I’ll fully toggle off the ‘beta’ moniker and we’re good to go.
… that’s not to say there’s not quite a few things left on my internal to do list around little bugs. But I think we’ll have reached a point where we got the core functionality working (uploading, syncing with TMDB, progress updates / data management, and stats). So at that point I will plow ahead to Korean.
I know I said in the past that I wanted to do content tags & favorites before moving onto Korean, but I’ve realized that’s it’s pretty important for me personally to get Korean on the platform. As I’m in Korea, I can’t tell you how many people i’ve met who are interested in the platform, but are bummed it’s only for Japanese.
But editions & content discovery are what i’m devoting myself to the rest of the year after Korean.
5 Likes
Awesome! Sounds like a good roadmap to me! Don’t sweat what goes in first and whatnot for features; it’ll all get there eventually, and imo Natively has good enough functionality as-is that there’s not massive desperation for anything in particular. It’d be awesome to have a Korean subforum I could spy on and shake my head in amazement at all these people reading this bizarre foreign language. 
3 Likes
These ahead of tags? As in tags won’t be implemented until next year at the earliest?
1 Like
There are a handful of QOL requests that would be nice to get before Korean if you can find a spare few weeks.
2 Likes
Are you planning on using Ridibooks and/or Aladin for Korean, or just Yes24? Also, what’s the Korean release timeline? I’m looking forward to it!
1 Like
Tags are practically the first thing after Korean… I am bucketing tags into content discovery.
Understood. I was going to do those first, but I’'m not sure now, as Korean has been very easy to implement.
For reference, I’ve already been using the site for a while now for Korean and it works as you’d expect. There’s only a few more tweaks, all of which have been specced out… not expecting more than a week. I had promised myself a while ago too that I’d have Korean out by end of June.
So when I said Yes24, I just meant that’ll be the source of the data, like Amazon operates currently. I think Yes24 has the best coverage, haven’t run into issues so far, but we’ll see. Happy to hear you’re excited! End of June is the timeline ~
6 Likes
I had no idea what content discovery meant and figured it was something like search improvements or global feed changes which was a 
3 Likes
Sorry, yeah that’s not terribly clear. The roadmap is pretty fuzzy after Korean. To be honest, i’ll probably spend the next few months on QoL improvements and cranking through the Product Requests backlog (Content Tags, Favorites, rereads… etc).
But ‘improving content discovery’ is a big product initiative I have in mind.
6 Likes
