Here are a few screenshots to give a taste of what it is like to use our new Django app to manage a set of URI redirections:

Administration Overview:

For any URI-Scheme: Basically, the Django app allows you to control a listing of MIME Media Types, and Rewrite rules.

USGIN URI-Scheme: The same basic structure, but the USGIN-specific app allows you to control a listing of Name Authorities and Resource Types, as described in this post.

Listing of Rewrite Rules: A nice overview of what rewrite rules you have in place, and a mechanism for searching for the one you might need to adjust.

Creation of a Rewrite Rule:

For a Generic URI scheme: Create a label and description for the rule, write a regular expression for the capture of a particular pattern, and specify redirect-to URIs for whatever content-types are available. Regular expressions are parsed in Python, and should follow syntax guidelines outlined here. Note that the regular expression ignores the server name (http://<server name>/) and does not begin with a forward-slash. Also, redirect-to URLs can be written as they are in Apache's mod_rewrite, with $1 indicating the first capture block, $2 the second, and so on.

USGIN URI Scheme: Similar to above, but implements picklists to control selection of name authorities and resource types. The entered regular expression is what gets captured after the name authority and resource type, and need not include ^ and $ characters indicating the start and end of an expression.

Generic representation of a URI: Django generates a "generic" html representation of each URI-matching rule that relays the information about that rule. This becomes a sort of default representation of a non-information resource that may not have any other web-accessible representation.