Data & Insights federation architecture supports a two site data model for cases where there is a need to federate public assets from an Enterprise Data Platform site to an Open Data Platform and allow community users to interact with those assets in the same way they would with public assets from the Open Data Platform.
What does this mean?
Users can view those data federated assets in the Open Data Domain Catalog (open in the url of the target domain, open in the same tab, have similar access to view, download, etc.)
Users can create derived assets on federated assets that live on the target open data domain
Once public data federation is enabled between two domains, approved public assets will federate from the internal Enterprise Data Platform site (source) to the Open Data Platform site (target). To learn more about unsupported assets please visit this support article. For steps on how to set up Data Federation, check out our Setup Guide and How-To-Video.
How can I access and interact with the data federated assets on the Open Data Platform?
Users will be able to discover those data federated assets in the Data Catalog, Admin → Assets and Asset Selectors.
Only roled users will see the source domain in “Data Provided by” facet at the target Open Data Domain.
Users will be able to view "Primer" for both federated and native datasets and filtered Views. Users will be able to see “View Based on" for derived views in Primer/grid views at the target domain if the Parent is public.
Every asset has a singular "home" domain, where it can be modified. Data federated asset appears as read-only on non-home domains and cannot be edited anywhere but their home domain. To make any changes to the data federated asset, roled users can click on the “Go to Source Asset" link on the target domain’s Asset Action Bar which will take the user to the asset on the source domain. Users will need to have appropriate access levels at the home domain to modify the data federated asset at the source.
Public assets federated with stories and embeds will link back to the federated version of themselves on the target Open Data domain.
Users can create derived assets on federated assets that will live on the target Open Data domain.
Derived assets created from federated assets will be gated through the public approvals process at the target Open Data domain.
Users can see all incoming federated assets with “Public” audience visibility along with the native assets created on the site in Administration Assets → All tab.
Users can easily view all incoming federated assets with “Public” audience visibility in the “Federated” tab and can filter assets by “Source” attribution.
“Go to Source Asset” action will take the user to the asset on the source site.
How to interact with federated assets at the source site?
During the “Publish” action, users will be prompted with text indicating that the asset will be federated and published to one or multiple sites if selected for “Public” audience visibility. The list will include all federated Open Data sites where the asset will be discoverable.
Approver(s) at the source will notice a similar text that once the asset gets approved, it will be immediately available to one or multiple site.
Users will receive a warning while changing the audience level of an existing federated asset from “Public” to “Private” or “Internal”(i.e. making it “inaccessible” for federation) at the source. Taking this action will remove the asset from being discoverable at the target domain and any child assets relying on this asset will break.
Users will notice an error while trying to delete a data federated asset from the home domain if there are one or more derived assets on the target. The derived asset(s) must be deleted on the target before the user can delete the parent asset on the source.