~bsprague/everdo-export

249461af22f33891ab6c401c62689066bc72a3af — Brandon Sprague 8 months ago ffe77dd
Clean up the README
1 files changed, 13 insertions(+), 5 deletions(-)

M README.md
M README.md => README.md +13 -5
@@ 1,8 1,8 @@
# Everdo Export

This is a simple, in-progress tool for taking a JSON export from Everdo and parsing it, with the eventual goal of transforming it into something vaguely [Logseq](https://logseq.com/) compatible.
This is a simple tool for taking a JSON export from Everdo, parsing it, and transforming it into something vaguely [Logseq](https://logseq.com/) compatible.

Since this tool is heavily based on my own personal Everdo export, features that I haven't used might be incorrectly represented.
Important caveat/warning: Since this tool is heavily based on my own personal Everdo export, features that I haven't used might be incorrectly represented.

## Everdo -> Logseq Translation



@@ 14,15 14,17 @@ All projects from Everdo become pages in Logseq. Each item from that project bec

```
type:: project
description:: <description from Everdo>
project-type:: {sequential,parallel}
project-status:: {active,someday,scheduled,waiting,deleted,archived}
tags:: <comma delimited tags from project, linked as pages>
```

and optionally have:

```
description:: <description from Everdo>
focus:: true // If the item was focused
waiting-on:: <comes from the `contact_id` in Everdo>
tags:: <comma delimited tags from project, linked as pages>
area:: <the area, linked as a page>
```



@@ 42,9 44,15 @@ The page it goes into corresponds to the List it was on in Everdo. Items may hav

```
waiting-on:: <comes from the `contact_id` in Everdo>
focus:: true // If the item was focused>
focus:: true // If the item was focused
inbox:: false // The designator that moves things from Inbox -> Next
area:: <the area, if any>
```

Additionally, all action blocks start with `collapsed:: true`, just to remove some clutter. There's also the `SCHEDULED: ` and `DEADLINE: ` commands, which are **not** 1:1 mappings to what Everdo has, but the script will fail if it's _too_ lossy.

### Notebooks

Notebooks look like projects for the most part, but they're also just mostly normal Logseq pages. They don't have `project-type` or `project-status` or `waiting-on` or `type`.

Notes are like action items, but without a TODO or other task label, and without other not-relevant properties like `waiting-on`, `inbox`, etc.