Hi Ricardo, As you've noticed, out-of-the-box, DSpace can only Harvest OAI-PMH with the following metadata formats: * Dublin Core (oai_dc) * Qualified Dublin Core (oai_qdc) * DSpace Intermediate Metadata (oai_dim)
However, these settings are configurable within 'dspace.cfg' (look for the settings beginning with "harvester.oai.metadataformats."). The limitation here is that DSpace *must* be able to crosswalk (i.e. translate) the metadata format into the DSpace intermediate metadata format (based on qualified dublin core). The way DSpace handles this sort of translation is via Crosswalks. Currently, DSpace does *not* have a Crosswalk for 'rfc1807' or 'marc' or 'etdms' (which are the other metadata formats offered by the OAI-PMH server you linked to). If you had a developer build such a crosswalk, then you could harvest from these metadata formats into DSpace. Out-of-the-box, DSpace 1.6 currently comes with the following crosswalks: * Dublin Core * Qualified Dublin Core * PREMIS * OAI-ORE * MODS (currently very basic) * XSLT-based (which allows you to build a custom XSLT to translate any XML-based format to DSpace metadata format) More information on DSpace Crosswalks is available in the DSpace 1.6.2 Docs: * http://www.dspace.org/1_6_2Documentation/ch02.html#N10257 * http://www.dspace.org/1_6_2Documentation/ch05.html#N13059 More information on the OAI Harvesting configurations is also in the DSpace 1.6.2 Docs: http://www.dspace.org/1_6_2Documentation/ch05.html#N14BE2 Hopefully that clarifies things a bit, - Tim On 7/20/2010 6:27 AM, Ricardo Borillo wrote: > Hi all, > > I'm harvesting metadata in a collection through the new OAI collection > harvester delivered with DSpace 1.6.1. > > The public address is: > > http://www.tdx.cesca.es/TDX_UJI/NDLTD-OAI/oai.pl > > This remote service offers several metadata formats: > > http://www.tdx.cesca.es/TDX_UJI/NDLTD-OAI/oai.pl?verb=ListMetadataFormats > > When i retrieve a list of recods with the "metadataPrefix" oai_dc, i > get a set of information that is usefull, but not offers all the > information that i want. > If i query with "metadataPrefix" oai_rfc1807, i manage to get the > original URL of the remote item (field other_access). > > Is there any way to instruct the OAI harvester to run using a custom > metadataPrefix different from oai_dc? > > Thanks!!! > > --- > Regards, > ==================================== > Ricardo Borillo Domenech > http://xml-utils.com / http://twitter.com/borillo > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Dspace-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-general ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
