Larry, I think this would be an interesting project. But I will propose three points of concern.
1.) Authority Control aligns with Vocabulary Encoding Constraints found in the the DCMI DescriptionSetProfile (http://dublincore.org/architecturewiki/DescriptionSetProfile). More specifically, DCMI Vocabulary constraints allow for a Vocabulary Encoding to be defined and asserted on metadata values. We are working to express and utilize this for the DSpace 2.0 Metadata Management and it would assist us highly if the implementation of Authority Control took this model and its domain into consideration when being implemented. This is an example of our trying to assure that changes made to 1.6 align with 2.0 and provide a stepping stone for 1.5 users to 2.0. See: https://scm.dspace.org/svn/repo/dspace2/trunk/api/src/main/java/org/dspace/services/model/metadata/NonLiteralConstraint.java and consider that Vocabulary Encoding Constraints have their own set of attributes it might be valuable to consider. 2.) Resources are spread pretty thin in the DSpace community and catching, evaluating and committing in-house projects thrown over the wall is quickly becoming a thing of the past. I would recommend that if this is something you want to see gotten into the codebase, seriously consider getting the permissions necessary to do it yourself (or perhaps permissions to do your proof of concept in an svn branch at scm.dspace.org/svn/repo/dspace/branches first) and then merging it in shortly afterward before it significantly deviates. With the new granular svn access controls this is indeed a tractable. My concern is that the 1.6 projects are piling up and assuring work is gotten in requires time and effort on the part of the "stakeholder". 3.) Confidence is an interesting idea, but certainly not part of the DCMI DescriptionSetProfile. We do need to consider how we will encode assertions about metadata fields assigned to a resource, not only something like confidence, but also, for instance who asserted it and policies on its management. This reminds me of your BitstreamFormatRenovation work, something I still consider important to get into DSpace. Considering not using the Data Model to directly encode this, but instead looking to the same Service Architecture strategy employed in 2.0 where alterations are encapsulated in a separate model, service and persistence store (even if it is the same database) independent of the core may be important and appropriate to assure alignment with the 2.0 Architecture. Cheers, Mark On Wed, May 13, 2009 at 6:38 PM, Larry Stone <l...@mit.edu> wrote: > I have to add an authority control mechanism to DSpace for an > institutional repository, so I'm doing it as modification to the 1.5.2 > source in the hope it will get adopted into 1.6. > > To begin discussion, I put up a wiki page about the design: > http://wiki.dspace.org/index.php/Authority_Control_of_Metadata_Values > > Since I have to get this into production locally in the fairly near > future, please read it and respond promptly so there is time to > consider your comments. There are also a few opportunities to fill in > work I will not have time to do (JSPUI support, for example) so let me > know if you're interested in volunteering to help. > > -- Larry > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel > -- Mark R. Diggory http://purl.org/net/mdiggory/homepage - Bio ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
