Custom frontmatter properties (status, priority, project, due-date, etc.) are currently discarded after ingest. They should be stored as individual metadata fields on the first chunk of each note so they can be used as filters in any query command.
Read all frontmatter properties from obsidian properties path=... format=json. For each key whose value is a string, int, float, or bool, write it as a ChromaDB attribute prefixed prop_ (e.g. prop_status, prop_priority). Expose a --where flag on all query commands accepting key=value pairs that are translated to chroma.EqString / EqInt filters. Add a secondbrain properties list subcommand that shows all indexed property keys and their value counts.
Custom frontmatter properties (status, priority, project, due-date, etc.) are currently discarded after ingest. They should be stored as individual metadata fields on the first chunk of each note so they can be used as filters in any query command.
Read all frontmatter properties from
obsidian properties path=... format=json. For each key whose value is a string, int, float, or bool, write it as a ChromaDB attribute prefixedprop_(e.g.prop_status,prop_priority). Expose a--whereflag on all query commands acceptingkey=valuepairs that are translated tochroma.EqString/EqIntfilters. Add asecondbrain properties listsubcommand that shows all indexed property keys and their value counts.