Introduction

Implementation

Upon creation of a document a sample is copied from the sample doctype directory. This sample already contains some sample meta data. The creator then applies an XSLT transformation to this sample which adapts the sample values to the values suplied in the creator request. This values are partially filled in by the user (subject, desciption, etc.) and partly by the system (creator, creation data). This is done in the create ant task which at the end invokes an xslt task which applies the addMetaData.xsl stylesheet which adapts the meta data according to the request values.

Display Meta Data

The display of meta data is handled by the meta.xsp xsp.

Modify Meta data

The modification of meta data is handled in the info.xmap sitemap. The matcher makes sure to check the document out before the modification and checking it back in after the modification. This is done using the ReservedCheckoutTestAction and ReservedCheckinAction. If there is an error the request is redirected to the meta data screen which displays a warning saying that the checkout or checkin failed and who was locking the document since what date and time.

Once the document is checked out the modifications are applied with the help of an ant task. There is a target named save-meta-data which simply invokes the ant task WriteDCParametersTask. This task saves the meta data using the DublinCore interface.

Involved classes, XSPs and XSLTs

The following classes, XSPs and XSLTs are involved in meta data handling: