Build/Store/Render drupal forms that allow for the manipulation of XML files.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.github Address ISLANDORA-1616; Take avantage of new GitHub functionality and… Mar 17, 2016
api Conform to Islandora coding standards (pt.2) Mar 6, 2018
elements Merge pull request #254 from d-r-p/7.x-ISLANDORA-877 Jun 14, 2018
schema line ending fix Apr 12, 2013
tests Clearing up hook naming changes. (#221) Feb 14, 2017
.gitattributes Added info/module files and .gitattributes Jun 16, 2011
.gitignore Add newlines at end of a couple files. Mar 19, 2014
.travis.yml force PHP 5.3.3 to run under Ubuntu Precise Sep 12, 2017 ISLANDORA-1698 - update Apr 7, 2017
LICENSE Update LICENSE Mar 1, 2017
build.xml place the test cm in the tests folder Feb 4, 2014 code review fixes Feb 4, 2014
xml_forms.module pass coder, phpcpd and lint. f'reals. Feb 14, 2014

Islandora XML Forms Build Status


XML Forms is a collection of Drupal modules that allow for the manipulation of XML documents though Drupal forms. The Islandora Form Builder (XML_Forms modules) makes it possible for users to create, copy, and edit ingest forms, and to affiliate them with Content Models in the repository.

The following Modules are installed as part of the XML Forms package. See inline documentation for additional details.

  • Objective Forms
  • Islandora XML Form API
  • Islandora XML Schema API
  • Islandora XML Form Elements
  • Islandora XML Form Builder
  • Islandora XML Forms

Objective Forms

This module allows for the creation of Object Based Drupal Forms. It provides a number of functions and class for processing/populating forms.

Some important notes.

  • Each Form Element is assigned a unique hash Form Property to identify it, #hash.
  • Each Form Element that is created is stored in a registry and it will persist though out the lifetime of the form even if it's removed from the form. Ancestry of Form Elements is stored so if a Form Element is cloned we will be able to determine the Form Element that it was cloned from.
  • Form Properties can be objects. To define new Form Properties implement the hook objectify_properties.
  • Forms will be auto-populated from $form_states[‘values’].
  • There is a FormStorage class that can be used to store any persistent data.

Islandora XML Form API

The core of the library this module provides functions for processing XML files through forms.

In essence this module models

  • The form to be processed.
  • The Form Properties needed to manipulate XML
  • The XML document to be manipulated
  • The actions required to generate repeating Form Elements (tabs,tags) from the XML document
  • The schema needed to determine the insert locations of elements and the validation requirements. (included via the Islandora XML Schema API)

Islandora XML Schema API

This module provides functions for processing Schema files. It's used to determine where to insert XML Nodes, and how to validate them.

Islandora XML Form Elements

This module defines custom Drupal Form Elements along with AHAH callbacks.


This module requires the following modules/libraries:


Install as usual, see this for further information.


Create and import forms at Administration » Form Builder (admin/islandora/xmlform).


You can also set whether a default DC XSLT will be enforced.



Further documentation for this module is available at our wiki.


Having problems or solved a problem? Check out the Islandora google groups for a solution.

Known Issues

  • Creative Commons Form Element: Note that there seems to be a bug in the Creative Commons API triggered by certain combinations of License Jurisdiction and other parameters. Querying, e.g., "Yes, as long as others share alike" for Allow modifications of your work? and "Finland" for License Jurisdiction results in a CC-BY-SA, resp. CC-BY-NC-SA, 4.0 International license, instead of the corresponding 1.0 Finland version (which exists and is not deprecated). The only way to obtain the correct license in this case is to enter, resp., manually (choose "Manually select a license URI" for Select a license type). Also, this kind of licenses cannot be set by administrators in Form Builder as Default Value for the Creative Commons Form Element.


Q. Can I convert an existing field to any form element type listed in the "Type" options under the "Common Form Controls" tab (or create new form elements using any form element type)?

A. No. The following element types are not supported for full CRUD (create/read/update/delete) operations:

  • checkbox
  • checkboxes
  • date
  • file
  • managed_file
  • password_confirm
  • radio
  • radios
  • tableselect
  • vertical_tabs
  • weight
  • button
  • image_button
  • submit


Current maintainers:


If you would like to contribute to this module, please check out In addition, we have helpful Documentation for Developers info, as well as our Developers section on the site.