Giuseppe: I can only speculate without knowing more about your setup, but in step 1), putting the .java file in the build/classes directory looks wrong, since that is where compiled classes go, not source files. If your arrangement is typical, it should go in:
c:/dspace-1.4.1-source/src/org/dspace/app/oai Finally, when you have done all the steps, examine the dspace deployment and verify that the oai.properties has the new line, and that the war file contains the compiled class. On Unix, the test would look like: jar tf dspace.war | grep RDFCrosswalk with the output: WEB-INF/classes/org/dspace/app/oai/RDFCrosswalk.class Not sure if you have 'grep' in your environment, Hope this helps, Richard On Fri, 2007-01-12 at 15:45 +0100, Giuseppe Bux wrote: > Richard, > thak you for your quick replay, but unfortunately my attempts to apply your > guidelines was until now unsuccesfull. > My steps: > 1) I added the RDFCrosswalk.java to my dspace source tree, namely to the > folder: c:/dspace-1.4.1-source/build/classes/org/dspace/app/oai; > > 2) I rebuilt and updated the dspace code, by running: > ant -Dconfig=[dspace]/config/dspace.cfg updateand by replacing, in > Tomcat/webapps, the old dspace.war with the new one; > > 3) Then I added the line: > Crosswalks.rdf=org.dspace.app.oai.RDFCrosswalk to > [dspace]/config/templates/oaicat.properties; > > 4)I updated my server configuration by > running the script 'insall-configs' > (I do not find the script 'update-configs') > > 5) I ran: oai2rdf -m rdf > http://localhost:8080/dspace-oai/request rdfdata, > which gives the following error: > 'Error'.java.io.FileNotFoundException: Could not find a > transformer for schema 'No-crosswalk-for-rdf' and namespace 'Error'. > > > What is wrong in my steps? > Thanks > Giuseppe > > ----- Original Message ----- > From: "Richard Rodgers" <[EMAIL PROTECTED]> > To: "General List" <[email protected]> > Sent: Thursday, January 11, 2007 5:41 PM > Subject: Re: OAI-PMH RDFizer: METS transformer xslt? > > > > Giuseppe: > > > > Another approach is to use the attached file (must be added to your > > DSpace source code - see the wiki for details) to OAI export in RDF. In > > addition to DC metadata, each item includes DSpace community & > > collection & thumbnail URLs. Then use the oai2rdf tool with > > the 'rdf' transformer to convert to a format Longwell wants. > > > > Thanks, > > > > Richard > > On Thu, 2007-01-11 at 10:28 +0100, [EMAIL PROTECTED] wrote: > >> Hi! > >> > >> I’m trying OAI-PMH RDFizer with the final goal to export and manage > >> dspace library contents in a SESAME repository. I successfully tried > >> that by using both mods and oai_dc transformers stylesheets available > >> in the oai2rdf distribution. These xsl however capture and render in > >> rdf only the strict dspace item properties . I would capture the > >> whole dspace data model including Community,Collections, etc. the > >> dspace item is related to. The OAI-mets crosswalk feature in dspace > >> allows metadata harvesting of the whole dspace data model, so a mets > >> transformer xsl is necessary for rdf rendering. Unfortunately this is > >> not available in the current OAI-PMH RDFizer distribution: does > >> someone (perhaps Stefano Mazzocchi) wrote that for its personal use > >> and could provide me with? > >> > >> > >> > >> Thanks, > >> > >> > >> > >> Giuseppe Bux > >> > >> > >> _______________________________________________ > >> General mailing list > >> [email protected] > >> http://simile.mit.edu/mailman/listinfo/general > > > > > -------------------------------------------------------------------------------- > > > > _______________________________________________ > > General mailing list > > [email protected] > > http://simile.mit.edu/mailman/listinfo/general > > > > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/genera > � _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
