Changes between Version 4 and Version 5 of UPDT_unit_changes

Timestamp:

11/18/14 13:55:14 (10 years ago)

Author:

lttoth@…

Comment:

--

UPDT_unit_changes

@@ -32 +32 @@
 Once the people registry updates are complete, take the following steps to apply the resulting LDIF to the LDAP repository.
         
-                1. ask DBA group to execute the following to 
+                1. Ask DBA group to execute the following to 
                 add world read permission to ldif files in /tmp
                   * ~oracle/local/production/PMldap_tmp_chmod.ksh
-                1. after the file permissions have been changed,
+                1. After the file permissions have been changed,
                 copy the resulting ldif to sxldap owned 
                 directory and to iplanet account on eklutna
                   * cd $HOME/appworx/
                   * ./manage_ldif_files.ksh
-                1. after copying the resulting ldif,
+                1. After copying the resulting ldif,
                 tell iplanet on eklutna to apply it
                   * ./apply_ldif_files.ksh
-                1. have DBA group run this script to 
+                1. Have DBA group run this script to 
                 delete ldif from /tmp/
                   * ~oracle/local/production/PMldap_tmp_cleanup.ksh
 ==== Publicizing Summary Changes====
 After confirming LDIF applied,
-# email summary of changes to sdedirregistry@email.alaska.edu
-
-        # changes are listed in ldap_RPTS_dept_<date>.changes file
-        cd $HOME/local/ldap/extracts/
-        ls -lrt *dept*changes|tail -1   # check date/time stamp
-        awk '{print $1}' $(ls -1rt *dept*changes|tail -1)|sort |uniq -c
-
-# compare EDIR structure to BOR structure and send
-# email to Budget Offices soliciting response to unit changes
-
-        cd $HOME/local/ldap/query
-        sqlplus /
-                @compare_edir_structure_to_bor.sql
-                exit
-
-        # copy and paste screen output to email for budget offices 
-        # with request for feedback
-        Recipients: Phil Harrington <plharrington@alaska.edu>, Lynn Wrightsman <lawrightsman@alaska.edu>, Barbara Hyde <bjhyde@uas.alaska.edu>
-        CC:  to !ua-oit-registry@alaska.edu 
-
-        # if the budget office respond with feedback
-        # then 
-                # move EDIR data to new unit records if applicable
+1. Email summary of changes to sdedirregistry@email.alaska.edu
+        * Changes are listed in ldap_RPTS_dept_<date>.changes file
+        * cd $HOME/local/ldap/extracts/
+        * ls -lrt *dept*changes|tail -1 # check date/time stamp
+        * awk '{print $1}' $(ls -1rt *dept*changes|tail -1)|sort |uniq -c
+1. Compare EDIR structure to BOR structure and send
+1. Email to Budget Offices soliciting response to unit changes
+        * cd $HOME/local/ldap/query
+        * sqlplus /
+                * @compare_edir_structure_to_bor.sql
+                * exit
+        * copy and paste screen output to email for budget offices with request for feedback
+          * Recipients: Phil Harrington <plharrington@alaska.edu>, Lynn Wrightsman <lawrightsman@alaska.edu>, Barbara Hyde <bjhyde@uas.alaska.edu>
+          * CC:  to !ua-oit-registry@alaska.edu 
+        * If the budget office respond with feedback
+                * move EDIR data to new unit records if applicable
                 (TBD - see beth in meantime)
-
-                # flag to keep, or delete, old unit records if applicable
-                (TBD - see beth in meantime)
-        
-        # Note: No EDIR unit record will be dropped from EDIR unless flagged
-        # in the EDIR_STRUCTURE table.  This allows EDIR to reflect units w/o
-        # budget that are **not** retained in the BOR structure table.
-
-# notify sdtsaa of new/obsolete EDIRroles (associated with unit changes)
-# NOTE: run show scripts before running add/delete scripts in next step
-
-        # first generate list of new and obsolete edir unit related roles
-        # send 2 emails to sdtsaa; one with needed one with obsolete
+                * flag to keep, or delete, old unit records if applicable
+                (TBD - see beth in meantime)    
+        * ''Note:'' No EDIR unit record will be dropped from EDIR unless flagged
+        * in the EDIR_STRUCTURE table.  This allows EDIR to reflect units w/o
+        * budget that are **not** retained in the BOR structure table.
+1. Notify sdtsaa of new/obsolete EDIRroles (associated with unit changes)
+   * First generate a list of new and obsolete EDIR unit related roles
+{{{
         @show_needed_dlevel_roles.sql
         @show_needed_unit_roles.sql
         @show_obsolete_dlevel_roles.sql
         @show_obsolete_unit_roles.sql
-
-# update LDAP_ZUAUSR_ADMIN table, adding needed roles and deleting obsolete roles
-# NOTE: run show scripts before running add/delete scripts
-
+}}}
+   * Run "Show" scripts before running add/delete scripts in the following step
+   * Send an email to sdtsaa; see  [[SyncDirectory|Banner/Directory Synchronization]] for detailed instructions.
+1. Update LDAP_ZUAUSR_ADMIN table, adding needed roles and deleting obsolete roles
+    * Run show scripts before add/delete
+{{{
         @add_needed_dlevel_roles.sql
         @add_needed_unit_roles.sql
         @delete_obsolete_dlevel_roles.sql
         @delete_obsolete_unit_roles.sql
-
+}}}
 ########################################################[[br]]
 LEGACY CHANGE HISTORY - NOTE: All subsequent changes are recorded in TracWiki[[br]]