Features

Features marked in green exist in some form, those in yellow are underway and those in black have yet to be started.

• Note tool agnostic

• Public kasten of notes.

• Private kasten

• Shared kasten

• Each kasten is a CouchDB database.

• Every user has a kasten on creation of their account. It is the same name as their user name.

  • Every kasten a user creates begins with that user name and separated by a '/'

  • A user may create a kasten name with multiple '/'s to create an apparent hierarchy but each kasten name is atomic.

• Notes can refer to and include other notes (ie ReTweets, Quoted Tweets or similar).

• Notes can include attachments.

  • Images

  • PDF

  • Word

  • Video

  • Mime Type

• Notes belong to a primary kasten, but may be copied to other kasten. Copies are shallow.

  • This means that a note may be ordered, coloured or arranged differently in different kasten.

• A Note can be moved from its primary kasten to another kasten.

• Tags are both explicit #tags and implicit from content.

• URLs are extracted from both notes and referred notes, or attachments

• PDF and other document types have metadata extracted and text excerpts (Abstracts, References)

• DOIs are extracted.

• Relevant icons on notes for Authors, ORCiD, Twitter, Evernote, etc.

• Every note has a permanent shareable URL.

• Each note, referred note and attachment is added to the full text index on each kasten.

• Tags are both explicit #tags and implicit from content.

• Every note has a permanent shareable URL (So long as it is a public note)

• Notes can be linked.

  • Linked notes can be shown as connections or graphed.

  • All notes in a kasten can be graphed

• Notes can be sharded.

• Notes can be ordered and the order saved, a kasten can have multiple orders.

• Search Results are a kasten and can be copied to a new or existing kasten.

• kasten can be filtered, ie searched.

• kasten can be tagged.

• kasten can have meta-notes

• API and kasten will be available for both separate installations and as part of federated and distributed systems.

• API accepts mutiple formats regulated with queues.

• Filters parse formats into zettel POSTs

• Initial formats