search

wmo-im / wmdr

WIGOS Metadata Standard: UML model and schemas
8 stars 7 forks source link

OSCAR/Surface OAI endpoint errors #50

Open tomkralidis opened 2 years ago

tomkralidis commented 2 years ago

Running pyoscar's harvesting functionality (connecting to the OSCAR/Surface OAI endpoint) yields the following error:

(pyoscar) (base) tomkralidis@aruba:~/Dev/pyoscar/pyoscar$ pyoscar harvest -d iii --verbosity DEBUG
DEBUG:pyoscar:Setting URL
Harvesting records
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): oscardepl.wmo.int:443
DEBUG:urllib3.connectionpool:https://oscardepl.wmo.int:443 "GET /oai/provider?verb=ListRecords&metadataPrefix=wmdr HTTP/1.1" 200 355
DEBUG:pyoscar:Request: https://oscardepl.wmo.int/oai/provider?verb=ListRecords&metadataPrefix=wmdr
DEBUG:pyoscar:Response: 200
DEBUG:pyoscar:Raw XML response:
<?xml version="1.0" encoding="UTF-8" ?>

<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
 http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
<responseDate>2022-07-04T23:28:03Z</responseDate>
<request verb="ListRecords" metadataPrefix="wmdr">https://oscardepl.wmo.int:443/oai/provider</request>
    <error code="cannotDisseminateFormat">This repository has no items available in format &#39;wmdr&#39;</error>

</OAI-PMH>
DEBUG:pyoscar:stopping harvesting

Running a rudimentary query such as https://oscardepl.wmo.int/oai/provider?verb=ListSets yields the following error as well:

<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
 http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
<responseDate>2022-07-04T23:45:27Z</responseDate>
<request verb="ListSets">https://oscardepl.wmo.int:443/oai/provider</request>
    <error code="noSetHierarchy">This repository does not currently have any sets defined</error>

</OAI-PMH>

Note that these issues are found in both prod and depl.

Any ideas on the above issues? At first glance, the OAI endpoint looks to be a default install which needs to be configured.

In the MSC case, we would like to run a periodic harvest of station metadata for our data assimilation/production workflows.

amilan17 commented 2 years ago

@tomkralidis -- this team/repository doesn't manage OSCAR/Surface. I believe that you can register an issue here: https://oscar.wmo.int/surface/#/feedback.