I apologize for the misunderstanding
I’ll try to describe more clearly.
Testing is a process designed to reveal information about the quality of a product relative to the context in which it is to be used. Users with access to the nightly builds, as far as I understand, not only have access to new features, but also have a higher risk of data loss than us alpha testers (my opinion).
And it’s really cool that you use the night versions of Anytype at the most comfortable level — you’ll be able to provide quality feedback and improve Anytype
Thanks again for creating amazing projects that inspire others!
That’s the result of using inline sets. I use inline sets to show an actors movies/shows and vice versa. So, there’s a customized movie/show set in every actor/director’s page and a list of all the casts in the movie/show’s page.
hmm, at the moment I’m doing all this manually mainly duo to 2 reasons. first being that I’m waiting on the release of the Anytype’s API later this year before doing any sort of automation. secondly, a lot of this is carefully picked based on my taste ( e.g. the posters, profile pictures and cover images); So, I have to manually select them but I hope I can automate the scores, ratings and other data in the future.
Well that makes it even more impressive then. Gotta step up my game haha.
I do really love how simular your approach is to my own when it comes to a movie database, including directors, actors and more connected information.
Edit: Btw fanart.tv has a lot of movie posters, logo’s and more art work to pick from. I usually go for the movie thumbs for my images in gallery view, then I have a poster in the page itself (like you do as well).
Wow, really amazing work! I would like to have something similar to your DB one day
In Notion I have a similar thing running which works amazingly with the help of API. It was created by someone really talented, called Notion Watchlist ( https://www.reddit.com/r/Notion/comments/rqmowq/release_notion_watchlist_powered_by_api_public/ )
I hope after the release of Anytpye’s API you or someone else will create something similar and share it with the community (not only for media, but also for games, books, etc)
wow! the automation is amazing there I hope we can achieve a similar level of automation here in Anytype after the release of the API.
But one advantage that anytype has over Notion which was also apparent in the video, was that in Notion you can’t define relations which can be filled with other objects/pages; for example you can’t define a relation called actors which is then filled with all the cast & crew which by themselves are objects of their own! That’s what I love about Anytype!
Yeah, exactly! This Notion watchlist only works like a standalone database, without relations to other databases of actors, directors, distributors, genres and so on, writes all these properties not as relations, but as text, tag or number mostly, which is sad and probably barely even possible in Notion
Tho automation by API makes this thing very powerful and convenient to use, simplicity beats functionality for now.
I also hope something like you described will be created in Anytype with the release of API, tho I don’t have an idea for now on how to implement it. Probably parse the info from IMDB about a director, for example, and make it an object with a separate type (human). and if such human was already in my Anytype, then link this object instead of creating a new one…
Anyway, im not a programmer, im sure smart people in Anytype will figure it out
When they will, it will be an OP solution, much better than most notion’s manual media DBs, and better than this Notion Watchlist!