Testing IATI Regsitry Publishing

We’re doing some user testing within the test Aidstream Implementation we have setup at http://aidstream.zimmermanzimmerman.com/ and would like to try out the publishing process to the registry.

Obviously we don’t want to start polluting the registry with our test data, so was wondering if you have a solution in place to be able to post to a test registry site which will give us the right responses back without it all being live?

(Let me know if this isn’t clear - not sure if I am describing the problem correctly).

Yes, this makes sense, and I think is something other publishers have asked about.

We have a test copy of the registry, which is used to test upgrades to the CKAN software - http://iati2.staging.ckanhosted.com/ . It may be possible to use this, or we may want to set up another test. The other alternative is to set up a copy of CKAN + the IATI extension locally. However, this isn’t especially straightforward, so we will probably look into providing a test instance for publishers. @stevieflow probably has more to say about this.

Some publishers have also suggested having a test copy of the datastore/dashboard which uses such a dev copy of the registry, to allow publishers to test the data using the datastore/dashboard without having to first make it live. This is more difficult, but is something we may also consider.

Yes - afaik the copy of the Registry at http://iati2.staging.ckanhosted.com/ can be used as it stands, Please bear in mind that this is not fully synched with the live Registry (in terms of account data) and may get wiped without notice. However, in terms of software (including the API), it is to the latest version of the live IATI CKAN.

However, I will confirm this with the OKF CKAN team, just in case there are any restrictions.

Thanks guys - I think this should work for us. Will let you know if we hit on any blockers :smile:

From Adria at OKF:

The staging site at http://iati2.staging.ckanhosted.com/
is running the latest code (but the database is using is an old one,
meaning that there aren’t all the publishers and datasets).

People is of course welcome to use it, the only thing is that we have
other staging CKAN instances running on that server so if people testing
against it affects the performance of the other sites we may need to
put some limits in place. I don’t think that will be an issue though.

HI guys,

We have just added a publisher at: http://iati2.staging.ckanhosted.com/user/activity/aidstream-zz

So

publisher: aidstream-zz
API Key: (deleted)

We have verified a single activity in our aidstream setup, but not showing up yet.

@steven, do you need to verify this aidstream-zz publisher?

please advise,

Siem

Hi @siemvaessen

I cant see any “application” for publisher/aidstream-zz - you point to a user with that.

I think you may have made that classic (aka common!) error in terms of not completing this form for a new publisher:

http://iati2.staging.ckanhosted.com/publisher/new

The Registry requires people to create a user and then a publisher (which is approved).

Thanks

Steven