Closed turbomam closed 2 years ago
Yes, that was brought up as a feature some could probably use. Is that a need of yours? And is it export of raw data as your link mentions that is needed? One thing to say is that we would want to do the JSON-LD export, which would include namespace of ontologies involved in selection lists.
Yes, NMDC is pretty JSON oriented. Bill, I and others obviously already have to do some table to JSON conversion, but coupling it to the DataHarmonizer template would be great.
I don't see why JSON-LD would be a problem.
I think the area where JSON would be useful is in API communication (persistence, validation) @turbomam moving from Handsontable data structure to JSON for API calls is not too bad. (This is exactly what I did with JGI's sample metadata submission.).
The use case I'd be looking at: Given CRUD API endpoints exists - can the format of those request messages be configured in a some generalized way - perhaps also driven by the data.tsv, either extending data.js (currently HOT config specific) or adding another API specific data structure.
Not sure there is a use case to just export JSON on the client side as files.
A request from NML has come in for JSON export format so this is more of a priority for us. We will implement this on the LinkML version of DH.
On pull request https://github.com/cidgoh/DataHarmonizer/pull/344 there is now a save-as-json option.
This doesn't have load-as-json yet though.
Now save and load are in master!
Has there been any discussion about saving to or exporting to formats other than rectangular tables?
Maybe this is a far fetched stretch for a project based on Handsontable. I did find this: https://forum.handsontable.com/t/export-to-json/3925