OCR SaaS: Difference between revisions

From iDigBio
Jump to navigation Jump to search
(Documentation for the OCR SaaS)
 
No edit summary
Line 1: Line 1:
OCR SaaS
'''OCR SaaS'''
 
Needs:


'''Needs:'''
- Accept incoming request and return a refId of the job.
- Accept incoming request and return a refId of the job.
- Process the ocr with the available OCR engines
- Process the ocr with the available OCR engines
Line 10: Line 9:
- Support round-robin features to share service evenly
- Support round-robin features to share service evenly


Future needs:
'''Future needs:'''
- Socket.io support
- Socket.io support
- Cleaning techniques
- Cleaning techniques
Line 34: Line 33:
'''imageAdd( uri, [id], [endpoint] )'''
'''imageAdd( uri, [id], [endpoint] )'''
returns:
returns:
{  
  {  
   success: bool
   success: bool
  , refId: uuid  
  , refId: uuid  
}
  }


imageRemove( refId )
'''imageRemove( refId )'''
returns:
returns:
{
  {
   success: bool
   success: bool
}
  }

Revision as of 15:12, 31 January 2013

OCR SaaS

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
 }