Category:DatastoreRedesign

Journal

• Main view shows actions: Wrote a document, Draw a sunrise, Took photographs about my birthday, ...

• An action is composed by metadata properties and can contain several objects.

• An object is composed by: a file, a mime type that refers to that file, metadata.

• May be needed an object view?

• Actions are grouped as versions of one more generic action. An action can be root or can be based on an existing one.

• Objects are also related to other versions of one more generic object. Do we want to expose this in the Journal?

• Actions and objects are immutable, but have some properties that refer to them and those can be changed: tags, description, starred, ...?

• Full text search operates over metadata (both from actions and objects) and over the content of some objects (those we can extract text from).

• Removable devices such as USB sticks and SD cards would stop appearing inside the journal and instead would use a simpler view that would allow to transfer files into and from the journal.

Eben, can you add some mockups?

Activities

• Most activities will save just one object inside one action, so these need to be able to use the existing super-simple API.

• Other activities will want to use a more complex API for:
  • storing several objects inside the same action,
  • editing the metadata of the action and objects,
  • influence the display of the action in the journal?
  • ...

Datastore

Let's first agree on the Journal and Activities sections before working on this one.