Terms | Description |
|---|---|
Bulk create | A feature that a Data Marketplace Administrator uses to create multiple data assets at once. |
Category | A category is a grouping of related data collections. It is a predefined classification where stakeholders can publish the data collections for which they are responsible. For example, if a Data Marketplace Administrator wants to publish employee policy documents to the Data Marketplace, the most suitable category for the documents might be "Human Resources". |
Checkout | The steps taken by a Data User to order a data collection. To use a data collection, a Data User submits an order for it. The stakeholder of the ordered data collection verifies the compliance parameters, approves the Data User's request to access the data collection. |
Consumer access | A record that indicates a Data User's access to a data collection, along with other details such as the date of delivery, details of the stakeholder that delivered the data, and the delivery option that was used for the delivery. |
Data asset | A representation of data in an organization. Data assets may contain relevant data elements and are contained in one or more data collections. |
Data collection | A data collection is a grouping of one or more data assets. If a Data User requires access to a data collection, the user can place an order for the data collection. For example, the HR team in an organization publishes all employee policy documents to the Data Marketplace as an "Employee Claims Made to the Company Health Plan" collection. |
Data element | A data element is the smallest unit of data that is present in Data Marketplace. A grouping of one or more related data elements forms a data asset. |
Delivery target | A delivery target is delivery option that a stakeholder of a data collection can use to deliver data to a Data User. Stakeholders use delivery templates to create new delivery targets for their data collections. For example, a stakeholder for a collection of XML files can specify the XML format and HTTPS method as the data collection's delivery target, with the location being "https://company.com/datawarehouse/XMLFiles". |
Delivery template | A delivery template contains the delivery format, the delivery method, and the location where the data is delivered to the Data User. The Delivery Owner creates and manages the delivery templates. For example, the Delivery Owner can create a delivery template with the delivery format XML, and specify the delivery method as HTTPS accessible via the location "https://company.com/datawarehouse". |
Fulfillment | The process utilized to provide a Data User access to the requested data. |
Order | An order is a request made by a Data User to gain access to a data collection. A Data User's order is reviewed by the stakeholders of the data collection who are responsible for the approval and fulfillment of the order. |
Terms of use | The terms of use provide usage requirements and guidelines that a Data User must accept to use the data. |
Usage type | A usage type defines the contexts within which an individual can use data. Stakeholders can utilize usage types to specify the intended use of their data collections. Data Users can utilize usage types to cite their intention when they order a collection. |