Content

Exporting documents from oneWEX Content Miner

When Exporting documents with 'Download' link on Content Miner UI, the document cannot be exported with HTTP Status code 404. To work around the issue, use the REST API as follows:

1. Get the collection id that you submit the document export job with the REST API. For example, save the output to col_list.json file and confirm the collection id in question.

curl -X GET 'https://<ONEWEX_SERVER>/api/v1/collections' -H 'Content-Type: application/json' -H 'authorization: Basic <Base64 encoded username:password>' -k -o col_list.json

2. Get the list of document export jobs of the correction identified in the previous step and get the jobid in question with the REST API.
For example, save the output to test_col.json file.

curl -X GET 'https://<ONEWEX_SERVER>/api/v1/collections/<COLLECTION_ID>/export' -H 'Content-Type: application/json' -H 'authorization: Basic <Base64 encoded username:password>' -k -o test_col.json

3. Identify the jobid in the saved json file. For example,

[
    {
        "state": "Success",
        "result": {
            "fileSize": 1708,
            "startTime": 1540876943478,
...
        },
        "id": "8",
        "tags": [
            "type:exporter",
...
    },
    {
        "state": "Success",
        "result": {
...

4. Download the document with the jobid identified in the previous step with the REST API.
For example, save the output to export_doc.zip file.

curl -X GET 'https://<ONEWEX_SERVER>/api/v1/collections/<COLLECTION_ID>/export/<jobid>/content' -H 'Content-Type: application/json' -H 'authorization: Basic <Base64 encoded username:password>' -k -o export_doc.zip

Building applications with oneWEX Application Builder

• Spell correction on Query Recommendation widget may show a corrected term multiple times. To get the correct result, click the first term. Clicking the secondly appeared term will not work.
• Bar chart or Line chart on Chart widget may not be displayed correctly when the chart orientation is set as "Auto". To work around the issue, specify the orientation (Horizontal or Vertical) explicitly.

Adding a new dictionary to the existing enrichment on UI

When adding a new dictionary to the existing enrichment and save it on oneWEX Admin UI or Content Miner UI, the change is not saved. As a result, newly added dictionary will not appear on UI when you go back to the enrichment UI. To work around the issue, use the REST API as follows:

1. Identify the enrichment ID that you want to add a new dictionary.
   1. Login to oneWEX Admin UI
   2. On the Resource tab, open the enrichment you want to add a new dictionary
   3. From the URL, copy the enrichment ID such as b6a0232d-7bd6-079b-0000-0166ce8de557
2. Open Swagger UI on the same machine at https://<ONEWEX_SERVER>/docs/#/ and expand "Enrichment".
3. Fill the body of the request, and execute POST /api/v1/enrichments/<enrichmentId>/fdics REST API (Create a dictionary) to create a dictionary with above enrichment ID.

Notes:

• After the new dictionary is added, you can edit it and add words in oneWEX Admin UI and Content Miner UI.
• When you call a REST API from Swagger UI, you would need to be authorized first. Use "Authorize" button on Swagger UI.
• If you are familiar with curl or any other tools to issue the REST API itself, do the same operation. See Swagger UI for each REST API details.

Delete Character Pattern Annotator on UI

When deleting a Character Pattern Annotator on UI, the change is not saved. As a result, deleted dictionary will appear on UI when you go back the Character Pattern Annotator UI. To work around the issue, use the REST API as follows:

1. Identify the enrichment ID that you want to add a new dictionary.
   1. Login to oneWEX Admin UI
   2. On the Resource tab, open the enrichment you want to add a new dictionary
   3. From the URL, copy the enrichment ID such as b6a0232d-7bd6-079b-0000-0166ce8de557
2. Open Swagger UI on the same machine at https://<ONEWEX_SERVER>/docs/#/ and expand "Enrichment".
3. Execute GET /api/v1/enrichments/<enrichmentId>/regexconfig REST API (Get the regular expression annotator rules) with the enrichment ID identified in previous step.
4. Save the response as JSON, and edit the JSON object to delete the object that include the ruleId that you want to delete. For example, you can identify the object that you want to delete with defined patterns:

         {
           "ruleId": "5034fe9c-3436-4af6-9d73-754aebc6e675",
           "name": "URL",
           "description": null,
           "matchType": "Document",
           "pattern": "http(s)?://([\\w-]+\\.)+[\\w-]+(/[\\w- ./?%&=]*)?",
           "facetPath": ".url",
           "facetValue": "$0"
         }

5. Fill the request body with you create in previous step, and execute PUT /api/v1/enrichments/<enrichmentId>/regexconfig REST API (Create or update regular expression annotator rules).