Field | Description | Example |
---|---|---|
Reference ID | Enter a reference identifier for the data collection. Field Type: Free text; optional Guidelines: If you don't specify a reference identifier, Data Marketplace automatically assigns a unique value to the object. If you want to specify a reference identifier, enter a unique alphabetical, numeric or alphanumeric value. You can also use special characters when you enter a reference identifier value. Ensure that the value that you enter doesn’t use a prefix value that is configured in Metadata Command Center. For more information about reference IDs, see the Manage reference IDs of objects topic in the Set Up Data Marketplace help. | You can specify DCollection01 or DC-1 as the reference ID of a data collection. However, if DCL- is a reference ID prefix that is configured in your Metadata Command Center, you cannot use DCL-1. |
Name | Enter a name for the data collection as you want it to appear in Data Marketplace. Field Type: Free text; required Guidelines: Enter a name that represents the data that it contains. You could choose a name that is similar to or is a combination of the data assets within the data collection. | Customer Address and Profile Data |
Purpose | Enter a description for the data collection. Field Type: Free text; required Guidelines: Enter a descriptive text so that so that Data Users can easily find the data collection. You can explain the nature of the data and the purpose for which it was created so that users can decide whether it meets their business requirements. If you use a CSV file to upload data collections, do not enter commas in the description. Commas are used as column separators. Consider rephrasing the description to avoid commas. | Data collection featuring two data assets. One is a customer address data set with location details. The other is a customer profile data set with demographics. Originally created for marketing purposes. |
Category | Specify the category within which you want to create the data collection. Field Type: Fixed value; required Guidelines: Enter the category name exactly as it appears in the Data Marketplace user interface. | Customer |
Certified Uses | Specify the most suitable use for the data. Field Type: Fixed value; optional; multi-select Guidelines: Enter a value that represents the usage context accurately. | Analytics |
Data Owners | Enter the email addresses of the individuals or the names of the groups that you want to assign as stakeholders of the data collection with the Data Owner stakeholder role. Field Type: Fixed value; optional Guidelines: Use semi-colons to separate your entries, and do not enter a space between each entry. Ensure that the users are aware of their responsibilities before you assign them the Data Owner role. Additionally, ensure that the users are already assigned the Data Owner user role in the Administrator. For more information about the responsibilities of a Data Owner, see the Data Owner topic in the Introduction and Getting Started help. | jdoe@informatica.com;Marketing |
Technical Owner | Enter the email addresses of the individuals or the names of the groups that you want to assign as stakeholders of the data collection with the Technical Owner stakeholder role. Field Type: Fixed value; optional Guidelines: Use semi-colons to separate your entries, and do not enter a space between each entry. Ensure that the users are aware of their responsibilities before you assign them the Technical Owner role. Additionally, ensure that the users are already assigned the Technical Owner user role in the Administrator. For more information about the responsibilities of a Technical Owner, see the Technical Owner topic in the Introduction and Getting Started help. | janeD@informatica.com;Sales |
Status | Select a status for the data collection. The status determines whether the data collection is discoverable by Data Users when they search for it. Field Type: Fixed value; required Enter one of the following values:
Guidelines: Typically, the data collections you create should be in the published state. If you are creating unpublished data collections, ensure that you have a valid reason for doing so, or create the data collections at a later time. | PUBLISHED |