Registry harvest trigger

[Markus Demleitner]

Dear Registry WG,

If you've ever sat with someone just publishing a new service, you
will probably know the anticlimactic moment when you have to say
"Well, wait for a day and your service will show up in the registry",
and then you can actually do <whatever nice things you showed them
before with registered services>.

At least for the searchable registry at dc.g-vo.org (which is
reg.g-vo.org and hence TOPCAT's and pyVO's default most of the time)
there's now a remedy: The Harvest Trigger Service at
<https://dc.zah.uni-heidelberg.de/rr/q/harvtrig/form>.
There, you can paste your publishing registry's ivoid to trigger an
immediate (incremental) harvest of your publishing registry.  For
when reg.g-vo.org does not know a new publishing registry, you can
make it update its internal list of registries by pasting in the
RofRs id.

I'd be grateful if interested people could play around with the thing
a bit to see which traps I have missed; I don't think I'll make it
terribly much prettier (it's deep infrastructure, after all).  But an
interesting question certainly is also where to document such a
thing so people can find the URI when they're holding peoples hands
while they publish their data.

If there's time in our session in Bologna, I will give a brief to
talk on this there, so that may also be an opportunity to give
feedback.

Thanks,

            Markus