id,node_id,number,state,locked,title,user,user_label,body,created_at,updated_at,closed_at,merged_at,merge_commit_sha,assignee,assignee_label,milestone,milestone_label,draft,head,base,author_association,repo,repo_label,url,merged_by,merged_by_label,auto_merge
771790589,PR_kwDOEhK-wc4uAJb9,15,open,0,include note tags in the export,436138,d-rep,"When parsing the Evernote `<note>` elements, the script will now also parse any nested `<tag>` elements, writing them out into a separate sqlite table.

Here is an example of how to query the data after the script has run:
```
select notes.*,
	(select group_concat(tag) from notes_tags where notes_tags.note_id=notes.id) as tags
from notes;
```

My .enex source file is 3+ years old so I am assuming the structure hasn't changed.  Interestingly, my _notebook names_ show up in the _tags_ list where the tag name is prefixed with `notebook_`, so this could maybe help work around the first limitation mentioned in the [evernote-to-sqlite blog post](https://simonwillison.net/2020/Oct/16/building-evernote-sqlite-exporter/).
",2021-11-02T20:04:31Z,2021-11-02T20:04:31Z,,,ee36aba995b0a5385bdf9a451851dcfc316ff7f6,,,,,0,8cc3aa49c6e61496b04015c14048c5dac58d6b42,fff89772b4404995400e33fe1d269050717ff4cf,FIRST_TIME_CONTRIBUTOR,303218369,evernote-to-sqlite,https://github.com/dogsheep/evernote-to-sqlite/pull/15,,,