Overview

The Knowledge Base outlines how to manage and utilize the API for creating and accessing "scopes" within the system. This process includes creating spaces, defining access permissions, and integrating Microsoft Document Intelligence (MDI) for enhanced document processing capabilities. Below is a structured overview based on the detailed information provided:

1. Scope Management via API

• Creating a Scope: Administrators can create a scope using a cURL command. This includes setting up the scope name and receiving a unique scope ID in response.

• Access Control: After creating a scope, access permissions need to be defined. This is done through creating "Scope Access" objects, specifying whether an entity (user or group) has READ or WRITE access. Two separate access objects might be needed for entities requiring both types of access.

2. Handling Scope Access

• Modifying Access: The interface allows for the modification or removal of access rights through specific cURL commands.

• Querying Scope Details: Administrators can query all scopes or specific scopes with detailed access configurations to oversee which users or groups have what level of access.

3. Document Ingestion and Processing

• Ingestion Modes: Documents can be ingested in different modes, defaulting to converting PDFs to DOCX format or utilizing Microsoft Document Intelligence for comprehensive data extraction.

• Scope-specific Configuration: For enhanced processing like with MID, configurations are made per scope, adjusting how documents are read and managed.

4. Integrating Microsoft Document Intelligence

• Activation and Configuration: MDI can be activated for specific scopes to handle complex documents, especially those with intricate tables and graphics.

• Geographical Considerations: The service is currently in preview in certain regions, with specific considerations for data privacy and service level implications.

5. Maintenance and Optimization

• System Maintenance Endpoints: These are used for tasks such as re-indexing data, rebuilding metadata, and ensuring data integrity.

• Re-ingestion and State Management: In case of issues, content can be re-ingested or forced into a specific state to correct errors or update system data.

6. Cost and Limitations

• Service Costs: Utilizing MDI incurs additional costs per page, which are not covered by standard service tokens.

• Preview Limitations: Being a preview service, MDI has limitations in terms of privacy, security, and data handling that are distinct from fully launched Microsoft products.