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:
- write your domain metadata mapping using a text editor. See https://wikis.mit.edu/confluence/download/attachments/25395402/metadata.xml an example.
- https://domainname.thalia.mit.edu/resttest.jsp and scrool down to meta data mapping. Copy and paste the mapping xml into the mapping text box, then click on "save mapping" button
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:
- dc_contributor
- dc_coverage
- dc_creator
- dc_date
- dc_description
- dc_format
- dc_identifier
- dc_language
- dc_publisher
- dc_relation
- dc_rights
- dc_source
- dc_subject
- dc_title
- dc_type
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>
Customization of the public library display name:
The public library is named "public" by default. If you want to give it an different name, use the <public_library_name> tag. For example:
<public_library_name>Chemistry Department Image Collection</public_library_name>
Customization of the help URL:
By default, thalia help goes to http://thalia.mit.edu/help. If you want user help to go to a different URL, use the <help_url>tag. For example:
<help_url>http://web.mit.edu/psb/photographs</help_url>
Customization of the upload behavior:
By default, if you start an uplod, the upload screen retains all the metadata entered by the previous upload. If you want that screen to be cleared every time, use the <clear_upload_form> tag. For example
<clear_upload_form>true</clear_upload_form>
Customization of the item hover tip:
By default, the item hover tip is the item title. If you want another field displayed, use the <thumb_mouseover_field> tag. For example
<thumb_mouseover_field>dc_description</thumb_mouseover_field>.
Please note, the value should be one of the 15 dublin core metadata field name.
Turn on the shopping cart feature:
This is specific to PSB. If you want to turn on the shopping cart feature, use the <shopping_cart_on> tag. For example
<shopping_cart_on>true</shopping_cart_on>
Customization of the domain security policy:
By default the domain is open to public. People can use http to access thalia as a guest. However some domains only want to be open to the MIT community.
Use <opentopublic>false</opentopublic> to indicate that only people with MIT certificate can access thalia.