<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Jorge,</p>
<p><br>
</p>
<p>I reingested your records for the STScI registry; both now appear in our programmatic interfaces (including RegTAP), and should show up in the keyword search page when it updates its index overnight. I haven't yet fully investigated the harvester history
for why <span><span>ivo://iacvo/PSZ1y2 did not show up before, and I'll keep looking into it. Thanks for letting us know.</span></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span>--Theresa Dower</span></span></p>
<p><span><span>Archives, STScI</span></span></p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> registry-bounces@ivoa.net <registry-bounces@ivoa.net> on behalf of Jorge A. Pérez Prieto <japp@iac.es><br>
<b>Sent:</b> Tuesday, May 28, 2019 5:23:55 AM<br>
<b>To:</b> Kostandin Vrioni; registry@ivoa.net; esavo.registry@sciops.esa.int<br>
<b>Subject:</b> Re: About VO registry</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Dear Markus and Costas,<br>
<br>
great! thanks a lot, now they appear in the GAVO directory and pyVO. <br>
Nevertheless, they still are not shown in the NVO and MAST directories <br>
or Aladin 10 (they do in Aladin 9); it's not critical but bit strange.<br>
<br>
Regards and thanks again,<br>
Jorge<br>
<br>
O 24/05/19 ás 10:26, Markus Demleitner escribiu:<br>
> Dear Jorge, hi Costas,<br>
><br>
> On Thu, May 23, 2019 at 05:35:31PM +0300, Kostandin Vrioni wrote:<br>
>> I have been using the Euro-VO Registry for many years to register<br>
>> some VO services of my institution (IAC, Tenerife, Spain) and I am<br>
>> very happy the application, so many thanks for your work.<br>
>> We are having an issue with the discovery of our services<br>
>> registered in the Euro-VO Registry and maybe you can help me.<br>
>> Although the services seems to work correctly, for example (SIAP):<br>
>> <br>
>> ivo://iacvo/IAC80<br>
>> ivo://iacvo/PSZ1y2<br>
>> I'm not been able to find them in most part of the VO discovery<br>
>> tools; I've tried these:<br>
> Interesting. Let's see: The OAI-PMH interface at the EuroVO Registry<br>
> actually delivers the record *now* when asked about it<br>
> (<a href="http://registry.euro-vo.org/oai.jsp?verb=GetRecord&metadataPrefix=ivo_vor&identifier=ivo://iacvo/IAC80">http://registry.euro-vo.org/oai.jsp?verb=GetRecord&metadataPrefix=ivo_vor&identifier=ivo://iacvo/IAC80</a>)<br>
> and even includes it when asked what changed when that record last<br>
> changed:<br>
> <a href="http://registry.euro-vo.org/oai.jsp?verb=ListRecords&metadataPrefix=ivo_vor&from=2018-12-21&until=2018-12-22&set=ivo_managed">
http://registry.euro-vo.org/oai.jsp?verb=ListRecords&metadataPrefix=ivo_vor&from=2018-12-21&until=2018-12-22&set=ivo_managed</a>.<br>
><br>
> Meanwhile, none of my registry mirrors had seen that record in what<br>
> they harvested over the last six month or so (which, of course, the<br>
> do for the Euro-VO publishing registry, too).<br>
><br>
> I didn't bring all that together and told the Heidelberg mirror to<br>
> just do a full re-harvest of the EuroVO publishing registry. And lo<br>
> and behold, the records are now there. They're now available in<br>
> TOPCAT (Aladin will take a bit longer, probably until tomorrow).<br>
><br>
> I can't quite say what happened (Theresa, who holds a lot more<br>
> history than I do, might be able to provide more insight), but I<br>
> suspect the records made it into the publishing registry quite a bit<br>
> after the datestamp and thus were lost in incremental harvesting.<br>
> The weak part of that theory is that the records are old enough to<br>
> have been part of the initial harvest. Why they were missing there I<br>
> really can't say.<br>
><br>
> Costas, I think the best way to fix the problem on all searchable<br>
> registries (without requiring their operators to do a full<br>
> re-harvest) would be to bump the datestamp on these (and perhaps<br>
> other records that may share their fate) to today. That way,<br>
> incremental harvesting will bring them back without further<br>
> intervention.<br>
><br>
> Thanks,<br>
><br>
> Markus<br>
---------------------------------------------------------------------------------------------<br>
ADVERTENCIA: Sobre la privacidad y cumplimiento de la Ley de Protección de Datos, acceda a
<a href="http://www.iac.es/disclaimer.php">http://www.iac.es/disclaimer.php</a><br>
WARNING: For more information on privacy and fulfilment of the Law concerning the Protection of Data, consult
<a href="http://www.iac.es/disclaimer.php?lang=en">http://www.iac.es/disclaimer.php?lang=en</a><br>
<br>
</div>
</span></font>
</body>
</html>