|
|
|
|
|
|
by mlisowsk
599 days ago
|
|
|
If I understand this correctly, you are proposing to deconstruct (a priori unstructured) documents into structured data, no? I think you need to have a demo use case in your app so people can better understand what this is about. I tried to make an invoice document type. So far I got simple header data and line items and I created a method to add up line items to a total. It would be nice if methods could be triggered to run automatically. I can place buttons to run methods, but can I run a method at document update or field update? Also I to speed up creation of methods you should have simple aggregation function like summing all items of a list (given a field name to sum over). |
|
|
Well I'm proposing to have a workspace with everything structured indeed, where all the documents would be "programmable" and "queryable" and where unstructured data would simply be attachments of structured data.
At some point when uploading a new "file", I think the framework should systematically call a multimodal LLM to extract structured data from it, so that it can be queried from anywhere in the workspace. My main concern on this is that the LLM should stay local...
Yes you are right this is lacking a good and simple demo usecase, I'm working on it.
Yes, as you've seen, some field types have a limited set of "builtin methods" that I've added just for the demo, and List is clearly the one that should have much more ! (map, reduce, filter, sort, sum...).
And indeed, being able to call methods dynamically in "formulas" like Excel does, and not just when clicking on buttons (what excel calls "macros") is a must-have as well !