Replies: 2 comments
-
In general that sounds like a nice idea to me. Depending on how many settings you want to be able to apply before running the manual OCR, this could be a bit of work though. From an MVP perspective I'd develop this gradually like:
From a processing perspective I think that processing the files synchronously would be the best and easiest idea. This would lead to the fact that an user would need to wait until the OCR process has finished after he clicked on the menu item. What are your thoughts? Any coding help would also be appreciated 👍 |
Beta Was this translation helpful? Give feedback.
-
Yes, the generic approach seems fine to me. For what it's worth, I wouldn't even expect a separate UI, but if it's feasible, sure, why not? As for the synchronous execution: I'd basically use the same job submission / progress indication method which is used by other file operations. That way the user can see something is happening on their behalf, and how it is going. When it comes to coding help: I haven't developed anything for NC yet, but if you're willing to give some guidance, then I might be up for it. |
Beta Was this translation helpful? Give feedback.
-
While having the ability to automatically OCR files in Flow, it would actually make sense to make this available manually, from the UI. It could e.g. be an item in the context menu of supported file types.
There's cases where I don't want to set up a complete workflow, I just need some file to be OCR'ed. Also, when I do want to set up a workflow, but I already have a bunch of files there before setting it up, it would be nice to be able to process those manually (yes, a whole selection in a single operation, too).
I guess all the settings could be taken from where the Flow version does. But with manual invocation, it might not make sense to keep those settings at the bottom of the Flow settings page.
Beta Was this translation helpful? Give feedback.
All reactions