Please officially document the import JSON document format.
Closed this issue · 4 comments
Hi. Please write canonical documentation for the JSON document import format. I've spent the last couple of days writing a Netscape bookmarks-to-JSON converter, without much success. Some of the fields are self-explanatory, but others (tags: {}) don't seem to make sense (shouldn't tags be a list and not an object?)
At the very least it'll make things significantly easier for those of us who are trying to get away from certain services that only export in HTML format.
I could need some more information about that too. Wrote a Python script to convert my Del.icio.us bookmarks but not a single generated JSON file was accepted. The closest I could get was this by using the export file itself but added about 15 own marks:
@Kovah I'm doing this now.
More importantly, I will document Unmark's Export JSON format as it should be thought of (at this point at least) as more of a "backup" of someone's Unmark install rather than an export/import schema.
However, I'll write up a doc so we all understand the JSON schema.
To import from Delicious, though, you could do what I did over on #158 to import Readability -- which is -- add new import functionality. I'd love to see Unmark support more services.