We should also have an API/smaller kitchen door way of providing Data for a configured @StrawberryRunnersPostProcessor. The idea is that e.g AMI can provide a ready OCR instead of having to go through the whole process. This requires some good planning but I was thinking maybe this:
The Kitchen door will simply deposit for a Given Source File (the UUID) and a given ADO (the ID) a file candidate in a certain location.
Every strawberry_runners_postprocessor instance will check before going full process mode if such exist.
If there, consume (but don't delete, mark to be composted by AMI really, since we might need it again) and/or transform.
If not do what it does, generate
Also: Every strawberry Runner output will also have a file (persisted) representation. This will allow you to build any simple "Text area" element to replace from S3/disk on OCR and trigger Solr reindex.
Another improvement here:
We should also have an API/smaller kitchen door way of providing Data for a configured @StrawberryRunnersPostProcessor. The idea is that e.g AMI can provide a ready OCR instead of having to go through the whole process. This requires some good planning but I was thinking maybe this:
The Kitchen door will simply deposit for a Given Source File (the UUID) and a given ADO (the ID) a file candidate in a certain location.
Every strawberry_runners_postprocessor instance will check before going full process mode if such exist.
Also: Every strawberry Runner output will also have a file (persisted) representation. This will allow you to build any simple "Text area" element to replace from S3/disk on OCR and trigger Solr reindex.