I noticed some missconfigurations on the DSpace demo server causing the following issues with the controlled vocabulary.
This is caused by the fact that authority control is enabled (in demo configuration) on this controlled vocabulary field. When switching this off it will work like expected (view screen: https://jira.duraspace.org/browse/DS-1130
This issue is is also caused by misconfiguration, but this isn't just demo. Discovery has received hierarchical metadata support for DSpace 3.0 although this hasn't been enabled for the subject field.
There are two paths we can choose to fix this.
- Fix it on the demo git instance only
- Fix it on the master git & set this to be the default for dc.subject (which has the controlled vocabulary enabled by default in the input forms)
- The downside of this being that if the users remove the controlled vocabulary for dc.subject in the input forms they might not consider changing this for discovery
Kevin Van de Velde
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions