since Joplin now has a shiny new API that seems pretty cool, I’m tempted to integrate it into my workflows. (That’s something I’ve always wanted to do, but didn’t really have a good editor to do it in. )
I sync data from various systems to my blog (some were automated, most manual). That kinda sorta works when I just create a new note, but to automate updates, I’d need to be able to find and identify a note to update - ideally by storing an ID used by the external system. (E. g. when I sync something from Airtable or Goodreads, I might want to store an Airtable or Goodreads ID to find the note by.)
So getting to the point, my question: would it perhaps be viable to add a new field, something along the lines of ‘additional data’, to the notes’ metadata? From Joplin’s point of view it could be a plain string that it doesn’t process in any way, just lets me get, set or search it via the API.
I’ve already noted the benefits this would have for me; I could, for instance, store a json that says ‘this note is from system A where it has the ID XYZ’. I could then find and update this note whenever necessary.
When it comes to drawbacks, there are the usual obvious ones: it would need to be implemented, and I’m not sure how many users would actually benefit from it/want to use this feature.
Other than that, noting comes to mind; seems to me this should be pretty orthogonal to all the other existing features and should not cause conflicts or require much upkeep. (But I might be wrong here, I don’t know the internals that well.)