Closed ryan-jacobs closed 2 years ago
The FOLIO leadership team discussed this and determined that we should actually be redirecting DLIR requests to catalog.crl.edu back to the old MilCat catalog-old.crl.edu while it is temporarily available. DLIR community leaders will also be reaching out to indivudal community members to inform them that the DLIR search features are temporary and will be going away soon.
When we take down catalog-old.crl.edu we could leverage this same redirect to point to an info page, but as long as catalog-old.crl.edu is available we can keep directing people to something useful.
The following should address DLIR scope references in both paths and query strings, directing the whole request unchanged to catalog-old.crl.edu:
# DLIR scopes temporarily redirect back to catalog-old.crl.edu. These are
# scopes 6-34 and 40-51. Note that these URLs are also case-sensitive.
RewriteRule (search~S(([6-9]|[12][0-9]|3[0-4])|(4[0-9]|5[01]))) http://catalog-old.crl.edu/$0 [R=301,L,QSA]
RewriteCond %{QUERY_STRING} (searchscope=(([6-9]|[12][0-9]|3[0-4])|(4[0-9]|5[01])))
RewriteRule .* http://catalog-old.crl.edu/$0 [R=301,L,QSA]
This rule has been tested in dev and moved to prod. This is instance-specific Apache conf, so no git-based deploy is needed. Closing.
We have setup numerous redirects to handle legacy traffic in #132. There are some cases that we can not handle because of a depend on legacy metadata that was not migrated. One such case is DLIR. DLIR scopes don’t have any representation in the new catalog so we don’t support any special routing for them.
Given that we do not intend to support those DLIR scopes in the new catalog I think it would be prudent if we put up an official notice as a dedicated page on catalog.crl.edu that explains this decision, and possibly offers a point of contact for related questions. We could then redirect all traffic for those old DLIR URL’s (things like http://catalog.crl.edu/search~S11, http://catalog-old.crl.edu/search~S15, etc.) to this explainer page.