Self Contained Notes Repository Manager: Difference between revisions

From Public wiki of Kevin P. Inscoe
Jump to navigation Jump to search
No edit summary
Line 10: Line 10:


==Design goals==
==Design goals==
*Works completely off-line (no cloud!) without global or local networks at least in terms of creating or editing notes.
*Intended for a single private individual with sharing of notes possible via export. Non collaborative notes and articles of a personal or private nature.
*Reliability, private, cross platform and simple to use are the priorities.
*Self-contained (not a web service, centrally hosted or cloud based).
*Access is encrypted, secure and authenticated.
*Encrypted end to end even while editing.
*Desktop oriented and not client server.
*Notes and attachments stored in a single encrypted vault in a single file.
*Organization of notes by drawer and then flder with tags and other semantics.
*Support for any editor and text formats. Files stored natively text or blobs.
*Entire vault encrypted (similar to archives or PKZIP).
*Documents in vault can be modified by the editor of your choice while ensuring their safe and encrypted return to the vault.
*Recoverable journal of revisions to documents.
*Authorized replication of documents (similar to Lotus Notes NSF) to other vaults (hosted else where or on local disk).
*Notes are searchable, indexed (if plain text) and tagged.
*Revision control of notes in the repo are possible (future feature).
*Don't re-invent what doesn't need inventing.
*Cross platform: Mac, Linux and Windows.
*Document management - Revisions, dates and changes much like a regular wiki.
*Dead man feature (upon owners death access would be granted to provided survivor(s) ...) [TBA].

Revision as of 19:17, 17 April 2020

This page is a work in progress.

What is it

Self Contained Notes Repository Manager of SCNRM is a free and open source multi-platform secure and encrypted notes repository GUI written in Python/TkInter usable under Linux, Windows and Mac and possibly others where Python and TkInter are implemented.

Notes storage

Note collections are stored in single file (or nosql database) containers referred to as a vault with a further organization of drawers.

Design goals

  • Works completely off-line (no cloud!) without global or local networks at least in terms of creating or editing notes.
  • Intended for a single private individual with sharing of notes possible via export. Non collaborative notes and articles of a personal or private nature.
  • Reliability, private, cross platform and simple to use are the priorities.
  • Self-contained (not a web service, centrally hosted or cloud based).
  • Access is encrypted, secure and authenticated.
  • Encrypted end to end even while editing.
  • Desktop oriented and not client server.
  • Notes and attachments stored in a single encrypted vault in a single file.
  • Organization of notes by drawer and then flder with tags and other semantics.
  • Support for any editor and text formats. Files stored natively text or blobs.
  • Entire vault encrypted (similar to archives or PKZIP).
  • Documents in vault can be modified by the editor of your choice while ensuring their safe and encrypted return to the vault.
  • Recoverable journal of revisions to documents.
  • Authorized replication of documents (similar to Lotus Notes NSF) to other vaults (hosted else where or on local disk).
  • Notes are searchable, indexed (if plain text) and tagged.
  • Revision control of notes in the repo are possible (future feature).
  • Don't re-invent what doesn't need inventing.
  • Cross platform: Mac, Linux and Windows.
  • Document management - Revisions, dates and changes much like a regular wiki.
  • Dead man feature (upon owners death access would be granted to provided survivor(s) ...) [TBA].
Retrieved from "https://kevininscoe.com/wiki/index.php?title=Self_Contained_Notes_Repository_Manager&oldid=800"