W-23899752 content catalog jh - #552
Open
JennyHajee wants to merge 5 commits into
Open
Conversation
Document the Context Catalog capability for the Limited GA/MVP release: - Add Informatica Cloud Data Governance and Catalog (CDGC) scanner row (new Data scanner type) to the scanner prerequisites reference. - Describe the CDGC scanner's data-asset ingestion in the add-scanners page. - Add a new page for viewing data asset lineage: the Lineage tab, edge detection (observed/declared/inferred + confidence), node and edge types, the explorer, and use cases. Note lineage is Amazon (AWS Bedrock) only in MVP. - Wire the lineage page into the nav and add Context Catalog, Data asset, and Lineage glossary terms. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Rename exp-data-asset-lineage.adoc to exp-data-service-lineage.adoc. - Change "data asset" to "data service" throughout, and refer to the catalog as the Data Services catalog. - Update the page title, glossary term, nav entry, and cross-references. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Align the prerequisites row with the agent-scanner-configuration-service InformaticaCredential and InformaticaRegion definitions: - BASIC auth using IICS username and password (exchanged for a session token), plus a required Region, rather than an IDMC URL or client secret. - List the actual region options: NA, EMEA, UK, APJ, and Canada pods. - Drop the unenforced Catalog Administrator/User role requirement that appeared only in the prototype. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Explain in the lineage topic that creating an Informatica CDGC scanner is what brings in data services and enables lineage, with a new "How Data Services and Lineage Get Populated" section. - Reinforce in the add-scanners Informatica section that the scanner populates the Data Services catalog and enables agent lineage. - State consistently that lineage currently supports only agents discovered from Amazon (AWS Bedrock). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Reference the Context Catalog Data Services catalog wherever the Portfolio catalog set is enumerated: - exp-portfolio-overview, exp-overview, exp-home-start, exp-services-add-to-portfolio, and the glossary Portfolio entry. - Gate each mention on the Context Catalog feature being enabled, and note that the catalog currently appears as "Data assets" in the UI (rename to "Data Services" pending). - Add the same UI note at the first Data Services mention in the Informatica scanner and lineage topics. Data Services is intentionally omitted from instances, conformance, and monitoring enumerations, which don't apply to data services. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.