# Product Metadata Guidance

The Product Entry Guidance section covers how to create a metadata record for a product.  A product can be anything from a dataset to a document or presentation to program script or model. mdEditor offers an extensive list of product options, of which "*product*" should never be used. 

## Before You Begin

### Adjust your mdEditor Settings, as needed:

### Select the Product Profile:

After creating your product record initially and before you begin editing metadata, select a profile.   **Product** may be chosen from the **Profile** drop down in the main menu.  A profile limits the available tabs and only shows tabs that contain fields that are required for product creation. Additionally, often a profile also limits the fields from view for a specific type of metadata record--in this case a product record.  For example, funding is not needed for a product and this tab is hidden. 

![The profile selection dropdown is located in the primary horizontal navigation bar.](/files/xVvwttcPvfjFHYwZtFiY)

### **Update your contacts in mdEditor, as needed:** <a href="#make-sure-your-contacts-are-loaded-into-mdeditor" id="make-sure-your-contacts-are-loaded-into-mdeditor"></a>

In mdEditor, contacts are created separately from individual records, and then stored within a contact library. Once contacts have been entered or imported into mdEditor, they can be used in any metadata records.  The Alaska region maintains a master contact list for import that can be found in a file folder in the top level of the [Regional Data Repository](broken://pages/-MkxN4s6rooPFXXa8CeL).  See [Contact Entry Guidance](broken://pages/SoxfQY8NINt73nIJel2Z).

## Complete the Project Metadata Record <a href="#edit-a-project" id="edit-a-project"></a>

* Fill out metadata information for the following tabs:
* Select the Product Profile: from the Main Menu (Top Navigation Bar) select "**Product"** from the profile drop-down menu.
* Choose the specific **Resource Type** that describes your product. Do not choose the generic "product."
* Import or create your product record (see [metadata creation workflow](broken://pages/-MkxR43228ewH1fpBcDM)).
* Fill out metadata information for the following tabs:
  * [Main Tab](/alaska-region-mdeditor-interim-user-guide/dictionary-entry-guidance/main-tab.md)
  * [Metadata Tab](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/metadata-tab.md)
  * [Keywords Tab](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/keywords-tab.md)
  * [Extent Tab](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/extent-tab.md)
  * [Taxonomy Tab](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/taxonomy-tab.md)
  * [Lineage Tab](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/lineage-tab.md)
  * [Distribution Tab](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/distribution-tab.md)
  * [Constraints Tab](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/constraints-tab.md)
  * [Dictionaries Tab](broken://pages/-Lg8aBwUggHRJhXq2fIc)
* If applicable, [associate](/alaska-region-mdeditor-interim-user-guide/product-entry-guidance/associated-tab.md) your products with other metadata records.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ak-region-dst.gitbook.io/alaska-region-mdeditor-interim-user-guide/product-entry-guidance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.