Split up input-forms.xml and explore controlled vocabularies

[alanorth]

input-forms.xml is one big, ugly file right now. It has many templates for many institutes, which makes it hard to manage, and always conflicts with mainline DSpace during upgrades.

We need to be able to split the institution-specific controlled vocabularies into separate files.

[alanorth]

@swebsheet did some more work on this for ILRI subjects. He modifies input-forms.xml to use an external vocabulary as such:

        <field>
          <dc-schema>dc</dc-schema>
          <dc-element>isubject</dc-element>
          <dc-qualifier>ilrisubject</dc-qualifier>
          <repeatable>true</repeatable>
          <label>ILRI Subject Focus</label>
          <input-type>twobox</input-type>
          <hint></hint>
          <required></required>
          <vocabulary>ilri-subjects</vocabulary>
        </field>

With dspace/config/controlled-vocabularies/ilri-subjects.xml containing ILRI subjects previously in input-forms.xml in the following format:

<?xml version="1.0" encoding="utf-8"?>
<node id="ILRISubjectCategories" label="ILRI subjects">
  <isComposedBy>
    <node>
      <isComposedBy>
        <node label="VALUE CHAINS" id="I.1">
          <hasNote>VALUE CHAINS</hasNote>
        </node>
        <node label="AGRICULTURE" id="I.2">
          <hasNote>AGRICULTURE</hasNote>
        </node>
        <node label="AGRI-HEALTH" id="I.3">
          <hasNote>AGRI-HEALTH</hasNote>
        </node>
...

See dspace/config/controlled-vocabularies/srsc.xml for a complete example.

[alanorth]

Works great!

... but resulting metadata is hierarchical, like: ILRI vocabularies::ILRI subjects::VALUE CHAINS.

This creates problems with our existing workflows (search, browse, data cleaning in Excel, etc)... I'm not sure if maybe we can adapt our workflow to use this?

[alanorth]

Looks like there are two solutions to these two separate problems:

• use XML includes to include sub files: http://xml.silmaril.ie/includes.html
• use controlled vocabularies and hierarchies, then adapt XMLUI / Discovery to use them: https://wiki.duraspace.org/display/DSDOC4x/Discovery#Discovery-Hierarchical%28taxonomiesbased%29sidebarfacets

The second option doesn't cover all the UI use cases, but definitely lets us use the power of hierarchies in Discovery facets. A good example of that is on the World Bank's repository: https://openknowledge.worldbank.org/handle/10986/21552?show=full (see the okr.topic etc)

[alanorth]

Option one works! From input-forms.xml:

<!DOCTYPE input-forms SYSTEM "input-forms.dtd" [
<!ENTITY cg-maps SYSTEM "cg-maps.xml">
]>
...
&cg-maps;

And then in cg-maps.xml we just paste the content we want to include.

[alanorth]

Closing in favor of #69.