Kitchen Door for strawberry_runners_postprocessor plugins #58
Labels
API flavor endpoints
Quick access to internals via APIs
Digital Preservation
Unreachable destination for a (digital) Streetcar Named Desire
enhancement
New feature or request
Post processor Plugins
The ones with a ->run() method
queue
FIFO
Milestone
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.
The text was updated successfully, but these errors were encountered: