There was discussion yesterday of reworking the choice/authority control configuration to use Spring.
Looking at the Properties-style configuration, it seems inside-out to
me. Here's what I currently have in mind:
<bean id='fields' class='org.dspace.authority.Fields'>
<property name='minconfidence' value='ambiguous'/>
<property name='configuration'>
<set>
<ref bean='dcContributorAuthor'/>
<ref bean='dcContributorEditor'/>
<!-- more... -->
</set>
</property>
</bean>
<bean id='dcContributorAuthor' class='org.dspace.authority.Field'
p:schema='dc' p:element='contributor' p:qualifier='author'
p:plugin='someChoicePlugin'
p:presentation='select'
p:closed='true'
p:controlled='true'
p:required='true'
p:minConfidence='failed'/>
<bean id='dcContributorEditor' ... />
'fields' would somehow be injected into ChoiceAuthorityManager. I suppose
this means declaring an initially useless instance:
<bean class='org.dspace.authority.ChoiceAuthorityManager'>
<property name='fields' ref='fields'/>
</bean>
and tucking away the reference in a private static Fields. If usage
of Spring spreads, this instance might someday be wired into other
objects in place of calling getmanager().
I suspect that Field might become more elaborate and be used more widely.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Asking whether markets are efficient is like asking whether people are smart.
pgpjvfqjXojnS.pgp
Description: PGP signature
------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
