[
http://jira.dspace.org/jira/browse/DS-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11773#action_11773
]
Michael B. Klein commented on DS-699:
-------------------------------------
I can think of three potential configuration options to go with this plugin,
with the defaults representing the behavior of the JSPUI controlled vocab. The
examples come from srsc.xml.
OPTION: [pluginName].value.type = [id|label]
MEANING: Should the resulting stored value be the selected text label, or the
ID of the node containing the selected value? (Displayed value will be the
label either way)
EXAMPLE: "VR110102" vs. "History of religion"
DEFAULT: label
OPTION: [pluginName].hierarchy = [true|false]
MEANING: Should the text displayed (and stored, if value.type.equals("label"))
include the entire hierarchy chain (true) or just the selected node's text
(false)?
EXAMPLE: "History of Religion" vs. "Research Subject Categories::HUMANITIES and
RELIGION::Religion/Theology::History of religion"
DEFAULT: true
OPTION: [pluginName].delimiter
MEANING: The delimiter to use when concatenating the hierarchy.
DEFAULT: "::"
Would those be useful additions, or is it best to leave it as is? They're all
dead simple to write, but I don't want to complicate things if nobody would use
them.
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
