https://github.com/bfulop/quivertolevel

Export Quiver notes to LevelDB
https://github.com/bfulop/quivertolevel

Last synced: about 16 hours ago
JSON representation

Export Quiver notes to LevelDB

• Host: GitHub
• URL: https://github.com/bfulop/quivertolevel
• Owner: bfulop
• License: mit
• Created: 2017-09-01T07:50:02.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2023-01-04T15:40:10.000Z (about 2 years ago)
• Last Synced: 2024-11-21T14:41:37.471Z (2 months ago)
• Language: JavaScript
• Homepage:
• Size: 504 KB
• Stars: 0
• Watchers: 2
• Forks: 1
• Open Issues: 13
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Quiver to LevelDB

A library to export your Quiver notes to a LevelDB database

Needs a `config.json` file to get the path to your Quiver library.

```json

{

  "quiverpath": "/Users/[path to]/Quiver.qvlibrary"

}

```

The format of the LevelDB records is the following:

```

key: 'anote:' + noteid, value: notedata -> to get a note contents by id

key: 'notes:' + timestamp + ":" + noteid, value: {title: 'note title'} -> list all the notes

key: 'anotebook' + notebookid + ":" + timestamp + ":" + noteid, value: {title: 'note title'}, -> to list the notes in a notebook

key: 'notebooks:' + timestamp of the latest note in the notebook + ":" + notebookid, value: {name: 'notebook name', uuid: 'notebookid'} -> to list the notebooks (by date)

```

The note contents will be (see `processNote.js`):

```

{

  nbook: [meta.json] // of the folder

  note: {

    meta: [meta.json],

    content: [content.json]

  }

}

```

### More config options

The `config.json` file has more options to process the notes and notebooks when importing.

```json

  "titlereplacements": [

    {

      "from": "foo",

      "to": "bar"

    },

    {

      "from": "baz",

      "to": "pants"

    }

  ]

```

These will replace texts in the notebooks titles.

### To run

```shell

$ node src/run

```