Hi Robert, I have some troubles very similar to what you had. So, how did you solve the problem...Now i´m using dspace version 5.5 trying to harvest 3 different geonetwork versions: 3.2.2 , 3.2.1 and 3.2.0
Try after try I reduced options to harvest geographic metadata using Dspace, so this is the issue: I am using Dspace v. 5.5 in linux ubuntu 16, all running well. I did some harvests in scientific journals in Mexico with good results using OAI protocol and Simple Dublin Core. RICA: http://www.revistascca.unam.mx/rica/index.php/rica <http://www.revistascca.unam.mx/atm/index.php/atm>Atmosfera : http://www.revistascca.unam.mx/atm/index.php/atm As far as i know , Geonetwork 3.x and Dspace use OAI protocol. But i can not extract info from Geonetwork using Dspace. I am very interested in extracting some geographic metadata from Geonetwork that use ISO 19139...I need metadata in Dublin Core. I was thinking if i must use a converter , some sintax tricks to send ISO 19139 strucuture to dublin core or may be a sequence of steps in and out of Geonetwork and Dspace. All suggestions are valuable, thanks in advance for your time and help. Luis Avalos. El martes, 25 de agosto de 2015, 16:37:16 (UTC-5), Robert Torgerson escribió: > > Greetings everyone, > > I have recently come across a problem with harvesting metadata from sites > running the open-source software Geonetwork. In the past, I have been able > to check a OAI provider by using their baseURL and querying > ListMetadataFormats such as: > http://www.fao.org/geonetwork/srv/en/main.home/oaipmh?verb=ListMetadataFormats > > Verifying that oai_dc is available, I have had little problem from other > sites gaining the metadata from these OAI providers. However, with > Geonetwork sites, I get an error message from my system along the lines of: > > The OAI server does not support this metadata format: > http://www.openarchives.org/OAI/2.0/oai_dc/ > > Exception: > org.dspace.harvest.OAIHarvester$HarvestingException: The OAI server does > not support this metadata format: > http://www.openarchives.org/OAI/2.0/oai_dc/ > at org.dspace.harvest.OAIHarvester.runHarvest(OAIHarvester.java:278) > > However, if you look at the query for metadata formats above, you will > notice that oai_dc is listed as a potential metadata format of the site. I > have noticed that there is one obvious difference between Geonetwork sites, > and the ones that I have had success in harvesting from, which is the > namespaces do not match in a query to ListMetadataFormats for oai_dc. > > Here is the oai_dc metadata listed from a registered OAI data provider: > <metadataFormat> > <metadataPrefix>oai_dc</metadataPrefix> > <schema>http://www.openarchives.org/OAI/2.0/oai_dc.xsd</schema> > <metadataNamespace>http://www.openarchives.org/OAI/2.0/oai_dc/ > </metadataNamespace> > </metadataFormat> > > And here is the oai_dc metadata listed from a Geonetwork site: > <metadataFormat> > <metadataPrefix>oai_dc</metadataPrefix> > <schema>http://www.openarchives.org/OAI/2.0/oai_dc.xsd</schema> > <metadataNamespace>http://www.openarchives.org/OAI/2.0/ > </metadataNamespace> > </metadataFormat> > > Could this namespace issue be the cause of the problems when trying to > harvest from Geonetwork sites? When I do a query on Records using the > metadata_prefix="oai_dc", I find that the records themselves are being > printed out as Dublin Core elements, but I'm not certain why DSpace seems > to think that it can't harvest from these sites? Am I missing something > fundamental about this problem? Has anyone ever run into this kind of > problem? > > Any help that you can provide would be greatly appreciated! > > Thanks, > > Bob Torgerson > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
