As one of the last steps in completing the migration to new LibraryWeb, LSO implemented the automatic redirection of users from old LibraryWeb pages to corresponding new LibraryWeb pages using two separate approaches: "directory-level redirects" and "file-level redirects".

In most cases, directory-level redirects send users to the new version of the page they requested and the process is completely invisible. If a user requests a page that does not exist, they are directed to an informational page allowing them to connect to the appropriate library or section homepage, or use new LibraryWeb navigation tools to locate the page they are seeking. Redirection to the informational page requires a the file named "error.404.html" be present in the appropriate directory. Do not delete this file!

In a few instances, file-level rather than directory-level redirects were used. This technique was employed when directory-level redirects would have interfered with access to active files in the old directory, or when the relocation of particular pages needed to be highlighted.

Directory-Level Redirects:  This approach is implemented on the server via special .htaccess file commands and automatically forwards all queries from the old directory to the specified new directory.

File-Level Redirects:  This technique executes on the client and is used on a file-by-file basis, e.g., if it is considered important to convey the new URL directly to the user. File-level redirects are accomplished using the "meta refresh" command, which can display a page to the user for a specified number of seconds and then automatically forward the user to a different page.

Keep in mind that directory and file level redirects are mutually exclusive. If you choose to have one file-level redirect in a directory, all pages in that directory must be handled via file-level redirects.