[ckan-dev] Feature: new system checkin / status API

Mon May 9 09:20:42 UTC 2011

On 9 May 2011 10:08, William Waites <ww at styx.org> wrote:
> I think this is way too complicated.
>
> Just take some contact information from the config, perhaps
> distinguishing between site owner and site maintainer, and implement
> an API call that makes this information, together with software
> version, available.

That's basically what I'm saying, but with a check in too.  Maybe I
was too wordy, but that's what I mean :)

A registry "server" can just be a page that gets logged as a web page
hit in an apache log file, 5 mins work.  The other stuff is just stuff
we could do in the future.

Without a checkin, we still have to maintain lists manually -- which
IMO doesn't work very well at the moment.

> There is already a ticket for this

Can't find it -- what's the number?

Thanks

Seb

>
> ] Hi,
> ]
> ] For various reasons it's useful and/or important to have a list of
> ] installed CKANs and preferably an admin contact for it too.
> ]
> ] I propose a new config flag "report_existence" which when enabled,
> ] pings a central CKAN server to register itself.  It should have some
> ] kind of privacy text associated with it to clearly state what is
> ] reported if set.  The basic registration process would register the
> ] site admin email address, the site name, the site domain name, and the
> ] reporting IP address (in case they've set up the site domain name
> ] wrongly).
> ]
> ] An API call would allow us to check the health of the system, update
> ] site name, domain, and admin contact at regular intervals.
> ]
> ] We would also write a simple central registry which lists all systems,
> ] and perhaps adds some interesting stats about the systems taken from
> ] their APIs.  When the registry can't contact a site, it should email
> ] the administrator and ask them to either click on a link to remove the
> ] site from the registry, or update the site config file to correct it.
> ]
> ] We will need to think what to do for existing systems when they are
> ] upgraded, w.r.t. privacy implications.  Perhaps fire off an email to
> ] the administrator telling them that their site has checked in with the
> ] registry, and telling them how to opt out if they like.
> ]
> ] Finally, the central registry should probably have a way of manually
> ] adding extra systems that aren't checking in because they've not been
> ] upgraded.
> ]
> ] How does that sound?  Pending full agreement about CEPs, I will write
> ] up a seb-CEP as a test, if we think this is a good idea :)
> ]
> ] Seb
> ]
> ] _______________________________________________
> ] ckan-dev mailing list
> ] ckan-dev at lists.okfn.org
> ] http://lists.okfn.org/mailman/listinfo/ckan-dev
>
> --
> William Waites                <mailto:ww at styx.org>
> http://river.styx.org/ww/        <sip:ww at styx.org>
> F4B3 39BF E775 CF42 0BAB  3DF0 BE40 A6DF B06F FD45
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>

-- 
skype: seb.bacon
mobile: 07790 939224
land: 01531 671074
web: http://baconconsulting.co.uk