--- Bulletin - Start New Bulletin ---


/var/www/SEC/Bulletin-Start-New.html

JH Wiki to start a new Bulletin,
Time Line for 2021 University Bulletin DOCX

Start an Admin Client
         Java Admin Client:
      or https://www.binghamton.edu:8443/exist/
   To do any steps below (I like running from the server)

01) Make a Backup of the current year
        -- Login to the admin account.
        -- Click on Backup. 
               This takes you to the “Backup Central” panel.
        -- Check the Zip box.
        -- Click Trigger Backup.
      Once the backup has been created ...
      Click [Download selected] button from the “Backup Central” panel to download the zip file. 
      	This is the square icon with the green up arrow on the panel to the left.
         The ZIP file is downloaded to the computer that the download is executed on,
             NOT to bingwww.

02)  Create a New Collection:
      Click on the Collections Icon
      Navigate to the new Bulletin folder|resource
      On Top Panel → New Collection (Folder with Green+ Icon)
         This will open the Create Collection dialog box.
            Enter the year : <this year + 1>-<this year + 2>  2021-2022
         Click OK

03) Import current years collection (from step 01)
    Unzip the zip file that you downloaded in the earlier step (01) on the PC being used.
      -- Create a directory with the new year set 2021-2022
      -- Select the extract all
     Goto or start the Admin Client
      -- Click the Collections Icon
      -- Click on the bulletin line
      -- Navigate down to the new collection year and click it
      -- Click the disk icon with a Disk Barrel Green+ last to the left.
      -- A diaglog box will appear, move into the hollow orange button ..
            it will turn green...click it.     
      -- On the PC navigate to the directory where the zip was expanded into. 
             Navigate down folder for last year.
             Ctrl A will select all the files in the directory
             Click [Select files or directories to store].

04) Change permissions on XQuery files
     XQuery files need execute permission
              otherwise, when you open a Bulletin page that uses an XQuery file, 
              you will be asked for a user/password before it loads. 
              Use the Java Admin Client to change file permissions. See also troubleshooting.
              Change the permissions to read/write/execute for owner 
                                    and read/execute for group and other. Click Save.
    Highlight the files for which you want to change permissions
    Click on the Edit owners/permissions for selected resourceicon.The Page and Pencil icon
    Change the permissions to read/write/execute for owner|user and read/execute for group and other. Click Save.

05) Edit the new collection files
    Use the oXygen XML editor to make any necessary changes to the new file collection to get them ready for the new Bulletin year.
    If you have the oXygen XML editor open before setting up the new collection, 
          you may have to disconnect the eXist-db connection and 
          then reopen it before you are able to open any of the files.
    From within the oXygen editor, Control-click on the connection and select Disconnect.

 -- Bulletin Review
 -- http://www.binghamton.edu:8080/exist/rest/bulletin/2021-2022/index.html
 -- What runs the exist database presentation
 -- When the permissions are changed on all of the XQuery files and we go back and check it doesn't show u-rwx g|o r-x 

06) Switching to new Bulletin year
     When the time comes in June to make the new Bulletin current, you will need to point bulletin.binghamton.edu to the new collection.

      Login to Bingwww and navigate to the configuration directory for Apache HTTPD.
      cd /etc/httpd/conf.d
      vi vhosts.conf
           RewriteRule / http://www.binghamton.edu:8080/exist/rest/bulletin/2019-2020/index.html  [R=302,L]
           to
           RewriteRule / http://www.binghamton.edu:8080/exist/rest/bulletin/2020-2021/index.html  [R=302,L]

      Reload HTTPD.
           systemctl reload httpd
           systemctl status httpd


    

Valid HTML 4.0 Transitional

o