Spaces or links allowed in Dataview fields?

[everruler12]

I'm wondering if I could mimic Roam attributes, which use the same double colon syntax for key/value pairs. In Roam, the attribute is a clickable link that leads to a note of that title. For example:
Homework for Life:: I learned Dataview today.
I could click the attribute as if it were [[Homework for Life]] and be taken to that page.

If I had one of these in Obsidian:
Homework for Life:: I learned Dataview today. or
[[Homework for Life]]:: I learned Dataview today.
How would I reference this field in a dataview code block?

Neither of these work:

TABLE WITHOUT ID file.link AS Date, [[Homework for Life]] AS "Entry"

or

TABLE  WITHOUT ID file.link AS Date, "Homework for Life" AS "Entry"

as they are interpreted literally and fill the entire column with that as the value instead of the value of the field.

According to the documentation, there is a reference type:
simple-field (refer to fields with spaces/punctuation in them like "Simple Field!")

What is the proper syntax for referencing a simple field?

[blacksmithgu]

In dataview, you can refer to multiword fields in two ways:

• The programmatic syntax: row["Homework For Life"]. row is a magic keyword which references everything in the current datarow/page in the query.
• The normalized syntax: Dataview normalizes all keys, so you can refer to them using lower-case and with dashes in place of spaces. "Homework for Life" becomes homework-for-life. You can use this in your query.

[everruler12]

It looks like [[Homework for Life]]:: I learned Dataview today. doesn't work. If there are double brackets before a double colon, it gets ignored as a field (while a tag gets counted, but without the hashtag symbol). My usecase is being able to change field names easily in the entire vault, like in Roam.

[AB1908]

One way to do this: use a regex search and replace in a separate program. VS Code, sed, awk, whatever suits your fancy. Another way would be to write a script that reads the notes containing this key and write back the changed key.

[AB1908]

Also, always remember to keep a backup of your vault!