Every Missing Thing About Collections and Sets

:red_question_mark:For whom?

This topic is directed towards Notion users who are considering transitioning to Anytype and wish to know about the missing Essentials from The Databases only that could be bothering, and for the Anytype team, I know most of these features/Essentials could be on the radar, acknowledged, or currently in progress. since it has been spoken in Anytype Town Hall - Feb 2024

:waving_hand:t3: Introduction

Hey there! I’d like to focus this topic on what’s missing elements or could be improved in Anytype’s collections and sets. As someone who uses Notion a lot, I’m hoping to move over to Anytype soon, so I’m really interested in these areas.

First, I posted a poll on the main subreddit to see which software people used before Anytype or wanted to move from. Notion had the advantage, followed by Obsidian. This poll is not accurate because only a tiny portion voted, but I believe most people are transitioning from Notion to Anytype. This seems obvious since Anytype has made a blogpost comparing their product with Notion, and currently, there’re an import/export option from Notion’s service only.

Given that databases are the most powerful and important feature shaping Notion, and that the majority of users rely heavily on them for nearly everything, I would like to address some essential aspects. These are not necessarily features within the databases, but rather elements that are currently not in Collections/Sets.

:red_circle: The current Version I use is 0.38, I will update this Topic regularly adding :white_check_mark: emoji of every one that has been implemented in Anytype, And for Notion users Relation as like Properties to not get confused. without further ado get your coffee :hot_beverage: and let’s begin.

Priority high to low from my personal opinion

1. :gear: No Options to tweaks in Relations?

I’m slightly disappointed that the Relation type can’t be adjusted. For instance, in Notion, I can create a number property called ‘Goal Progress’ and display it as a bar, which I can then divide by a limit number such as 1000. If I input 500, it shows the bar as half full. Additionally, I have the option to change the format to percent, currency, and others. same for the other relations too.

The only type of relation that have solid options to tweak is
Object relation for now

2. :trident_emblem: Group by Object/Relation

This is one of the features I desire the most in anytype, as I find myself using it in every database and every view. ‘Group by’ is one of the key features that can organize your lists in any view, with the option to drag items from one group to another, like in these examples. In the left example, there is an inline database that I use in my goal dashboard, which is grouped by Status from ‘Favorites’, ‘Documents’, and ‘Archive’. I always group my documents in this manner and appreciate the ability to drag or create my documents such that their Status updates immediately.

And because I assume you can group objects both in a collection and a set by relation, it will be the best thing ever for Anytype to do. For example, making a set for recently edited and grouping by objects such as tasks, notes, and journal logs, so I can see which objects have been edited. The possibility is unlimited.

3. :card_file_box: Batch Editing for objects relations. :white_check_mark:

There isn’t much to note here, but editing and updating relations in Anytype is time-consuming. I hope this feature can be implemented as quickly as possible.

4. :straight_ruler: Formulas

It’s kind of self-explanatory, I know that anytype team working on formulas, I wish them all the best. /:

5. :magnifying_glass_tilted_left: General Enhancements in Filters + (or)

I knew this would be implemented as it was in the 2024 Q2 roadmap. However, I hope the filters, in general, will be improved from UX standpoints, as I find it a bit overwhelming. Additionally, the ability to group is also an important feature to add.

6. :high_voltage: Simple Automation For relation

Simple automation

For example, the first simple step when editing a journal log template is to automatically set the date field relation to today’s date, there’re many of These are typically highlighted in blue in Notion.

:police_car_light: Essential automation.

Secondly, and most importantly and find myself confused to explain and I didn’t find a workaround for Anytype, and it’s related to both automation and filters. For example, when I create a Project template, and in this template, there are two inline sets for the Document obj and Task obj, I want a filter to relate the tasks in the view of the template. This means any object that is created by the template will be the related object for tasks, similar to in Notion, I suggest something called ‘template origin’. So, when I create an object relation called ‘related to Project’ and link the project object to the Template, it should link automatically; that would be cool. I will try it to explain furthermore if not already clear.

7. :right_arrow_curving_down: Sub Objects, (Sub-Tasks)

Sub-objects are important feature to have in anytype using object relation it will be good to have for sub tasks and Sub Recourses, I guess!

I would like to be integrated in as many views as possible, such as grid and list view.

8. Recurring objects (Recurring tasks)

I personally use this feature in Notion to schedule recurring entries in my journal every day at 12:00 AM. This way, I’m prepared to write immediately. In Notion, you can set pages to recur daily, weekly, monthly, or even annually. For example, I can create a yearly recap, set to be generated once a year at a specific time and date, using a specific template.

9. :heavy_equals_sign: No Calculate Cell in Grid view :white_check_mark:

This’s dealbreaker for me since I use finance tracker to track my income and expenses. why there’s not Calculate cell underneath every relation. to Calculate by Sum, Average, Count all or the others.

10. :framed_picture: First Image as a cover option

In Notion, you can choose between displaying the page cover or the first image for a card preview. However, since the option to show the first image for the card preview is not yet available in Anytype, this has disappointed me. because in my hundreds of journal log pages, I set a picture as the first block on every page in my journal database. Particularly I like this because I don’t find it suitable to the cover to stretches, so I instead I set a picture. This is also useful for other things.

11. :cityscape: No Cover in Kanban view :white_check_mark:

Card preview whether First image or cover need to be in kanban view.

12. :cyclone: Wrapping in view

Adding the ability to wrap tables.

13. :wastebasket: Hiding Inline title

Still yet you can’t hide the title in both inline Collection/Set. it will be better even if I can lock the inline view.

14. :crutch: Easy drag and drop between Collections/Set

I wish it were easier to drag and drop between inline collections or sets (which should be the same). Furthermore, implementing a feature to copy from one Anytype window to another would be beneficial.

15. :package: Common issues to import inline view

Common issues such as inline databases not appearing occur when importing Notion databases. However, this isn’t a problem for me currently if you implement the concept of Sync relation. “Live Template” - An Idea for a New Relation Concept. since you can fix all in once using it with some tweaks you need to do yourself unfortunately

16. :magnifying_glass_tilted_right: Roll-up Relation*

Mentioned by @Dzlg

Roll-up works simply To Pull up Information from another related/linked objects.

For example, suppose you have a ‘Journal Set’ with a relation called ‘Related Tasks’. This allows you to display the related tasks for each journal log. However, suppose you wish to display additional information from your ‘Task Set’, such as Priority, Status, or the projects linked to each task. This is where the roll-up comes in. It not only retrieves this additional information, but it can also count the number of related tasks for each journal. instead of implementing in the traditional way check this Multi-dimensional relations by @Dzlg

17. :window: Global and Local view*

Mentioned by @sofalakatino

This is something similar to Notion. You would want a global view that maintains attributes from another view, such as the main set or collection, or inline. Additionally, there’s an independent local view that you can transform to Global. It would be nice to copy these views and add them elsewhere like the main set or inline view.

18. :date: Calendar update*

Still, in the Calendar view, you cannot easily create an object by hovering over the day cell and creating an object and dragging it to another day.

Additionally, the ability to right-click and clear the date relation is not yet available.

:end_arrow: In the End

There’s one barrier that still prevents me from transitioning to Anytype, and it’s the Collection and Sets. As a Notion user, the most important elements are the Databases. I use them extensively, and I find that the Collection and Sets feel incomplete, which is understandable since it’s a beta product.

I don’t mind if certain blocks are not yet in the editor, nor plugins and the others. The only thing I need to be in place is the fully functional Collection and Sets, so I can float in the boat and enjoy the rest. Big thanks to the Anytype team for all their hard work. :+1:

Feel free to give me feedback so I can add it in the topic.

And yeah, if the Database was one face of the coin, the other side of the coin would be the Editor experience. make sure to check this topic If you want to give Anytype team genuine feedback of the editor. Basic editor experience. Help needed! - Any Talk / Consult the Community

I just want to say thank you for writing this out.

Most if not all of these I agree 100% on you with.

I also want to thank.
Such a high-quality post! :+1:

Thank you for expressing my and many others’ ideas and thoughts!

Absolutely amazing and quite detailed post! Kudos buddy! :ok_hand:

The only thing that I would add besides the multi-dimensional relations is the roll-up/relation feature of Notion Data bases.

I would like to mention this later in this post as the Point Number 16. Although I don’t use the roll-up feature in Notion, it might be cool to start utilizing it as the multi-dimensional relations. Even so, I’m still confused about it and probably need to reread the post.

Another minor thing, after everything else is sorted out:
17. Keep a consistent view for inline sets/collections and their independent set/collection. If I make a change to the view of an inline collection, I want to see that same adjusted view when opening that collection.

One other tiny thing I would add to this list is the ability to hid the views, the name of the set/collection in the inline form. Right Now, the inline “views” are not tied with the original set but the Name is. Like Notion, having the option to hide/change both is a quality of life improvement.

:+1:Got it, I will try integrating this into the topic in the Number 13, and add the others in the Point 18.

good job, bro.

Excellent documentation/analysis work!!

All my major gripes too, and I don’t even come from Notion!

I think the only thing that I wouldn’t miss, would be using cover or first image. I guess in that case, I would change the cover directly. But all the other points are great and issues I have noticed too!

Look, sometimes I don’t like using the cover in Notion, simply because when I’m journaling, the cover cuts from the top and bottom. It doesn’t display the whole image, like when I capture a picture for the day. This issue is even worse for portrait/vertical photos.

In another situation, when I use the web clipper in Notion, it extrudes the content from the page. Whatever the first image on the page is, it automatically becomes the cover of the page, which’s what I want.

Great post, I’m not even coming from notion I’ve been messing with sets fairly heavily and would love to see a lot of this gone over.

Here’s another, hopefully simple enough that it can come quick:

14.5. Allow adding objects to a collection on the collection page.

Besides mouse-dragging an object into a collection to create the link, it would be great to also be able to add an object to the collection from the collection page.

By way of example, I just created a collection called “High yield”, where I want to add a series of select objects (of different types). The way things are now, to add the objects I need to search them, open their page, open the menu, and mouse-click my way to link them to the collection. It would be much simpler and more intuitive to have the option “add to collection” on the collection page. (Naturally, this will open a search dialogue and the selected object is added to the collection.) IMHO, this will also make the distinction between collections and sets clearer.

(My current workaround: a single “high yield” page with multiple inline sets, one for each type. Each inline set gets a new checkbox-relation, “High yield”. After I search&find the object in the set I can mark it as such, and then filter to view only marked objects)

It seems like a good thing to have, but in your case, I suggest something even better. This would be a type of filter that you can apply to the sets, forcing any object creation to be within the collection you want. For example, in your ‘High Yield’ scenario.

But there’s just one flaw - you can’t create objects from the quick capture menu because you can’t put a filter on the creation. but I’m not aware if you can apply linked collection on the templates.

Creating a new object within a collection is simple enough. The issue is how to facilitate bringing existing objects into collections. Maybe a filter in Sets can help do that, but I didn’t really understand how, and I suspect it would just add to the confusion between the two.

Agree with everyone here, great comprehensive post!
Thanks for sharing and still being hopeful that Anytype will be the super app we’re wishing for. :slightly_smiling_face:

Absolutely great post. We are listening here, some things you were mentioning here already in works. We’ll update you here as soon the the designs of the next iteration collections and sets are there

Hopefully, these features will be implemented one by one in the upcoming updates. That’s what will excite me and many others to switch to Anytype. :+1:

All these features will be implemented. Some are easier to make, some are really hard due to our current architecture.

We are reworking sets and collections right now, to combine both in one (we plan to name them lists) and allow easily [batch] adding to them via query or one by one.

From your list what is comming first:

Batch editing

Advanced, but simplified filters

Calculate cell in grid

First image as a cover

Easy drag and drop between collection and sets

Very hopefully grouping.

Synced views for inline collection/sets

Templates for sets/collections

Hiding inline title and lock the view is not a problem

Rollups and tweaks of relations are part of a different project - relations 2.0. No eta right now, but hi priority