- Help & Support
- IDs & Accounts
- Tech Depot
- Networks / Telephones
- Academic Services
- Information Security
- Web Services
- OIT Projects
- About OIT
The OAK system (which used to publish personal pages) has been retired and decommissioned.
This page addresses working with pages on the new place for personal pages — www.ohio.edu/people/ (also known as "people2") — there are separate instructions for migrating your old pages from OAK to www.ohio.edu/people/.
This page includes both an overview and also links to more detailed information.
See both the links immediately to the right (which jump down to specific parts of this page), and also the links in the lower block on the left (which take you to other pages).
For brevity, we will use "people2" to refer to the server to which you upload your personal pages. People2 is not the server used for organizational pages or academic and administrative departmental pages, even though the world sees them all as part of www.ohio.edu, the Front Door server.
The people2 server publishes personal pages of current students, current employees, retirees, and — for a limited duration after they leave Ohio University — former students (including alumni) and other former employees. You may not be able to modify your pages during the grace period after you are no longer eligible before your old files are deleted from the server.
On the people2 server, there are separate folders for the public and the secure subsites, within each of which there is a folder named, "people," and within those folders there is a folder for each person. The file locations on people2 are summarized in the following illustration:
If your primary personal home page is on any other server, we do encourage you to go through the process outlined here (on people2), creating a simple home page named index.html that contains a link to your primary home page.
Personal pages fall into two categories: those that are under the control of the individual, and those that are not. If in doubt about which category any of your pages falls into, please contact University Communications and Marketing for clarification and guidance.
If an employee's personal site includes work-related information whose content is not under the control of that employee (i.e., if the content is the result of agreement between the employee and others, or if someone else is in a position to tell the employee what to put on the page -- e.g., instructional materials that a faculty member maintains for use by multiple instructors), then those pages are generally official, should be marked at the bottom of the page as being copyright by Ohio University, and should include the Ohio University logo signature graphic in the upper-left corner. If that is done, then both the logo graphic and the words, "Ohio University," in the copyright statement should be linked to the Front Door, http://www.ohio.edu/.
All personal pages that are under the control of the individual are unofficial, must not assert copyright by Ohio University, and must not use any official logo graphics, unless specific permission has been granted (e.g., by University Communications and Marketing for any variation of the Cutler Hall woodcut, or by Intercollegiate Athletics for the Attack Cat). It is entirely appropriate for any personal page, and especially appropriate for your home page, to have a reciprocal link to the Front Door. See the "Rules" section of http://www.ohio.edu/sorgs/ for the detailed specifications for reciprocal links to the Front Door. Those specifications apply to all categories of pages.
The first step, normally done one time only, is to create your personal subdirectories ("home folders"), one for public and one for secure pages on people2, and then to apply the appropriate security settings. You will not be able to connect by SFTP to transfer your files, as documented in the next section, until after you have completed this step.
A separate page provides the step-by-step instructions to accomplish this task.
You are free to use whatever software you prefer to create your web site files on your personal computer. You may edit the HTML directly (e.g., with TextEdit on a Macintosh or Notepad on Windows); you may choose to "save as HTML" from a general word-processor or page layout package; or you may use a commercial web site authoring tool (e.g., iWeb on Macintosh or Adobe Dreamweaver on Windows or Macintosh).
Once you have prepared your site files, you should proofread them from your disk drive, using at least one regular browser, before you transfer them to the server for others to see.
There are three prerequisites to transferring your files according to the instructions below:
You must have SFTP software installed and configured with the correct preferences settings, as described under the appropriate "Install" link to the left.
Fetch is available online at no cost as described on http://www.ohio.edu/oit/webservices/people/fetchinstall.cfm.
FileZilla is also available online at no cost as described on http://www.ohio.edu/oit/webservices/people/filezillainstall.cfm.
We have no intention of breaking any other SFTP software, but Fetch and FileZilla work and are free, so if you use any others, you are on your own.
You must have created your public and secure home folders, as described under the "Provisioning Steps" link to the left.
You must have your web site files in place on your personal computer. If you had an old personal site on OAK, but don't have those files on your personal computer, contact firstname.lastname@example.org: we may have archived a copy before OAK was decommissioned.
Once all three of those are done, then you can transfer your web files to people2 by Secure FTP:
Connect to people2.ohio.edu with SFTP, using your own Ohio ID (what was formerly called your "OAK ID" or your "OAK login ID") and password; you must have changed your password since October 1, 2007.
The full step-by-step instructions for using Fetch do apply to pages published through people2.
The full step-by-step instructions for using FileZilla do apply to pages published through people2.
Both sets of full step-by-step instructions include more detail and specifics to supplement the outline instructions in steps 2 through 5, immediately below.
If you are using some other SFTP software (e.g., using a Linux desktop system, or using the internal uploading features of Dreamweaver), then it will be useful to know that the server's full specification for the standard default location after connecting is
Some software may require that you include the final slash, other software may require that you omit the final slash.
You will be in the "people" folder inside the "public" folder, and will see an alphabetically sorted list of the Ohio ID-named folders for the people who are already establishing their public personal subsites.
If you want to work on your secure (password-protected) subsite, then:
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;
open the "people" folder that is inside the "secure" folder;
observe the sorted list of Ohio ID-named folders for the people who are already establishing their secure personal subsites.
If you are using some other SFTP software (e.g., using a Linux desktop system, or using the internal uploading features of Dreamweaver), then it will be useful to know that the server's full specification for that location is
Some software may require that you include the final slash, other software may require that you omit the final slash.
See also the discussion of Restricting Access, below.
Scroll down to the folder whose name is your Ohio ID.
Open your folder and get to work.
If you attempt to upload a file that would exceed your disk space usage quota on the server, the server will refuse to accept the full file, but may well accept part of it. Either way, your SFTP software will display one or more error messages. Those messages differ among the various SFTP packages, so they are documented in the step-by-step instructions, linked in step 1, above, not here. A failed attempt to upload a folder full of files may create a folder with multiple partial files. You should delete any incomplete files as the first step of your recovery from this problem, to ensure that no one invests time (and network bandwidth) downloading broken files. When disk quota has been exceeded, file deletion may well be unusually slow.
You will be notified by e-mail when you reach your disk space quota, but of course that will arrive a few minutes later, so it will just confirm the nature of the problem you will already have seen in your SFTP session.
The disk space quota is enforced for each top-level folder. Thus, if you are authorized to work on more than one subsite (e.g., on your own pages and also on someone else's pages — as an assistant pagemaster), the files you upload for one subsite will count against the disk quota for that subsite only. Working as an assistant pagemaster for someone else's subsite will not reduce the space available to you for your own pages.
Disk space on the server is not free; furthermore, maintaining accurate backup copies of the data for disaster recovery requires equipment and labor. That said, the primary value of disk quotas is to prevent one person's broken SFTP process from consuming the entire drive, blocking everyone's updates. If you need more disk space, please let us know. There may later be a self-service application to deal with such requests; if so, if will be linked from here. In the meantime, we will deal with such requests manually, so please let us know by e-mail to email@example.com.
If you were planning to use your personal web space to share large files with collaborators, please be aware that OIT also offers a service specifically designed with this need in mind: Filelocker.
Once your files are in place on people2, they will be visible to the world with URLs similar to
where your own Ohio ID will be between the "people/" and the following slash. See the section, "Restricting Access to Your Secure Web Pages," below, for a discussion of the URL for your secure pages.
The first time you upload files to people2, you should promptly look at them with your browser, to confirm that they are intact. Be sure to look at a web page that contains an image that is yours, and be sure to scroll all the way down to the bottom of the web page; if both HTML and image files uploaded correctly, it is very likely that all files uploaded correctly.
Any folder in the /people/ subsite, including your home folder, that does not contain a file named, "index.html," nor one named, "index.htm," will display a server-generated list of links to every file and folder that it does contain; see, for example http://www.ohio.edu/people/, itself. When we provision your public and secure home folders, we do not place a generic index.html file into either of those folders. This makes it simpler for people with carefully chosen file names to just upload their files for people to see. Not linking to a file doesn't conceal it — unless you also ensure that the folder contains its own index page. Furthermore, such "security by obscurity" doesn't prevent people from seeing any file on your public site: if they somehow learn or guess the filename and type in the URL, the server will show it.
As soon as you are satisfied with your site on people2, you should make it easier for others to find it.
A separate page provides step-by-step instructions to accomplish this task.
You can restrict access to your secure Web pages, permitting only those people whom you authorize to see your pages.
This feature is now activated on the people2 server; there are no known problems; but please do confirm that the restrictions you intend are working correctly, and report any problems you encounter.
The details are in http://www.ohio.edu/oit/webservices/people/accesscontrolsteps.cfm.
If you want to authorize one or more other people to update your personal web presence (e.g., teaching assistants working with a professor's online instructional materials), please do not tell them your password! Instead, let us know the details: we have configured the people2 server so that we can readily add and remove assistant pagemasters for each person's subsite. We may later have a self-service application that you would use for this purpose (if so, it will be linked from here), but for now we will be doing these changes manually, so just send an e-mail to firstname.lastname@example.org.