[ 
http://jira.dspace.org/jira/browse/DS-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11779#action_11779
 ] 

Kim Shepherd commented on DS-699:
---------------------------------

I think it'd be useful to add them, and I know they'll get use over in NZ at 
least (where we've agreed to a standard subject code display format to help 
consistency with our national harvester)

So, I'd recommend keeping the defaults as per your initial patch and JSPUI 
behaviour, and include the default configs (commented-out) in dspace.cfg with 
the brief usage examples.

> ChoiceAuthority plugin for old-style controlled vocabularies
> ------------------------------------------------------------
>
>                 Key: DS-699
>                 URL: http://jira.dspace.org/jira/browse/DS-699
>             Project: DSpace 1.x
>          Issue Type: Improvement
>          Components: DSpace API
>    Affects Versions: 1.6.2
>            Reporter: Michael B. Klein
>            Assignee: Kim Shepherd
>             Fix For: 1.7.0
>
>         Attachments: DS-699_Controlled_Vocab_Authority_Control_Lookup.patch, 
> DSpaceControlledVocabulary.java
>
>
> Since XMLUI is lacking support for the JSPUI controlled vocabulary browser, I 
> implemented a self-named plugin that publishes a ChoiceAuthority plugin for 
> each file in ${dspace.dir}/controlled-vocabularies. The plugin has the same 
> name as the basename of the file; e.g., controlled-vocabularies/srsc.xml is 
> published as "srsc". Each node of the vocabulary's hierarchy is then 
> available as an auto-completable term for that plugin/authority.
> To activate the plugin, add the following to dspace.cfg:
> plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = 
> org.dspace.content.authority.DSpaceControlledVocabulary
> Then, to attach the Research Subject Categories vocabulary to the dc.subject 
> field:
> choices.plugin.dc.subject = srsc
> choices.presentation.dc.subject = suggest
> Since the ChoiceAuthority plugin system binds a vocabulary to a particular 
> metadata field system-wide, instead of making it configurable per collection 
> (as the old controlled vocabulary system does), you'll need to either make 
> sure that you really want it to be a global authority, or create a 
> vocabulary-specific metadata field and use it instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to