Search is a v0.6.0 goal. It is a prerequisite to #17, so both this issue and #17 will be moved to the v0.6.0 milestone.

Parent: #3

Parent #3

Note creation, that kind of thing are best effort, return as soon as possible kind of thing.
Note update can be put in a list of changes to be made when the server has time, so the db update is added to the queue, and the note is echoed back to the user to ack the fact that the note was received. This can be tied in with processing for incrementing versions. The user making the edits gets an immediate response, but other users will see the new data as soon as possible.
Aggregate analysis data can be run on a tertiary queue that runs whenever the 2nd job queue (after live server requests) is empty

Each version is a milestone, and I can add issues to each version as a milestone. Once the milestone is 100% complete, I can release the version.

Parent: #4

get note versions (atoken, list of <note id>)

Returns a list of the maximum version of the given note ids.

Except if the user has been logged in for more than 24 hours.
This depends on #37

Parent #4

get note by version (atoken, <note id>, version)

Returns the note at the specified version. version is an incrementing integer, and invalid version defaults to latest version.

It needs to be redone to match up better to what the server side is doing.

Parent: #3

Parent: #3

Parent: #4

get notes (atoken, list of <note id>)

Returns the note title, metadata and contents as a json object.

Parent: #4

get searchable notes (atoken, list of <note id>, options)

Options:

• delimiter: delimiter string
• as list: returns a list instead of delimited string
• tokens: returns as a dict of tokens, with their count
  Returns a space delimited version of the note that is designed to be indexed or searched on the client. This can be converted to a list of tokens by spliting on the spaces.

Parent: #4

update notes (atoken, list of <note info>)

Push the provided info into the given note.
Returns { 'results' : number of successful updates }

Parent #4

get note offset (atoken, note id, note set)

Find the position of a note in the given set. A set is a combinations of a notebook (1 or 0) and arbitrarily many tags, and ordered by a given attribute (default is last updated). A note set contains:

• notebook: notebook guid
• tags: list of tag ids
• sort: sort order (title, meta, content, created, updated)
• sort ascending: 1 or -1
  Returns the integer offset (0 for first note)

This will be removed and broken down into many sub-components that can be handled as separate issues.

Parent: #4

trash notes (atoken, list of <note id>)

Send the given notes to the trash
Returns { 'results' : number of successful notes trashed }

Including authenticating with the API

Parent: #4

create notes (authentication token, list of <note info>)

Create new notes based on the given information. If nothing is provided, the default note values are instantiated.

• title
• meta
• content
• public share
• private share
  Returns the list of <new note id>s

This is a prerequisite to issue #16 (Get notes sharing info).
This is a v0.3.0 task, as identified in Goals.md, so I'm going to set this and #16 to milestone v0.3.0

It starts out with just a username and password field, with a login button:

• If the username/password sent in match a user, switch to a profile view.
• If it doesn't match, offer two options: login again, or create user.
  • If they click create user, load a new screen with the username and password field filled in, and an extra confirm password field.
  • otherwise, repeat login step.

Parent #4

email notes (atoken, email info, list of <note id>)

Send the given notes to the given email address
Returns { 'results' : number of successful notes emailed }

No editing yet, just show user, last login (via token information). Authenticate this with the token.
This is a prerequisite for finishing #2. This is also part of the web interface that does basic note creation.

First test is on the login page.

Part of the v0.2.0 spec. This is part of the conversion to Github issues from a single doc. See #1

Parent: #4

get notes sharing info (atoken, list of <note id>)

Return a list of pairs of [private, public] share link strings. If they are empty, the note is note shared that way.

Parent: #4

copy note (atoken, note id, target Notebook)

Copy the existing note to the target notebook
Returns the new note id

This is a prerequisite for #11, #12 . The current system is just getting all notes for a user. This depends on having notes and tags ( #5 and #6 ) so this is a v0.4.0 task. #11 and #12 need to also be updated to the v0.4.0 milestone.

Part of the v0.2.0 spec. This is part of the conversion to Github issues from a single doc. See #1

This depends on #32, #33

This will require progressive database updating

Parent #3

Part of the v0.2.0 spec. This is part of the conversion to Github issues from a single doc. See #1

Depends on #32

Parent: #4

get note ids (atoken, set)

Find the notes that are in the set. A set is a combinations of a notebook (1 or 0) and arbitrarily many tags, and ordered by a given attribute (default is last updated). A note set contains:

• notebook: notebook guid
• tags: list of tag ids
• sort: sort order (title, meta, content, created, updated)
• sort ascending: 1 or -1
  Returns a list of the ids of notes in the set.

Parent: #2

Create the html for the initial login page (username field, password field, login button, create user button)

Use this as a basis for #14 and #15