Export in Json

esanpons

It would be a good way to be able to export and transfer the information if it could be exported as Json.

In addition, the attached files could be added as Base64 so they could be transferred to other platforms without having to complicate the user and have to do it manually one by one.

timo

What are the benefits of export in JSON? What would you do with that file?

esanpons

Have a readable bak, be able to read and modify the entries massively, import it to other systems. Interact between two applications since the Json system is somewhat more standardized.

will v

I'd like to see this feature too. It would help future-proof Diarium. Let's be honest—if something happened to you we users would all be up a creek.

Day One supports JSON export and because of that fact several other journal apps can import it (including Diarium). I don't think I could have made the move without the ease of use that comes with JSON export/import.

timo

will v You can already create a database backup in the app settings. It's a plain SQLite database so you have full access to your data. Other apps should have no problem reading and importing data from such an SQLite database and I from one other journaling app that does exactly that. It's the choice of other journaling apps to support migration from Diarium data or not, nothing prevents them today from supporting it

HectorM

First of all, this is an incredible journal app! The only thing I think is missing is this feature, so I also vote for this to happen. I know we have the sqlite database, but I found myself trying to convert that into json manually and at some point I feel that it does not make sense that I have to do all the process each time I want a json file, I mean, I had to installed other software to read the database, and even after exporting it to json, the text have some HTML characters so now I need another process to clean that, and I don't even have the tags related to each entry in that json.

Manipulating a sql database is not as easy as a json file which is a standard. As esanpons said, is readable, easy to modify, easy to import/export, like you can do a lot of stuff with that.

Is this something that could happen anytime in the future?

timo

What are you planning to do with a JSON file? What would be use-cases for it?

HectorM

Well I’m seeing options for a journal/diary app, and this one is perfect but if I’m going to choose one so that in the future when I need to migrate to another or updating my current json file with the entries written in the app I have chosen, I would want that app to have the option to export to json and don’t have to be playing with a sql database or manually transforming a docx into a json.

A lot of apps have this option but those are not as good as this one.

That’s why I like the idea of having this feature. In summary what I wrote is the long version of just saying “That would make this app future proof”.

timo

So if I understand you correctly, you would write a script or program to read and manipulate the JSON file. For the majority of users (who don't know how to code), adding a JSON export would therefore likely show no benefit. Will still think about it, shouldn't be too difficult to implement

HectorM

timo
No, I mean, having a export to JSON option would be actually better for users that don’t know how to code. If I wouldn’t know and you give me a sqllite db file that when I try to open to plain text doesn’t show anything but weird characters and you tell me that’s me having full access to my data, well I wouldn’t know what to do. I’ll probably just export a docx and start from scratch to another app knowing I can’t use a docx to import to another app. But with a json at least it can be open as plain text and others apps like Day One accepts importing with json file.

As will v said:

“I don't think I could have made the move without the ease of use that comes with JSON export/import.”

So it will be easier for the regular user to export/import a json than a sqldb just because other apps have that option too and it’s readable as plain text.

I know you said you will think about it, but wanted to clarify this part.

Thank you again for making this app, it’s awesome, and for taking the time to respond messages here.

timo

HectorM But with a json at least it can be open as plain text

You can open as plain text, but the file will also contain all the JSON syntax with braces, commas etc - the .docx export is much better suited to just display plain text.

HectorM and others apps like Day One accepts importing with json file.

HectorM because other apps have that option too and it’s readable as plain text.

No, this is not correct. Just because Day One supports importing their JSON file, this doesn't mean Day One can import any Json file. Json files needs to be structured a certain way to be consumed by these importers. If an app wants to import the JSON of another file, they need to manually write migration logic. I did that manually for Day One and Day One would have to do that manually for Diarium. And if they wanted, they could already use the SQLite database that I offer today. So just offering a JSON file doesn't make the data importable from other journal apps. That's what I mean with that a JSON backup option wouldn't have any real benefit for the majority of users.
Yeah, you could export a JSON file and look at it in a text editor app, but you couldn't import it into other apps.

HectorM

timo yeah I know that is needed a specific structure for that json file. But if they already to that, it will be easier to map a json file and hence easier to migrate from Diarium to other apps but probably you don’t want that.

You’re right that they could use what you offer right now, and maybe I’m just asking for an edge case.

I think right now for me the best is to just move to Day One, but thank you anyway.

timo

I just don't think Day One would consider adding such a migration for Diarium data or if they would, that the fact that I don't provide JSON export is holding them back due to the reason of reading an SQLite database is considered too difficult for them (they most likely use a SQLite database internally anyways and have could read a Diarium SQLite database right away, without having to add more code than they would if they read a JSON file).

I am certainly not trying to put in measures that prevents you having ownership of your data. But I have the credo that before I add a feature that is being asked form the community, I want to completely understand what the user really wants. And in this case, it seems that the feature request should rather be titled "Offer a way to migrate to Day One" and not "Provide JSON export".

I also don't understand your last sentence. If you prefer Day One, why have you started this thread in the first place? Did you want to start a journal with Diarium but move to Day One later? As I explained above, a "JSON export" feature wouldn't have helped you to move you data.

HectorM

Don’t take it personal, I said Day One because that is another of my options, in fact I do prefer Darium over Day One, but having that feature is a deal breaker for me, specially if I’m going to pay for an app.
I come from Journey app and from others before that and I’ve always used that feature (yeah I had to modify/adapt the json to keep importing it into other apps). But that’s how I keep moving each time I found a better app. Maybe my reason or the reasons of the users above are not enough to make it happen so I think my best option is to simply go for my second option which right now is Day One.

timo

As it's an easy feature addition with no drawbacks that I can see, I will add this to the next app update.
However, Diarium can not re-import the exported JSON file.

esanpons

I have seen that you have added it and it is very cool, I thank you

mars-online

I think it is great for visualisation.

I hope to find time for an export script that allows me to filter by tag (a specific vacation for example) during a specific time frame and export the entrie to HTML. Then I could visuallize the entries on an OSM map besides the list form of your HTML export. My old travel journal app had such an export format but was sadky discontinued...