Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
Files:
- dspace/config/input-forms.xml
Instructions:
- This XML file contains form definitions, each contained within its own
element. Each
<form>
element contains<form>
elements that represent single pages of input. Each<page>
element contains<page>
elements with instructions for creating the fields on that page. This structure is mocked up below, for a single form with a single page.<field>
<form-definitions>
<form name="traditional">
<page number="1">
<field>
...
</field>
</page>
</form>
</form-definitions>
- The default form has a
attribute whose value is
name
. To change all submission forms throughout DSpace, edit the XML inside this form."traditional"
- To change a submission form for a specific collection, add a new
element with a new and unique collection-related value for the
<form>
attribute. (You can copy the XML from the default and edit as desired, as long as you change thename
attribute value.)name
- Once you've created your new
element, you will have to map it to your specific collection using the
<form>
section at the top of the XML:<form-map>
<form-map>
<name-map collection-handle="default" form-name="traditional" />
</form-map>
- You'll need to create a new
element to "map" your collection's handle to the new
<name-map>
you just created.<form>
- Once you've created your new
- Create all appropriate
elements, numbering them sequentially starting from 1 in the
<page>
attribute. Within them, add individualnumber
elements according to this template:<field>
<field>
<dc-schema>dc</dc-schema>
<dc-element>identifier</dc-element>
<dc-qualifier>citation</dc-qualifier>
<repeatable>false</repeatable>
<label>Citation</label>
<input-type>onebox</input-type>
<hint>Enter the standard citation for the previously issued instance of this item.</hint>
<required></required>
<vocabulary></vocabulary>
</field>
- Stop and restart Tomcat (See Quick Restart in Rebuild+DSpace).
Notes:
- The
element contains the textual hint displayed to the submitter about why the field is required. Leave it empty for optional fields.
<required>
- The
element is optional. It allows you to specify the controlled vocabulary (see Use Controlled Vocabularies for more information) that this field should select its values from. This field also has an optional
<vocabulary>
attribute. If closed is set to true, a user can only select values from the controlled vocabulary. By default, closed is set to false, which allows a user to also enter in free text if he/she chooses. For example:closed
<vocabulary closed="true">srsc</vocabulary>
- The name of the controlled vocabulary must correspond to the name of the XML file (without ".xml") which contains the vocabulary. So, in the above example,
references the vocabulary specified in the file located at dspace/config/controlled-vocabularies/srsc.xml
srsc
- Valid input types (for
) are:
<input-type>
- "date"
- "name" (two text boxes, labeled last and first name)
- "onebox" (a one-line textbox)
- "twobox" (two textboxes on a single line)
- "dropdown" (for which you must specify a
attribute referring to the
value-pairs-name
list of allowed values, see Change+a+form+value)<value-pairs>
- "qualdrop_value" (a textbox, which is preceded by a "qualifying" dropdown of values. Requires a
attribute, similar to "dropdown". Also requires
value-pairs-name
is set to "true")<repeatable>
- "textarea"
- Setting the
element to "true" creates an "Add more" button, which allows you to add multiple values into that particular field. Examples of this include the authors and keywords fields in the standard DSpace submission process.
<repeatable>
Overview
Content Tools