R3 Ingestion Service (aka Ingestion Framework) - documentation
Thanks to a recent note from @alan.henson , I found lots of useful information in this site. (especially clarify how this related to "Workflow service")
My questions/comments -
Introduction mentions - use for wp+wpc+file. So, what is recommended strategy for loading Master Data? What if I have somehow prepared json/manifest for metadata of 100 wellbores and I am looking for optimal way to add that information? And the same question for Reference entities. Can you make clear statement about support of Master data, Reference data (and overlap with similar capability from Storage service)?
Introduction mentions "files". And the same in example below submitWithManifest. Should that contain "Dataset" instead of "Files"?
Can you also add very high level explanation in "Ingestion API" section about difference among 3 options? Details are provided below. But a high level explanation "up front" will help the reader's mind setting in my opinion.
Example in submitWithManifest is more complete. Example in /V2/submit/manifest - please provide more complete example by populating wp, wpc, file/dataset.
Sample below V2/submit/manifest shows Master, Reference included. This implies that we can effectively use this approach for addition of Master and/or Reference data as well. Please confirm.