On Jul 8, 2008, at 3:37 PM, Conal Tuohy wrote:

> On Tue, 2008-07-08 at 12:43 -0400, Gary McGath wrote:
>> In order to prevent provenance metadata from being easily reached by
>> users, and to make embargoing watertight, I'd like to disable the
>> "metadata" URLs in Manakin. (I've disabled METS output in the OAI
>> provider for the same reason.) Since they're useful for debugging
>> purposes, it would be nice to have them available, so changing the  
>> path
>> component from "metadata" to something else seems like a useful
>> approach. To this end, I edited
>> (dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/sitemap.xmap) and
>> changed the relevant map:match element.  When I restarted DSpace,
>> though, it hung. Changing it back let DSpace run normally.
>>
>> Is there something else that needs to be changed in order to  
>> disable or
>> modify the metadata URLs?
>
> The problem with disabling the pipelines which handle those URLs is  
> that
> other parts of Manakin depend on them. The "theme" XSLTs which display
> item metadata on item pages, for instance, dereference those URLs to
> obtain the item data. :-)
>
> What you should be attempting is to patch the pipelines which handle
> those URLs, so that the sensitive information is filtered out. Take a
> look at this pipeline fragment, for instance:
>
> <map:match pattern="metadata/handle/*/*/**">
>    <map:generate type="DSpaceMETSGenerator">
>       <map:parameter name="handle" value="{1}/{2}"/>
>       <map:parameter name="extra" value="{3}"/>
>    </map:generate>
>    <map:serialize type="xml"/>
> </map:match>
>
> If you insert a <map:transform src="exclude-sensitive-metadata.xsl"/>
> element between the generator and the serializer, then you can have
> complete control over what metadata Manakin exposes. e.g. removing any
> dc.description.provenance fields which include an "@" character.
>
> -- 
> Conal Tuohy
> New Zealand Electronic Text Centre
> www.nzetc.org

Thats a pretty slick solution Conal!

I'm still tempted to suggest that those xslt's should be using / 
internal/metadata/handle over /metdata/handle... scott can you  
comment on why this isn't always the case?

-Mark


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to