MarkW,
Our challenge is that currently we suffer with Authority Control being
"layered" on top of DSpace as if authority control is a second thought.
THus Authority control only applies in the Submission or Item Edit
Interfaces.
Authority Control needs to be seen as First Class feature of the DSpace
Model. This means that when we say
MetadataValue[] val = Item.getMetadata("dc.foo");
val[0].getAuthority()...
We should be able to access an appropriate Collection or Query Interface to
get to the Set of allowed Values, in Java.
We were talking in another thread about Runtime vs Application
configuration, and authority control is a grey area, but given we want to
be able to make up entirely new metadata fields and curators in an admin
interface, it tends to make sense that we also want to be able to easily
control authority assignment to specific fields as curators as well. In
this sense, Authority Assignment seems to fit in the perview of Runtime
configuration and would more than likely be stored in the database,
possibly with submission, workflow and input-forms configuration.
MarkD
On Thu, Mar 8, 2012 at 11:00 AM, Mark H. Wood <[email protected]> wrote:
> 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 [email protected]
> Asking whether markets are efficient is like asking whether people are
> smart.
>
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
>
--
[image: @mire Inc.]
*Mark Diggory *(Schedule a
Meeting<https://www.google.com/calendar/selfsched?sstoken=UUdDSzJzTTlOUE1mfGRlZmF1bHR8MzgwMmEwYjk1NDc1NDQ1MGI0NWViYjYzZjExZDI3Mzg>
)
*2888 Loker Avenue East, Suite 305, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
http://www.atmire.com
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
