Curating the Portfolio: Connecting Assets
Connecting Assets
The purpose of the CW Data Catalog is to provide the ability to link related assets to catalog users. The CW Data Catalog offers a registry for users to access all of the connected assets in a web of linked data without leaving the data catalog. Using the hierarchical structure when creating assets will guide curators in forming meaningful connections between related assets. This, in turn, shows users significant and meaningful results when searching for assets using keywords and filters. Prior to creating assets lower in the hierarchical structure, such as Datasets for a specific topic, map out how those specific Datasets are connected to a larger System and where the data is coming from- the Service. Use the System as the building block for creating Datasets, Services and other asset types that are all related to the System. As each asset is created, the properties for use in creating connections are part of, serviced by, used by and was generated by.
Connecting Assets to Assets
Part Of- The Part Of relation of a Registered Item explicitly identities other Registered Items for which the referent resource is physically or logically included as a part or component. For example, a Dataset is part of a Dystem or part of a data collection.
Serviced By- The Serviced By relation of an Asset resource explicitly identifies a Service resource that accesses updates, consumes, queries, analyzes, or manipulates the Asset. An Asset may be Serviced By more than one Service resource. For example, a Service can provide data for any related Datasets or Systems.
Used By- The Used By relation of a Registered Item identifies other Registered Items that “use” (depend on, access, analyze) the referent resource.
Was Generated By- The Was Generated By relation links an Asset resource to an Activity resource that created, produced, or generated the Asset. For example, a Dataset was generated by an Application
Validated By- The Validated By relation links the Agent (e.g., Organization, Person, Group) who established the accuracy or legitimacy for the resource. For example, a Dataset was validated by an organization. Note: This property is added through the Attribution property using Role and Relation.
Using these relationship properties to link assets will create the connections in the hierarchical structure from datasets to their related sub-Datasets, Applications, Systems and Services. These connections provide purpose to users viewing assets that may not otherwise have been known to be related. When creating asset relationships, experienced curators suggest starting with a Dataset and building out relationship links from there connecting Applications, Services and Systems. As mentioned, relationships between assets are essential to understanding how multiple entries within the catalog can be interconnected. The connecting properties listed above are representative of the level of the Dataset however, the catalog infers the inverse relationship of the connecting asset. For example, a Dataset is part of a System and the connection was made from the Dataset out to the System. On the links web, the relationship “part of” is shown as well as “has part”, which is the relationship from the System to the dataset.
Connecting Assets to Other Items
Along with connecting assets, assets can also be linked to other meaningful information, such as who is managing the assets or the metadata record, how the asset is being paid for and who/what is using the asset(s).
  • Creator:The Created By property identifies the actor responsible for producing/ making the resource.
  • Publisher:A Publisher is the Agent responsible for making an Asset resource available.
  • Contributor:A Contributor is an Agent responsible for making contributions to an Asset resource.
  • Contact Point:A Contact Point has information about how to contact a person or organization by postal address, telephone, or email.
  • Produced By:The Produced By relation of a Dataset Asset explicitly identifies those System resources that produce or update the referent Dataset resource.
  • Managed By:The Managed By relation links an Asset resource to an Organization resource that manages the Asset.
  • Consumed By:The Consumed By relation of a Dataset Asset explicitly identifies those System resources that consume or use the referent Dataset resource.
  • Was Funded By: The Funded By relation links an Asset resource to an Investment resource that funds the Asset.
  • Primary Investment:The Primary Investment relation links an Asset resource to an Investment resource that is the primary Investment activity associated with the Asset.
  • Attribution:Used to link an entity (e.g. a Dataset, Service, Activity, Organization) to an agent (e.g., an Organization or Person) with a specified role (.e.g., “stakeholder”) For example, the property Validated by is entered as an attribution.