theodi/open-data-certificate

Run against some portals on staging

Closed this issue · 9 comments

Add some portals here to test against.

If you're looking for CKAN portals to test, here's my top 3:

Or my full list. Note: they're not all CKAN portals.

Thanks @digitalWestie for testing the Australian portals.

I assume this was tested locally as I don't see the results on http://staging.certificates.theodi.org/en/datasets (which by the way isn't rendering fully for me).

What will be the approach for portal owners that harvest from other portals and encounter the data.sa.gov.au issue above? Should they run a collection of organisation based campaigns or just ignore the errors from a full run?

The data.sa.gov.au issue is in #1436, and is on the list to resolve - hopefully we can make it follow the proper links.

See #1442

But just as I pushed this up I realised, do we really want to include harvested datasets in these campaigns? Do we not want to run campaigns against a specific portal? Not just any that it comes across?

@digitalWestie No you don't want to include them. Just elegantly ignore them (that's what I meant in my last comment above).

To scan my whole portal and not get any errors due to harvested metadata, I would prefer that I just specify the portal (e.g. data.sa.gov.au) and the campaign intelligently ignores harvested metadata.

I'm not sure how you are determining what is harvested from elsewhere. My guess was by organisation, hence my question "Should they run a collection of organisation based campaigns [to avoid getting errors when running the campaign]?".

Hope that's clear - sorry.

So perhaps no need for #1436?

Can this be closed given #1442 ?