# Metadata Metadata can be associated with spatial data sources in JMap. It can include information such as the person who produced the data, the date it was updated, a description, etc. Users can view this information for the corresponding layers in JMap applications. Metadata can be entered directly into JMap Admin using preset templates or it can be taken from an external metadata management system. Refer to the [Metadata Templates](#metadata-templates) section for more information on creating templates. To access the metadata settings of a spatial data source, click on **Metadata** in the details section of a spatial data source. The following options are available:


Metadata
Type	3 options are possible: None: No metadata is associated with this data source. External: The metadata comes from a metadata management system that is outside of JMap and accessed through a URL. The URL must be entered in the URL field below. Template: The metadata is entered directly in this section using the selected template.
URL	If the type of metadata is external, this setting defines the URL to be opened in order to view the metadata associated with this spatial data source.
Template	If the type of metadata is template, select the template to be used for this data source. The metadata entry form for this template displays. Enter the metadata in the various fields.

Layers whose data originates from spatial data sources with metadata will automatically inherit this metadata. Metadata can be viewed by users of JMap Web and JMap Pro applications. ## Metadata templates JMap Server allows you to define metadata templates to document spatial data sources directly in JMap Admin. Once the template has been defined, you can associate it to certain data sources and enter all the information, which users can then easily view in JMap’s applications. If you already use a metadata management system that can be accessed in a browser, you can also create a direct link between certain layers and this system. You can create as many metadata templates as you want. The metadata template management section can be accessed by clicking on **Metadata templates** in the **Spatial data** section. ## Creating a metadata template Click on **Create** to create a new template. The interface shows the following options.


Metadata template
Name	Enter a name for this template. Template names must be unique.
Default language	Among the languages available for the metadata template, choose the default language that will be used when the requested language is unavailable or when translations are missing.
Available languages	Select one or more languages that will be supported for this metadata template. All text elements in the template's configuration (section and field names, field values) will have to be translated into each supported language. You must select at least one language.
Section name	You can define one or more metadata sections. Enter a name for the current section. Click on to add a new section. Click on to delete a section.
Label	Enter a label for the field. The label text will be displayed in the metadata entry window and in the consultation interface. Click on to add a new field. Click on to delete a field.
Type	Select the type of field. The following types are available: TEXT: Alphanumeric data entry field on a single line. TEXTAREA: Data entry field spanning multiple lines to allow for longer text.
Mouseover	By selecting this option, the field value will be displayed in the mouseover bubble when a layer is pointed in the layer bar of JMap Server applications. This bubble presents a summary of a layer's metadata.

--- # 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://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/spatial-data-sources/configuring-spatial-data-sources/metadata.md?ask= ``` 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.