 |
 |
On Aug 30, 2012, at 2:17 PM, John A. Kunze wrote: > If you run Apache server at the old location, and the original links and > new links obey one or a few regular patterns, you could use one or a few > RedirectMatch directives. > > If there are few patterns, you could use a big enumerated list of simple > Redirect directives. An ordinary Apache server can easily be loaded with > a million directives; a little slow on 'restart', but very short redirect > times when it comes up. If you need more than that, you could look into > installing a noid resolver. (google "CPAN noid") Yet another alternative in Apache when you're dealing with a larger number of items to redirect (and it's not simple directories moving about) is mod_rewrite's RewriteMap: http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritemap -Joe > --- On Thu, 30 Aug 2012, Pottinger, Hardy J. wrote: >> Hi, we're in the process of migrating an existing digital library to a new >> platform, and we want to ensure that old URLs continue to resolve to the >> items in the new location. The new digital library will be built on >> Islandora, and I am pretty sure we can just map old URLs to new ones >> within Fedora Commons. But, in case we run into trouble, I was wondering >> if anyone might have some experience with an application that's more >> specific to our use case? Or, heck, if you have already migrated from a >> DLXS-based digital library to an Islandora-based digital library, and have >> already sorted out how to handle redirects, I'd love to hear from you. >> Thanks! >> >> -- >> HARDY POTTINGER <[log in to unmask]> >> University of Missouri Library Systems >> http://lso.umsystem.edu/~pottingerhj/ >> https://MOspace.umsystem.edu/ >> "Debug only code. Comments lie." >>