ckan / ckan/ideas

Redirects extension?

Open
#43 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
39
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Sometimes things change.

We all know this is a [Bad Thing](http://www.w3.org/Provider/Style/URI.html), but face it, these things happen in the Real World.

I'm wondering if it would be useful to have a simple CKAN extension,that when installed and enabled, lets admins of an instance/organization set up a redirection from OLD to NEW, with a choice/set of HTTP Status codes (and actions), 301, 303, 308, 410, 451, like Wordpress provide(s|d).

The extension should check OLD no longer exists, and NEW does.

There could be an impact on ckanext-qa, but there may not.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the proposed CKAN extension behavior and how CKAN represents existing resources or URLs. Define how admins and organizations configure OLD-to-NEW redirects, which HTTP status codes and actions are supported, and how OLD/NEW validation works. Check whether ckanext-qa is affected; the issue is done only when the scope and behavior are agreed.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.