The prerequisite to using Fetch to transfer files is that you install and configure it with the correct preferences settings.
There is a separate version of these instructions for people building personal sites on the people2 server; the following instructions cover all of OIT's static-page servers:
After installing and configuring Fetch, start it; if already started, select "New Connection" from the File menu.
In the resulting dialog box:
as shown in the yellow-shaded region of the illustration, below:
for pages seen at www.ohio.edu/people/, specify host "people2.ohio.edu" (do not specify the host as "www.ohio.edu" or "www.ohiou.edu": those are different machines);
for pages seen on the staging server, specify host "wws2.ohio.edu" (do not specify the host as "www.ohio.edu" or "www.ohiou.edu": those are different machines);
for pages seen on the production server, specify host "ww2.ohio.edu" (do not specify the host as "www.ohio.edu" or "www.ohiou.edu": those are different machines);
for pages seen on OAK, specify host "oak.cats.ohiou.edu";
your Ohio ID (formerly called, "OAK login ID") as the username, in the red-shaded region, below -- without the "@ohio.edu" or quotes;
connect using SFTP, as shown in the purple-shaded region, below; and
your own password, in the green-shaded region, below.
Leave the "initial folder" and "port" fields blank, if those extra choices are displayed.
Click on "Connect" to make the connection.
The first time you connect to a server, you may be asked to confirm its identity. That stores information about the server in the Mac OS's "known hosts" file.
If the server configuration changes, the conflict between the stored and new information will prevent Fetch from connecting, generating an error message that provides few or no clues as to the true cause ("SFTP connection to 'ww2.ohio.edu' could not be opened because the connection to the SFTP server could not be established or was lost."). You can fix this problem:
click on Fetch's "Help" menu and choose "Fetch Help";
type "known hosts" in the "Search" field at the upper-right and wait briefly;
click on the line "'RSA host key differs' warning" (even though you may well not have received that particular warning), and follow the instructions there.
If you decide to delete the known hosts file, the primary consequence will simply be having to reconfirm each new host the first time that you connect to it afterwards.
When the connection is made, you will see in the main portion of the Fetch window a list that depends on the server (the colored circles highlight features that are discussed following the illustration):
for people2.ohio.edu, you will see a list of all the folders for people with public pages in http://www.ohio.edu/people/.
If you want to work on your public pages, then scroll down, as needed, to find the folder whose name matches your Ohio ID; and double-click on that folder.
If you want to work on your secure pages, then
click on the "Path" tool near the left end of the toolbar across the top of the Fetch window (highlighted green, above), in order to navigate "out" or "up" two levels (to look at the contents of the "people2.ohio.edu" folder, where you will observe both the "public" and the "secure" folders);
open the "secure" folder by double-clicking on it;
open the "people" folder by double-clicking on it;
scroll down, as needed, to find the folder whose name matches your Ohio ID; and double-click on that folder.
for ww2 and wws2, you will see a list of all the other Front Door top-level (subsite) folders. Scroll down, as needed, to find your subsite's folder and double-click on that folder.
for OAK, your will see a list of the files and folders in your home directory. Find and double-click on the folder named, "public_html," for your public site, and on the folder named, "public_shtml," for your secure site.
If you are working on other pages that are published by the static-page production server, but which are seen by the world with URLs that do not contain "www.ohio.edu," then you will see all the Front Door top-level (subsite) folders. Click on the "Path" tool near the left end of the toolbar across the top of the Fetch window (highlighted green, above), in order to navigate to other drives and folders, according to the information provided when you were authorized to work on those pages (typically, come "up" or "out" one level, to "WebDocumentFolders," and then double-click on the folder whose name matches your server).
Continue to navigate in your directories on the server in the main portion of the Fetch window, with the usual Macintosh techniques, until you are looking at the files that are already in the directory where you want to place the new file.
You can go to "outer" folders in the current path by using the "Path" button on the tool bar (highlighted green, above).
You can go directly to recently visited folders using the "Recent" button on the tool bar across the top of the Fetch window (immediately to the right of the "Path" button).
Decide whether the file should be transferred in text or binary mode. If the file has a conventional name for its type, then the "automatic" mode is likely to choose correctly between text and binary operation.
There are two ways to perform the file transfer:
Drag and drop: open a Finder window to the point where you can see the file or folder you want to transfer, and then use the mouse to drag the file or folder from your Finder window into the Fetch window (or vice versa, for downloading). This is usable only if you want an automatic-mode transfer (by far the most common situation).
Toolbar: click on the "Put" button on the tool bar to initiate the file transfer. In the resulting dialog box, navigate on your Mac's disk drive until you have selected the file you want to transfer. Observe that the lower portion of the dialog includes a "Format" pop-up, which defaults to "Automatic"; if you need to, you can force a text mode transfer by selecting "text," or a binary mode transfer by selecting "Raw data."
Verify that no semicolon (";") is included within the filename. If there is a semicolon, cancel, rename the file on the hard drive, and then go back to Fetch and click on the "Put" button again.
Double-click on that file or single-click on the file and then single-click on the "Put" button at the lower right to perform the upload. Wiggle the mouse and observe the pointer displayed as a running dog. Wait for the transfer to complete.
If you attempt to transfer a file that is bigger than your available free space, the server will refuse to accept the full file. On ww2, wws2, and people2, the part of the file that used up your available space will be left on the server, and Fetch will display an error message that identifies the lack of available space as the cause of the problem. You will have to manually delete the file-fragment to prevent people wasting time downloading the useless file.
If you need to change the name of a file after uploading it, click on the "Refresh" button on the toolbar (highlighted brown, above), then click on the file whose name you want to modify, then click on the "Get Info" button on the toolbar (highlighted blue, above).
You can adjust the widths of the columns by putting your mouse over their boundaries (highlighted gold, above); the mouse pointer changes when you are over the boundary. Then click and drag to the left or right.
When done transferring files, choose "Quit" from the Fetch menu.
Alternatives to explore include:
Creating Fetch "Shortcuts" to the staging, production, or people2 servers, which you can select using the heart tool icon to the right of the "Hostname" field when making a new connection. You can identify one shortcut as the default, pre-selected when you start Fetch.