Migrate data to the hoarder bookmarking self-hosted application
Marty Oehme
1017b876e9
There are clear issues remaining with this approach. The wallabag-given 'start' and 'end' fields do _not_ just point to the n-th paragraph all the time (like I thought) but actually represent a beautifulsoup4 like tree descent. So: `p_start_match = re.match(r"/p\[(\d+)\]", annot["ranges"][0]["start"])` will fail on any annotation not just at the n-th paragraph. Instead we should see how we can move this tree into the beautifulsoup4 parser and make use of wallabag already having done the work for us? |
||
|---|---|---|
| shaarli2hoarder | ||
| wallabag2hoarder | ||
| .gitignore | ||
| .python-version | ||
| main.py | ||
| pyproject.toml | ||
| README.md | ||
| uv.lock | ||
Hoarder migration scripts
Simple scripts which try to ease the migration to a self-hosted hoarder instance.
Wallabag
Use one of the flavours of transferring your wallabag entries into hoarder.
Run it like: ./wallabag2hoarder/convert.py <input-file>
Where input file is a wallabag json export of all your saved entries. There are options to change the style of output (netscape HTML, native JSON) and the file to output to. By default converts to hoard JSON and prints to stdout.