The metadata on the registry is quite often out of date, because the harvester that runs inside of CKAN doesn’t work very well. It would be useful to instead have a harvester that runs outside of CKAN, and then updates metadata via the CKAN API.
Proposal
The first step is to flag all the instances where the metadata is currently wrong. This could be done using iatikit. Not sure how/what the interface should be yet, though. Maybe just Flask RESTful or something like that.
Rationale
The metadata on the registry is quite often out of date, because the harvester that runs inside of CKAN doesn’t work very well. It would be useful to instead have a harvester that runs outside of CKAN, and then updates metadata via the CKAN API.
Proposal
The first step is to flag all the instances where the metadata is currently wrong. This could be done using iatikit. Not sure how/what the interface should be yet, though. Maybe just Flask RESTful or something like that.