Skip to content

(feat) More storage structure options #243

@Zepmann

Description

@Zepmann

Does it fit the projects scope?

  • This is relevant

Why?

What I like about Note Mark is that the content of notes is saved as plain text on disk. This opens the door for interoperability.

What I like less is the chosen directory structure. Currently the structure from the data directory root is <first two letters of note UUID>/<note UUID>/note.md. Without Note Mark's database, it is impossible to know which note belongs to whom.

Solution?

What I would like to see is more configuration options for dynamic paths. For example:

<configurable unique user ID>/<notebook slug>/<note slug>/note.md

Notice that all these values are unique, preventing duplicate values from occurring. This structure is also compatible with the existing ability to attach assets, since the contents of the note directory is not changed, just its location.

The configurable unique user ID should be something that the user configures. Examples include the unique user ID Note Mark generates, a claim from OIDC (such as sub or preferred_username), etc.

When configured to use the same type of usernames, this will allow access to a user's own "raw" notes through other software, such as Nextcloud. That would be a great first step in the ability to integrate Note Mark in other software. 😃

Alternatives?

No response

Extra Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    Status

    No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions