2.1 KiB
| title | date | description | url | type | mp-syndicate-to | tags | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Joplin Hypothesis v0.1.0 | 2022-12-11T11:20:00Z | A publically available version of the hypothes.is plugin | /2022/12/11/joplin-hypothesis-0-1-0 | post |
|
|
I've just released v0.1.0 of my Joplin Hypothesis plugin.
The exciting news is that it now shows up in the Joplin plugin installer/marketplace - just go to tools > Plugins and enter 'hypothesis' in the search to find and install it.
This version adds checks to see whether the user has Joplin note sync enabled and forces the plugin to wait for any ongoing sync to resolve before running the Hypothesis sync process. That way the chances that duplicates/conflicts are generated by both Joplin and Hypothesis Syncing at the same time are reduced.
One matter I'm still not sure about is the best way to structure the notes. At the moment one new note is created per annotation. However, this might seem a bit overwhelming and some people might prefer a single note per website/document being annotated that contains multiple notes. I have considered this solution, however I think it is less useful from an information management and retrieval perspective. It would mean that all the tags that have been applied to different annotations would be co-mingled and that the user would then have to search through larger documents to find the quote or annotation they are interested in. This in itself could become problematic if you have many annotations for a given document.
My current suggested workflow is to use tags to find notes you're interested in on a given topic, or, search for the title or URL of a document that you have annotated to find all annotations for that document. I'd certainly be interested in hearing from people who have tried my plugin as to which workflow they would prefer and why or whether there might be other ways of working that I've not considered.