metadata mapping file is domain specific. It allows individual domain to customize their domain environment, such as the display of their metadata field, the name of their public library, help url, etc. The metadata mapping currently is a xml file. It needs to be loaded into thalia via the resttest.jsp interface:

We are working on an UI interface to make this process easier.

Customization of the dublin core metadata fields:

We have 15 dublin core metadata fields:

You should have an entry for each of those fields in your mapping file to tell the UI weather or not you intent to use this field and how you want this field displayed.

An entry looks like this:

<element>
<dc_field>dc_title</dc_field>
<label>Title</label>
<type>text</type>
<show>true</show>
</element>

<dc_field> is the name of the dublin core field and should be one of the 15 listed above.

<label> is how you want this field displayed in the UI

<show> take a "true" or "false" value. If it is set to false, UI will not display this field and this field will not be used in your domain.

<type> can be text, textarea, or select. "text" will display a text field, "textarea" will display a multi-line text field and "select" will display a list box. If you use "select", you need to list all the options to be displayed in the UI by using an <option-list>, for example:

<element>
<dc_field>dc_source</dc_field>
<label>Storage</label>
<type>select</type>
<option-list>
<option>slide</option>
<option>CD</option>
</option-list>
<show>true</show>
</element>