Open Data Federation allows datasets from your domain to appear on other data portals. To be the recipient of federated data, the federation request must originate from a different data portal.
To federate your data with other data portals, first you will need to click on Federation within the administrative panel.
Next, use the search box type in the domain with which you wish to federate. This will return a list of potential matches.
When you set up federation you set a "Search Boost" option that determines how high it appears in searches. The main site will always appear first, and then the "Search Boost" is a score from 0-1, with values closer to 1 appearing earlier.
Note: You cannot change the search boost after you set it for each federation.
Tip! When federating a catalog from smaller entities (such as federating a state catalog with the catalog of cities and/or counties), you may want to adjust the priority of datasets showing up in search queries to manipulate their location in the search list.
By clicking Publish, a request will automatically be sent to the site administrators of the domain as a request to federate into your site. Once they approve the request, federation will automatically happen.
At any point in time, you can Terminate the federation relationship.
Once the federation has been approved, users will see these federated domains when searching your site's catalog, the example below is from New York State
If approvals are being used on the source domain, only assets that are approved and the public will federate to the target domain. These assets will immediately appear in the catalog and will not go through approvals on the target domain, even if enabled.
Note: Both routing and approval, as well as view moderation, are in the process of being deprecated. Existing customers will these features will be migrated to a new approvals workflow before deprecation.
If routing and approval is enabled and you are federating datasets:
- The target domain has routing & approval set up.
- For domains with R&A; set up, only datasets that have been approved from the target domain, along with their derived views, will appear in the catalog. Views derived from unapproved or rejected datasets will not be visible. Datasets and their derived views from the source domain must go through the target's routing & approval process to be visible in the catalog.
- The target domain doesn't have routing & approval set up, but the source does.
- All datasets and derived views of the target domain will be visible in the catalog. Datasets and derived views from the source domain will only be visible in the catalog if the source domain has approved the dataset, or in the case of derived views - the parent dataset is approved.
- Neither the target domain nor the source domain has routing & approval set up.
- All datasets and derived views from both the target and source domains will be visible in the catalog.
If view moderation is enabled and you are federating datasets:
- Both domains have view moderation enabled:
- If both domains have view moderation enabled, all views that have been approved from the source domain will appear in the catalog, and will not go through view moderation on the target domain.
- The source domain has view moderation enabled but the target domain does not:
- Any approved views from the source domain will appear in the target domain, and will not go through additional view moderation because it is not enabled on the target domain.
- The source domain does not have view moderation enabled but the target domain does:
- None of the views from the source domain will appear in the target domain, and they will not be listed in view moderation for approval.
- Neither the source nor the target domain has view moderation enabled:
- All views from the source domain will appear in the target domain, and they will not go through view moderation.