Upgrade Archiver extension

[avdata99]

Description

In the catalog-app we are using a fork of the official ckanext-archiver extension (on the datagov branch).

As a part of a plan to upgrade CKAN extensions in use, and in order to improve the way that we manage forks we need to upgrade this extension.

Acceptance Criteria

• When there's a new release upstream, we can get onto it in under an hour
• When there's a new release upstream, we see a notification in a Slack channel
• If the upstream maintainers don't already use versioning, there's an issue in their tracker requesting they do.
• If the upstream maintainers don't already have tests, there's an issue in their tracker requesting they add them.
• We have tests for this extension running in CI. Done here if we use upstream

Tasks

• Create a test environment with the catalog-app
• Test this extension
• Upstream do not use tags for versions, do not have a change log file and version is 2.0.0 since 4 years ago. Ask upstream for improve versioning: Done
• Measure the effort to move the catalog-app to this official archiver version.
• Check if the custom broken link functionality is required. If it is, look into pulling some, or all, of the GSA code related to this upstream.
• Check if the bulk update code is required. If it is, look into pulling some, or all, of the GSA code related to this upstream.

The official repo has tests and CI. It is an active repo.

Analysis & notes

There are 2 main differences between the GSA fork and upstream. The first is a custom implementation of displaying whether a link is broken, on the package page itself. This is something that’s listed as TODO upstream, so we might be able to use some of this code there. The second change is a custom bulk resource update function. Some of this might also be useful upstream.

Our fork is Ahead in 43 commits and behind 69 commits. These links show us the changes between our datagov branch and master at upstream.

Recommendations

We recommend to move to the community version.

[nickumia-reisys]

We are using the upstream version of archiver, but there are some issues with production,

• Re-integrate (QA | ARCHIVER | REPORT) extensions to catalog.data.gov #3957
• Create plan for Archiver/QA on Production #3986