Last update: 2008-02-13
MODS Editor is a Cocoon package that generates a web form for editing MODS records. It uses the Cocoon Forms framework. It attempts to provide all the elements in the MODS 3.2 spec (except mods:extension), and it provides a very flexible mechanism for customizing a form to meet the needs of a particular project.
The sample records below are taken from the MODS site. You can edit them as you wish; when you submit, though, the changed record will not be saved, it will just be displayed back to you in XML.
|Item||MODS record||Full form||Localized
|Article in a serial||xml||form||form|
|Serial special issue||xml||form||form|
Localizers are a mechanism for adapting the MODS form to the needs of a particular project. Since the main form implements the full range of MODS fields, implementors will typically want to remove those elements that are not used by their project. They may also want to customize certain options, such as selection lists for permissible values in a given field (e.g. note types).
To achieve these results, all that is necessary is to write a simple configuration file in XML that represents the desired changes. The MODS Editor framework uses this config file to generate an XSLT stylesheet, which is applied to the Cocoon Forms configuration files (model, binding, and template), ensuring that consistent changes are made to each of them. The stylesheet and the modified Cocoon Forms config files are generated on-the-fly.
To see the localizer config file or the XSLT stylesheet that it produces, click the "xml" or "xsl" links for any of the localizers below. The work of the localizer depends heavily on the classes used in the Cocoon Forms config.
This is used to test localization functions. Currently it makes the following changes to the form: