I've always found it a bit odd about hiding the provenance metadata on the dspace items. I think this metadata came into existence as a weak attempt to introduce some history on the creation of the item.
Likewise I've not been very concerned about its exposure (albeit the submitters email address embedded there) Ideally this user info in the provenence metadata should contain obviscated email addresses like the kind that are allowed as sha signatures in FOAF persons. Attaching that signature as metadata to the eperson and allowing lookup via sha signatures would allow the admins to get back to the user that submitted or approved the item from the metadata. and thus there would be no need to hide the actual metadata fields from the public. I'd like to eventually see this metadata stored differently so that METS packages (or ORE ReMs) can easily be exposed without too much concern for private metadata. The "metadata/" space is currently being used as a "catch-all" for exposing various types of metadata to the user (at least in my usage), it shouldn't be difficult to block it behind either authentication or drop it entirely using the sitemap.xmap configuration of Cocoon in the dspace/modules/xmlui/src/main/webapp/ sitemap.xmap. You'll need to obtain a copy from the dspace-xmlui- webapp/src/main/webap/sitemap.xmap. -Mark On Jul 8, 2008, at 9:43 AM, 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? > > -- > Gary McGath > Digital Library Software Engineer > Harvard University Library Office for Information Systems > http://hul.harvard.edu/~gary/index.html > > > ---------------------------------------------------------------------- > --- > 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 ------------------------------------------------------------------------- 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
