Setting up a registry

Simon O'Toole simon.otoole at
Fri Nov 10 02:38:45 CET 2017

Hi everyone,

Wonderful – thank you!

These ideas will get us started at least :)

We are interested in a python based implementation, so I will look at pyoai.


> On 10 Nov 2017, at 3:09 AM, Theresa Dower <dower at> wrote:
> Hello,
> As for available registry implementations, the STScI Registry system is also open, but, having been developed for a Windows environment, is based on IIS web server and .NET (it's in C#  and uses aspx) and lightly tied to MSSQL server. While STScI runs it as a full searchable registry, there are subsystems that can stand alone just for the publishing registry capabilities and ingesting raw XML resources. I expect we'll continue being the only folks who run it but for the sake of listing options it is out there.
> We're also capable of hosting a small number of resources from outside institutions that don't want to run a full publishing registry. These are managed through webforms once an account and authority record have been set up.
> --Theresa
> From: registry-bounces at <registry-bounces at> on behalf of Markus Demleitner <msdemlei at>
> Sent: Thursday, November 9, 2017 3:41:33 AM
> To: registry at
> Subject: Re: Setting up a registry
> Hi Simon,
> On Thu, Nov 09, 2017 at 12:57:10PM +1100, Simon O'Toole wrote:
> > We are interested in setting up a publishing registry for IVOA
> > services for our new Data Central system; we have a TAP service and
> > will soon have several Simple Cone Search services and an Simple
> > Image Access service, plus more services in the pipeline.
> Ah -- we should really have a nice and concise page with a couple of
> standard answers to this and related questions.
> > How do we go about this? We don't want to be re-inventing the
> > wheel, so any assistance or pointers would be most welcome!
> OAI-PMH as such isn't a terribly complicated protocol, but producing
> the records themselves programatically can be a bit involved
> depending on how you currently keep your metadata.  So, my
> recommendation is to start with that (some publication tools already
> do that for you, but that isn't likely to be terribly helpful if
> you've written your own software).
> There's a short introduction on
> <>
> -- feedback on what additional information would be helpful is highly
> welcome.
> To see if you got it roughly right, use a normal XML schema validator
> (if you give schemaLocation).  You can also use purx for that if you
> put your piece of VOResource on the web.
> purx, <>, in addition is an
> alternative to running a full-fledged publishing registry if you
> forsee that you'll only have a dozen or so resources.  Have a look at
> the docs if you're interested.
> As to speaking OAI-PMH yourself, there are several generic tools out
> there (e.g., <>) that may be
> helpful in setting up a complete registry.  I'm afraid I can't be
> more specific than that since I've never used any of those -- perhaps
> someone else can chime in?
> There is furthermore some code around for more VO-specific OAI-PMH.
> DaCHS has a python implementation that, however, is pretty closely
> integrated with both twisted/nevow and DaCHS' metadata management;
> take that away and the rest is almost trivial.
> What else exists?  CDS, CADC, IRSA, HEASARC, etc: If you have
> anything public, please speak up!  I'll collect the responses into
> the "RegisterYourServices" page I'd like to create.
>         -- Markus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the registry mailing list