Features

Configuration Control of Note Property Structures

2y agoPending

A recent change in NotePlan permits use of AI to update Property structures.

I think that the following are all true:

1. The need to update property structures for notes of the same “kind” will inevitably arise. For example, after creating 30 notes with Property Set “Books Version 1” a need to add a new property will be identified with book 31. Then another new requirement will be identified with book 43, and still another with book 75.

2. A proliferation of structures for the same basic “kinds” of information will create confusion and interfere with the efficiency of Eduard’s planned table views.

3. Updating dozens of notes, one at a time, with new structure will be painful.

Recommendation:

a. NotePlan employ “named property sets” - each with a version number. Examples: “books”, “projects”, “clients”, “delivery orders”, “bug reports”, “feature requests”, “bird sightings”, etc.

b. When a structural change to a “named property set” is made, all notes employing that property set should be updated - perhaps by using AI to do so. The version number should also be updated.

and 2 others

6 comments

  1. Leo Melo2y ago

    The way I achieve this is by having "collection" notes and setting those properties on that note, I then reference that note on any related note and the back links will allow me to easily reference what I want.

    I used to have the referenced collection note in a frontmatter property but with the new property UI it broke links (and also the way I used to do tags) so that's less helpful right now but it still works if you add it outside the property header just fine.

  2. Why not have property sets similar to Tana supertags or Capacities objects? Define what a note is and the predefined properties will be added.

    1. Tor-Einar Rogn Exactly. But, that is now possible with templates. What is missing is updating a set of notes that were given the same set of properties with an updated set of properties. For example, if you have 50 books with a set of properties and want to add another, say "rating" then all 50 should be updated vs having to update 50 notes one at a time. That is, of course, a Tana supertag feature.

    2. Brian Barry It would certainly be practical to update several similar notes at the same time. Right now I don't really use properties for this very reason. I'm eagerly following the development of properties in NP however!

  3. Hi Brian, we were thinking that AI could update a handful of notes all at once. Right now there is anyways no property inheritance available, and I think that would complicate things too much, if we would introduce this.

    1. Eduard Metzger I am not suggesting a property inheritance scheme, but there must be some way to identify the "handful" - and relying on folders being the answer seems like an unnecessary limitation in flexibility. Rather, choose the highest level folder and prompt: "Change those with property "book" by ..."