Why are json keys rearranged after hitting "create" button?

[1of13]

After spending a lot of time creating a JSON schema by hand, things get rearranged as soon as you hit the "create" button on the demo site. This impairs the extraction process as the information in the document is no longer found in the order specified in the original schema. Additionally, sometimes the process fails to generate a table or JSON output—it just spins, and nothing shows up when it completes.

The same schema rearrangement occurs when using the API. Again, extraction is not optimal, as information is not retrieved as indicated in the schema, LLM instructions, and examples. Please include some examples of extraction using local files (perhaps batches) and directories in the documentation.

Thank you so much. I appreciate your hard work.

[eyurtsev]

Got it -- thanks for the feedback. We're using a JSONB field in the database -- I was imagining optimizing for a situation where one might want to run queries against the schemas themselves at some point. It sounds like we need another JSON field so we can store the output as is.