BulletinNotes-GH.html
Before the start of a new Bulletin cycle, the publishing location (FTP) to which the OU Bulletin site points
needs to be changed. That preserves the current Bulletin files on the production server as subsequent
publishes will then be made to the new location. This year’s files are in /local/htdocs/bulletin/2020-2021.
Last year’s files are in /local/htdocs/bulletin/2019-2020. Next year’s files will be in /local/htdocs/bulle-
tin/2021-2022.
Instruction (updating publishing path):
• Login into OU (www.binghamton.edu/bulletin/ou/)
• Navigate to Setup (top navigation, last option) ‐> Sites (from dropdown)
• Click on bulletin under Name
• Scroll down to the section Production Server FTP Settings and find FTP Root
• /local/htdocs/bulletin/2021-2022 is listed in the field
The template root must be changed the Remote (production server) Radio Button
Changes need to be made to the files in the colleges_and_schools/rightcolumn_content directory in
OU. Within those files are hard-coded strings for the current Bulletin year (2020-2021). Those need to be
changed to 2021-2022.
Instruction (updating paths within the source view):
• Navigate to Content (top navigation, second option) ‐> Pages (from dropdown)
• Navigate to colleges_and_schools ‐> rightcolumn_content
• There are 10 [[Is that number correct? ]] files in this directory, ccpaCombined.html through watsonUndergrad.html
• Each file needs to be opened in Source view, updated, saved and published:
-- THIS NEEDS TI BE ADDED TI EACH OF THOSE FILES? WHERE?--
<script type=”text/javascript”>
var url = “www.binghamton.edu:8080/exist/rest/bulletin/2020-2021/xq/watson/undergraduate/”;
var xsl = “/bulletin/2020-2021/xsl/MasterCompose.xsl”;
</script>
After the OU site’s publishing location is changed the entire site needs to be published from OU.
This gives a baseline for the new year so Liz can track the changes that are made to any given file.
Instruction (publishing the Bulletin):
• Navigate to Content (top navigation, second option) ‐> Pages (from dropdown)
• Check the box next to all the directories 01_about_bu through colleges_and_schools
• Click on Publish at the top of this window.
There are no Index Files
systemctl reload httpd
The ssl.conf and the vhost.conf entery for bulletinreview.binghamton.edu must be changed for the new year.
Need instructions for GRoups??
Before the editing cycle begins (usually in mid February), the OU editors need to be set up with the prop-
er permissions. The existing set of editors is in place from the past year but there are always changes to be
made. Some new editors are added, some old editors leave, and permissions are sometimes changed as to
who should have access to what files. OU groups are also modified at this time. Sometimes this can be a
little tricky but it’s more tedious than anything else. Some OU editors need to be locked out after the editing
period has ended. Others are locked out later.
Instruction (lock/unlock users):
• Navigate to Setup (top navigation, last option) ‐> Users (from dropdown)
• To lock users, select a user, navigate to the Restrictions section and
check Lock User box and click Save.
• To unlock users, find the user from the listing and click on the red lock in he status column.
Instruction (creating new users):
• Navigate to Setup (top navigation, last option) ‐> Users (from dropdown)
• Click on the New button at the top-right section of the page
• Fill out the User Information section including the Username (PODS id), first name and last name
(referencing a current user account can help)
• Fill out the Restrictions including user level and approver (if needed)
support.omniupdate.com/learn-ou-campus/administration/permissions-chart.html
• Within the New User Options, assign the user to a group
• Click save
Instruction (deleting/removing users):
• Navigate to Setup (top navigation, last option) ‐> Users (from dropdown)
• Find the user from the listing, check the box next to the user and click on Delete option from the top
of the window
Sometimes new files need to be added in OU and old files removed. Sometimes files would need to be
moved from one directory to another. With such changes I would often rename files so that they would re-
main in the proper sequence for when the Bulletin PDF was created in the fall.
Instruction (creating pages):
• John may need to weigh in on this, but I would suggest duplicating an existing page within
the directory that would need a new page.
• Navigate to the directory where the new page needs to be created, check the box next to the page
that will be duplicated and click on the Copy option from the top of the window
Instruction (deleting pages):
• Navigate to the directory where the page needs to be deleted, check the box next to the page
that will be deleted and click on the Delete option from the top of the window
Instruction (moving pages):
• Navigate to the directory where the page needs to be moved, check the box next to the page
that will be moved and click on the Move option from the top of the window
• Using the modal that popped up, navigate to the directory you would like your page to be moved to.
The page will need to be published to see in the production environment.