Use Relation(s) as Tags!

So recently I discovered that you can create a set from a relation. At first I thought, damn this is cool but I wouldn’t use it or I don’t know how.

For those who don’t know, you can create a set when you click on the relation you want in the Library.

Then it suddenly hits me, use your relations as tags! Yes, you read it correctly! :smiley:

Let’s say you have a project and lets call it “Project Relation as a Tag”, where you need to manage people, meeting notes, project information, notes and more. All these objects can and should be their own type (people, notes, etc) with all the relations you expect for those types…

Then you just add the relation called “Project Relation as Tag” to those people/notes/objects part of that project and you can make a set from all those different objects! This can be any relation type that you don’t even have to use or fill in!

But that is cool and all, but you can level up this “Relation as a Tag” by making it a Status relation and give each object type the same status name. Now you can filter on these status/object types. For example, make a Kanban view of all your project objects.

9 Likes

Great case!

Actually, I have ever thought about the difference between tag and relation. Firstly, tag is a type of relation, but I supposed that relation is something like tag (or attribute?) with an additional domain, which is more powerful and convenient for work organization.

For example, I could tag objects with various values, like ‘sci-fi’, ‘magazine’, while relation can offer a more specific range. I can create a relation named ‘genre’, and the values are ‘sci-fi’, ‘magazine’, which is more clear.

So in my imagined workflow, I will use tag directly instead of specific relations in these situations: (I have not used AnytType so deeply yet :sweat_smile:)

  1. Frequently used relations.
  2. General relations.
  3. Relations that are difficult to classify.

These three types may have overlaps, e.g., I usually use ‘Tmp’ and ‘Personal’.