You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<OAI-PMHxmlns="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>
<requestverb="ListSets">https://oscardepl.wmo.int:443/oai/provider</request>
<errorcode="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.
The text was updated successfully, but these errors were encountered:
Running pyoscar's harvesting functionality (connecting to the OSCAR/Surface OAI endpoint) yields the following error:
Running a rudimentary query such as https://oscardepl.wmo.int/oai/provider?verb=ListSets yields the following error as well:
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.
The text was updated successfully, but these errors were encountered: