# Process Metadata

# POST POST Process Metadata

# /data-catalog/api/process/metadata

# Description

Process the metadata for the given connection and file specified in the url of the event message body received. Url contains the complete path information of the metadata file received on azure blob storage. This process reads the file content from the blob and creates the module in data catalog with file path information. For subsequent processing when new metadata file is placed in blob, the process will compare the new metadata file with the previous one and creates a module with incremented version. Comparison result / changes in the files are kept in that new module entry.

# Payload

{
      "url": "https://genrwfs25euwdev.blob.core.windows.net/genix-rawstore-business/021badb7-ad38-4c85-89a4-c99a7a9e4eec/f7d875b5-0ad1-4b96-87ea-9ffef591d0f1/07242c4b-08dc-48eb-b7ad-40e0d1f43afc/abb.ability.device/OPC001/metadata/metadata_v1_20250121032533.json"
}

# Responses

Code Description Schema
200 Successfully processed
400 Bad Request. Something wrong with request body.
401 Not Authorized. Either the Access token is missing or the access token validation failed ServiceErrors
403 Access Forbidden. Requesting entity does not have enough permissions to access the resource ServiceErrors
409 Conflict. File already processed
500 Service error. Service has encountered one or more unexpected conditions that prevented it from fulfilling the request, which may or may not be temporary. Response will contain more details about these errors ServiceErrors
Last updated: 5/5/2025, 4:46:50 AM
Feedback