[ivoa-rofr] Re: rofr.ivoa.net question

IVOA Registry of Registries ivoa-rofr at cfa.harvard.edu
Tue Jun 25 20:42:44 CEST 2019


Hi Patrick,

We have reharvested your registry's document so now the https endpoint is
registered.

The validation error is because the phase 1 OAI validation requires that
schema locations are specified in the document, where phases 2 and 3 use
schemas from the local RofR cache. This is the nature of the legacy third
party SW that is used in the phase 1 and we are working on changing it. In
the mean time if you want an error free validation you can change

  <ri:Resource xmlns:ri="http://www.ivoa.net/xml/RegistryInterface/v1.0"
xmlns:vg="http://www.ivoa.net/xml/VORegistry/v1.0" xmlns:vr="
http://www.ivoa.net/xml/VOResource/v1.0" xmlns:vs="
http://www.ivoa.net/xml/VODataService/v1.1" created="2011-12-09T14:24:09Z"
status="active" updated="2019-06-14T16:00:00Z" xsi:type="vg:Registry">

to

 <ri:Resource xmlns:ri="http://www.ivoa.net/xml/RegistryInterface/v1.0"
xmlns:vg="http://www.ivoa.net/xml/VORegistry/v1.0" xmlns:vr="
http://www.ivoa.net/xml/VOResource/v1.0" xmlns:vs="
http://www.ivoa.net/xml/VODataService/v1.1" created="2011-12-09T14:24:09Z"
status="active" updated="2019-06-14T16:00:00Z" xsi:type="vg:Registry"
xsi:schemaLocation="http://www.ivoa.net/xml/RegistryInterface/v1.0

http://www.ivoa.net/xml/RegistryInterface/v1.0
                                 http://www.ivoa.net/xml/VODataService/v1.1
                                 http://www.ivoa.net/xml/VODataService/v1.1
                                 http://www.ivoa.net/xml/VOResource/v1.0
                                 http://www.ivoa.net/xml/VOResource/v1.0
                                 http://www.ivoa.net/xml/VORegistry/v1.0
                                 http://www.ivoa.net/xml/VORegistry/v1.0">

Yulie


On Thu, Jun 20, 2019 at 3:21 PM Patrick Dowler <pdowler.cadc at gmail.com>
wrote:

> Hi Yulie,
>
> last Saturday I updated all records to add a setSpec element, plus updated
> all URLs to https, and updated timestamps. So a full reharvest would be
> useful I think.
>
> One thing: the validator reports two schema validation errors for
> verb=Identify that I cannot reproduce.
>
> URL: https://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/reg/oai
>
> --
> Patrick Dowler
> Canadian Astronomy Data Centre
> Victoria, BC, Canada
>
>
> On Tue, 18 Jun 2019 at 11:17, IVOA Registry of Registries <
> ivoa-rofr at cfa.harvard.edu> wrote:
>
>> Hi Patrick,
>>
>> When exactly did you update your registry?  The registry's record was
>> reharvested and updated in the RofR on April 19. At that time the accessURL
>> was still http and update date "2018-01-24".  For the record, all registry
>> records were updated at that time regardless of their validation status.
>> The current plan is to start reharvesting all records regularly and we are
>> working on setting this up.
>>
>> When I try to access your registry now either over http or https I am
>> getting the same results. It is not clear why access over http is failing
>> for the euro-VO but if needed we can reharvest  and update it in the RofR
>> again now before the next reharvest of all registries.
>>
>> Yulie
>>
>>
>> On Tue, Jun 18, 2019 at 3:43 AM Kostandin Vrioni <k_vrioni at neuropublic.gr>
>> wrote:
>>
>>> Dear Patrick,
>>>
>>> We had recently a telecon on the RofR resource update and validation
>>> process, please check the link for details:
>>> https://wiki.ivoa.net/twiki/bin/view/IVOA/RegistryTelecon2019A
>>>
>>> The problem I think is that we have 3 version of your Registry resource:
>>>
>>>    - In RofR:
>>>       - *URL:*
>>>       http://rofr.ivoa.net/cgi-bin/oai.pl?verb=GetRecord&metadataPrefix=ivo_vor&identifier=ivo://cadc.nrc.ca/registry
>>>
>>>       - *Updated attribute:* 2018-01-24
>>>       - *Harvest URL:*
>>>       http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/reg/oai
>>>    - In our registry:
>>>       - *URL:*
>>>       http://registry.euro-vo.org/oai.jsp?verb=GetRecord&metadataPrefix=ivo_vor&identifier=ivo://cadc.nrc.ca/registry
>>>       - *Updated attribute:* 2018-01-24
>>>       - *Harvest URL:*
>>>       http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/reg10/OAIHandlerv1_0
>>>    - In your registry:
>>>       - *URL:*
>>>       http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/reg/oai?verb=Identify
>>>       - *Updated attribute: *2019-06-14
>>>       - *Harvest URL:*
>>>       https://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/reg/oai
>>>
>>> Therefore:
>>>
>>>    1. Our registry version has a wrong *Harvest URL *therefore is not
>>>    updating your resource because it cannot reach the site at all.
>>>    2. Our registry is not updating your registry resource from RofR
>>>    because both has *Updated attribute*: 2018-01-24.
>>>    3. The RofR is not updating your registry resource because your
>>>    registry failed on RofR validation (see also the telecon notes)
>>>
>>>
>>> *Solution*:
>>>    I suggest you ask RofR for manual update of your resource and bypass
>>> the validation at least for this time.
>>>
>>>
>>> I remain at your disposal for any further information.
>>>
>>> Kind regards,
>>> Costas
>>>
>>> *Kostandin Vrioni* │ Senior Software Engineer
>>> *NEUROPUBLIC SA* │ 6 Methonis Str, Piraeus, 18545, Attica, Greece
>>> *Τ :* 210 4101010 – ext. 3882 │ *F :* 210 4101013 │ *W : *
>>> www.neuropublic.gr* | *www.gaiasense.gr
>>>
>>> [image: NEUROPUBLIC A.E.] <http://www.neuropublic.gr/>    [image:
>>> gaiasene] <http://www.gaiasense.gr/>
>>> *Information Technologies | Smart Farming Services   *
>>>
>>> *Join us in*[image: Facebook] <https://www.facebook.com/neuropublic>[image:
>>> Twitter] <https://twitter.com/neuropublic>[image: Linkedin]
>>> <https://www.linkedin.com/company/neuropublic-s-a-/>
>>>
>>>
>>>
>>> * From: * Patrick Dowler <pdowler.cadc at gmail.com>
>>> * To: * <registry at ivoa.net>
>>> * Sent: * 14/06/2019 9:34 PM
>>> * Subject: * rofr.ivoa.net question
>>>
>>>
>>> If I modify the records for my own registry internally an that is
>>> exposed via OAI publishing endpoint, is rofr.ivoa.net supposed to
>>> automatically pick that up? That is, does rofr periodically
>>> re-harvest/update registry records? Or are other harvesters expected to
>>> come to my OAI endpoint themselves?
>>>
>>> Awhile back I changed the accessURL for our registry from http to https
>>> and I did change the timestamps as well. Then yesterday I was trying to
>>> figure out why CADC services had disappeared from the GAVO registry....
>>> when I checked EuroVO registry it contained much older (2018-01-24) records
>>> than we are currently publishing (2019-04-05) for our registry itself.
>>> Costas
>>> says that EuroVO is comparing our registry record from rofr with the one
>>> it has and rofr has the 2018-01-24 record...
>>>
>>> Do I need to poke rofr somehow? Can I automate that?
>>>
>>> There was an issue where Identify returned an http URL which didn't
>>> match the https URL from ivo://cadc.nrc.ca/registry but that is fixed
>>> and timestamps updated.. maybe that is related.
>>>
>>> Aside: our registry is still a bit of a hack and fails OAI Validation -
>>> it does pass all IVOA and VOResource tests.
>>> --
>>> Patrick Dowler
>>> Canadian Astronomy Data Centre
>>> Victoria, BC, Canada
>>>
>>>
>>>
>>> Αποποίηση ευθυνών - Disclaimer <https://www.neuropublic.gr/disclaimer/>
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20190625/f92e237b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ae5d6232-13c1-435a-b90a-dd8a2d94202b.png
Type: image/png
Size: 1953 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20190625/f92e237b/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8ca7183d-9cf2-43f2-a832-b46f8f30011d.png
Type: image/png
Size: 1886 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20190625/f92e237b/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 61065366-0f7c-4c66-8246-48070accf1bf.png
Type: image/png
Size: 1890 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20190625/f92e237b/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ce94be0e-c886-4980-a87f-6bab347d546e.png
Type: image/png
Size: 6307 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20190625/f92e237b/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: f62db48c-4a68-4325-a86c-e791dd90136d.png
Type: image/png
Size: 4635 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20190625/f92e237b/attachment-0009.png>


More information about the registry mailing list