I've found I frequently struggle with having a metadata record fail on submission to FOXDEN because of typos or transcription errors. This is especially prone to happen in cases where I've created all or part of the .json by hand in a text editor.
It would help a lot to have a tool independent of actual record submission that validates a record .json against a specified schema. I figured out my most recent transcription errors by manually trying to upload the .json in question via the FOXDEN web interface, which returned sufficient error messages for me to figure out which key/value pair was the problem.
Because we are trying a workflow at 3A (implemented by @keara-soloway ) where SPEC (or a human) creates a partial .json with BTR-level information once per BTR, and then a user can pre-populate a sample-level .json that gets combined with the BTR-level .json by SPEC, it would help to be able to validate these partial records independently.
I've found I frequently struggle with having a metadata record fail on submission to FOXDEN because of typos or transcription errors. This is especially prone to happen in cases where I've created all or part of the .json by hand in a text editor.
It would help a lot to have a tool independent of actual record submission that validates a record .json against a specified schema. I figured out my most recent transcription errors by manually trying to upload the .json in question via the FOXDEN web interface, which returned sufficient error messages for me to figure out which key/value pair was the problem.
Because we are trying a workflow at 3A (implemented by @keara-soloway ) where SPEC (or a human) creates a partial .json with BTR-level information once per BTR, and then a user can pre-populate a sample-level .json that gets combined with the BTR-level .json by SPEC, it would help to be able to validate these partial records independently.