Skip to content

Commit b44b98b

Browse files
committed
fix review comments
1 parent d558b54 commit b44b98b

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/energy-data-services/concepts-manifest-ingestion.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ ms.custom: template-concept #Required; leave this attribute/value as-is.
1212
# Manifest-based ingestion concepts
1313
Manifest-based file ingestion provides end-users and systems a robust mechanism for loading metadata about datasets in Microsoft Energy Data Services Preview instance. This metadata is indexed by the system and allows the end-user to search the datasets.
1414

15+
Manifest-based file ingestion is an opaque ingestion that do not parse or understand the file contents. It creates a metadata record based on the manifest and makes the record searchable.
16+
1517
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
1618

1719
## What is a Manifest?
@@ -52,7 +54,7 @@ The Manifest-based file ingestion workflow consists of the following components:
5254
* **Search Service** is used to perform referential integrity check during the manifest ingestion process.
5355

5456
### Pre-requisites
55-
Before running the Manifest-based file ingestion workflow, customers must ensure that the user accounts running the workflow have access to the core services (Search, Storage, Schema, Entitlement and Legal) and Workflow service. As part of Microsoft Energy Data Services instance provisioning, the OSDU™ standard schemas and associated reference data are pre-loaded. Customers must ensure that the user account used for ingesting the manifests is included in appropriate owners and viewers ACLs. Customers must ensure that manifests are configured with correct legal tags, owners and viewers ACLs, reference data, etc.
57+
Before running the Manifest-based file ingestion workflow, customers must ensure that the user accounts running the workflow have access to the core services (Search, Storage, Schema, Entitlement and Legal) and Workflow service (see [Entitlement roles](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/osdu-entitlement-roles.md) for details). As part of Microsoft Energy Data Services instance provisioning, the OSDU™ standard schemas and associated reference data are pre-loaded. Customers must ensure that the user account used for ingesting the manifests is included in appropriate owners and viewers ACLs. Customers must ensure that manifests are configured with correct legal tags, owners and viewers ACLs, reference data, etc.
5658

5759
### Workflow sequence
5860
The following illustration provides the Manifest-based file ingestion workflow:

0 commit comments

Comments
 (0)