Provide the ability to create a Catalog against a single Cloud Object Storage bucket. This provides several benefits:
- The ability to use a Cloud Object Storage bucket as an "Incoming Destination" to quarantine all new content
- It enables a small set of "Data Engineers" or "Content Administrators" to have one location and flow for all raw or incoming data sets to follow. From this "Incoming bucket or destination content is screened, cleansed, moved and published in the larger area wide catalog.
- It facilitates Content providers (both internal and external to a team or business) with a place and process to push all raw content to so it can be screened before allowed in a more area wide catalog.
- It makes very efficient use of content repositories and their logical isolation mechanisms (bucket level isolation in COS).
- This provides an excellent start for creating an event driven data cleaning / data cataloging workflow.
Why is it useful?
|Who would benefit from this IDEA?||Content Provider, Content Administrator, Data Engineer|
How should it work?