Asynchronous Concept Extraction From a Zip Container

With these services an asynchronous extraction processing of zip files is possible. This approach allows a client to receive the extraction response independent from requesting the service.

The client orders the processing of the provided file, receiving a taskId from the system to identify the processing task in later calls.

After receiving the file, the zip file is inserted into a processing pipeline.

Finally, the extraction result can be collected using the taskId as soon as the processing is finished.

Similar to Concept Extraction From a Zip Container there are two basic processing options for zip containers:

1) extraction results for each document individually

Mimetype of request must be 'multipart/form-data'

POST /extractor/api/extract/zip/async + zip file

2) extraction results aggregated for the whole zip container

Mimetype of request must be 'multipart/form-data'

POST /extractor/api/extract/zip/aggregated/async + zip file 

GET /extractor/api/extract/zip/taskstatus?taskId

Returns the current status of the specified task in the extraction pipeline.

After the zip file passed the processing pipeline the result can be retrieved by providing the taskId. Depending on the processing option, defined during pipeline start, the results can be retrieved by using one of these services:

Returns a asynchronous called extraction identified by the task id

GET /extractor/api/extract/zip/task?taskId

Returns a asynchronous called aggregation extraction identified by the task id

GET /extractor/api/extract/zip/task/aggregated?taskId

Example showing usage of the async Extraction service

Step 1: insert zip file into pipeline & receive taskId as immediate response

Step 2: check status of specified task

Step 3: retrieve extraction result of specific task after completion of the process