On 23 October 2012 13:19, helix84 <helix84@centrum.sk> wrote:
On Tue, Oct 23, 2012 at 1:09 PM,
Kind regards,

Kevin Van de Velde
@mire
Esperantolaan 4 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com - Institutional Repository Solutions

<Kevin@mire.be> wrote:
> Subject keyword box breaks layout for long taxonomy values
> (https://jira.duraspace.org/browse/DS-1328)
...
> Subject keyword box breaks layout for long taxonomy values
> (https://jira.duraspace.org/browse/DS-1328)

Hi Kevin,
you mentioned the same issue twice. Did you mean DS-1296 instead
(which probably also has some duplicates)?
 
This is indeed what I meant, sorry for the mixup.
 


> 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).

Anyway, isn't there anything we can do about it in the default (turned
on) case? (I might have misunderstood because of the issue number
mixup.)

I'm afraid I don't quite understand your question... The problem is since it has authority control enabled, this will override the controlled vocabulary config option in the input-forms.xml.
 

> 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

I don't use either feature, personally. But I'd recommend fixing this
in Git so that the default configuration works, and mentioning this
dependence directly in comments above these configuration options.

Regards,
~~helix84