Hello,
I have a pretty extensive tool-database for all my tools and I could generate a file like CSV to import all my tools at once.
There is an import option but it’s in a file format I can’t edit/create, or is there some documentation?
So I guess my question is: Is there a way to import my tools into Kiri:moto?
Thanks for you effort,
Da BIG One
Kiri:Moto exports/imports JSON data encoded in base64.
If you export the tool library and run the contents of the file through a base64 decoder you will get an editable list of tools. You could them run that through an encoder and import it back into K:M.
Oh nice, I’ll try that, thanks.
@stewart Do you think it makes sense to allow JSON tool list imports by drag and drop?
if you drag/drop onto the platform it acts the same as file → import so that already works
I wasn’t clear with what I was saying. I was wondering about allowing imports of un-encoded JSON. currently, it does this:
it’s a common code path, so if we want to support non-base64 .km then we could test that the string is enclosed in {} and skip base64-decode. probably low risk. base64 is used as “armor” encoding and for other historical reasons. but I’m not opposed to allowing clear imports. it will obviously not work for .kmz which is a zip format and includes binaries and other things we won’t stick into json.
Should also enable unencoded export