List of already assigned values from a property-keys

[SiliasOS]

Hi there,

How can I generate a list of all the already assigned property-values of one specific property-key?

For example, I have a property-key, called “city”, and sometimes I have one city-value and sometimes more than one city-value assigned to that key, e.g.:

---

— note1—

---
city: Los Angelas
---

---

---

— note2—

---
city: Florida, Los Angelas
---

---

---

— note3—

---
city: Florida, Munich
---

---

=> Now, I want to produce a List of all citys, I already have assigned, like:

• Florida
• Los Angelas
• Munich

… I found a helpful thread here:

Making lists with Dataview of all values in use in metadata field

This worked for me: LIST GROUP BY join(location, ", ")

, which produces the following output:

• Los Angelas
• Florida, Los Angelas
• Florida, Munich

=> but I want to generate a list, where every city only occurs one time

Do you have an Idea, how to accomplish that with dataview, or is it necessary, to use dataviewjs for that job?

Thanks in advance,
kind regards,
Silias

[Pch]

If your city key is of type list…

E.g.:

---
city:
  - Florida
  - Los Angelas
---

… this query :

```dataview
LIST 
WHERE city
FLATTEN city
GROUP BY city
```

Seems to return a list of unique city across the various notes containing a city key:

- Florida
- Los Angelas
- Munich

But I’m not enable to make it work for a text type city key .

I hope someone more experienced with Dataview than I am () will be able to give you an appropriate query .

[SiliasOS]

Thank you very much, that was exactly the view, I was looking for!

… Meanwhile, I discovered this extreeeemly interesting showcase:

Live filtering of dataviewjs table

I actually liked this idea so much, that I decided to use the same principle to create pagination and also add new notes to the table. And added the ability to filter by list properties too (only by one at once). As a result I created absolutely monstous script, that is too big to put here, so you can find it on my Github. Here is the demo: [image]

which describes a solution for my actual usecase, … the actual reason, why I wanted to generate that List-view as a first step.

I hope strongly, that this kind of feature becomes a core feature of Obsidian!!!