OCR SaaS: Difference between revisions
Jump to navigation
Jump to search
m (→OCR SaaS) |
m (→OCR SaaS) |
||
Line 1: | Line 1: | ||
=OCR SaaS= | =OCR SaaS= | ||
:::;SaaS: Software as a Service | :::;SaaS: Software as a Service. Read more about what SaaS means at [http://en.wikipedia.org/wiki/Software_as_a_service| Wikipedia] | ||
==Needs:== | ==Needs:== |
Revision as of 16:35, 31 January 2013
OCR SaaS
- SaaS
- Software as a Service. Read more about what SaaS means at Wikipedia
Needs:
- Accept incoming request and return a refId of the job.
- Process the ocr with the available OCR engines
- Support zBar for barcode detection
- Support language detection
- Support calling endpoints
- Support round-robin features to share service evenly
Future needs:
- Socket.io support
- Cleaning techniques
- Techniques to determine if the OCR is handwriting or type
- Support imagemagick adjustment techniques for better results
- Support custom training files
- Support Abbyy and OmniPage
- Support EverNote
- Support OpenCV image detection features
Current Plans:
- Use NodeJS along with some
Possible Routes
- imageAdd
- imageRemove
- imageStatus
- queueInfo
- ping
imageAdd( uri, [id], [endpoint] )
returns:
{ success: bool , refId: uuid }
imageRemove( refId )
returns:
{ success: bool }