Differences

This shows you the differences between two versions of the page.

--- sfx_update_procedures [2019/03/29 15:41]
jmulvaney
+++ sfx_update_procedures [2019/03/29 15:59]
jmulvaney [Tips and Notes]
@@ Line 8: / Line 8: @@
   *As hosted customers, our update is applied a week later than the current update. This affects applicable software changes, new and removed targets, and other changes in SFX. Target name changes/deletions affect Menu Display logic and Target Precedence (needs to be changed manually or in sort_services_config eventually).
-==== Tips and Notes  ====
+=== Weekly maintenance ===
+    * **KB Update Reports** are obtainable from the front page of the SFX Admin under KBUpdate. They both reports should be run every Monday. Setting to "Yes" is supposed to retrieve only UMass active targets but does include UMass formerly-active targets, designated "Inactive". Any time you choose an option be sure to let the page reload.
+      * **HTML Report:** Under //Type of Change// check Deleted and Updated. Set //Filter to active/localized only?// to Yes. Choose //Targets, Target Services, Sources, Source Services.// Click submit. View Updated Active Records. Test linking for things that have changed.
+          * Platform changes occasionally appear in this report. Make sure they go onto the Platform Changes worksheet.
+      * **Text Report:** Set //Type of Change// to Deleted. Set //Filter to active/localized only?// to yes. Choose Deleted Object Portfolios. Click Submit. The results will launch as a text file which you should copy and paste into excel. Sort alphabetically by Target.
+          * Previous title and other deletions in ejournal packages appear here. Officially, ExLibris does delete our active object portfolios but it still happens occasionally. Disregard databases with fluid content.
-  * **Release Notes** for the next update can be checked for upcoming target deletions. Be sure they are deactivated, with object portfolios moved. Check for upcoming changes to targets. Export any target active portfolios that might be affected (e.g. previous titles that might be lost).
+  * **KB Release Notes** are available at the URL listed above. They show the changes in the next KB update like target deletions, name changes, new targets, etc.
-  * **KB Update Reports** are obtainable from SFX Admin>KBUpdate. Setting to "Yes" is supposed to retrieve only UMass active targets but does include UMass formerly-active targets, designated "Inactive".
+      * Ignore the //Applying the Revision// section. This is for libraries who manage their own server.
-      * **HTML Report:** Check Deleted and Updated "Targets, Target Services, Sources, Source Services." Test linking.
+      * //Target Name Changes// affect target precedence and menu logic. If you see that an active target is going to be changed, make sure that it is updated in both places. (Or wait for the Sort Services Config.) Be sure to make a note of it in CORAL.
-      * **Text Report:** Important: Set to "Yes" and check Deleted Object Portfolios for possible previous title and other deletions in ejournal packages (ExLibris does delete our active object portfolios occasionally). Disregard databases with fluid content.
+      * If something we have activated appears in the //Targets to be Removed// make sure to find out exactly when they will be deleted. Be sure they are deactivated before then, with active object portfolios moved (including activation status, date thresholds, and notes). Export any target active portfolios that might be affected (e.g. previous titles that might be  lost).
+          * You can also run a collections report between the Target being deleted and they one ExLibris suggests we use to see what changes you might encounter.
-=== Weekly maintenance ===
+      * //Targets Removed// shows when a target is actually taken out of the KB.
+      * Check CORAL to see if anything in //New Targets and Target Services// should be activated. Since we are hosted our update is deferred by one week, so you will have to wait to check if it really works for something we subscribe to.
+      * //Changed KB Software// is like mini patch notes. For the most part they don't affect anything but can provide hints to what bigger issues ExLibris might be working on.
   * **UNIX-side: Clean sessions subdirectory**. This terminates live sessions so best to do in quiet times.
-          * Login UNIX-side.
+      * Login UNIX-side.
-          * ds
+      * ds
-          * cd sessions
+      * cd sessions
-          * rm cgisess_*  (if done regularly, there is no need to breakdown with numbers and letters, e.g. rm cgisess_0* and rm cgisess_a*)
+      * rm cgisess_*  (if done regularly, there is no need to breakdown with numbers and letters, e.g. rm cgisess_0* and rm cgisess_a*)
-          * (To exit without checking stats)
-            * da
-            * exit
-  * **UNIX-side: Check Stats tables.**
       * da
+        * (To exit without checking stats, if not continue one below)
+        * exit
+  * **UNIX-side: Check Stats tables.**
+      * da (continued from above)
       * ./server_admin_util
       * 5 (Statistics)
@@ Line 34: / Line 43: @@
       *q
       *exit
-  * Check outstanding SFX support cases at [[https://exlidp.exlibrisgroup.com | Salesforce]]. Login to see support cases.
+  * **Check outstanding SFX support cases** at [[https://exlidp.exlibrisgroup.com | Salesforce]]. Login to see support cases.
 === Monthly maintenance ===
-  * Scratch directory cleanout. ExLibris may be automatically cleaning this file but check for stats and old export files.
+  * **Scratch directory cleanout:** ExLibris may be automatically cleaning this file but check for stats and old export files.
        * Web side: SFX Admin>Administration>UNIX File Manager>dbs>scratch
-       *  **DO NOT DELETE: Sessions Directory! Recent e_collection and MARCit files! Institutional holdings file (Google Scholar/WorldCat holdings)! ** Leave several months in scratch folder.
+       *  **DO NOT DELETE:** Sessions Directory! Recent e_collection and MARCit files! Institutional holdings file (Google Scholar/WorldCat holdings)!
-  * Export directory cleanout. This seems to be automatically cleaned out as of 2016.
+           * Leave several months in scratch folder.
-       * Web side: SFX Admin>Administration>UNIX File Manager>Export
+  * **Export directory cleanout:** This seems to be automatically cleaned out as of 2016.
+       * Web side: SFX Admin > Administration > UNIX File Manager > Export
   * **UNIX side bX Statistics file cleanout**
        * After notification that a successful harvest has occurred or every month or two, clean the OAI_REPOSITORY table.
@@ Line 51: / Line 64: @@
           * y (erase all records in table OAI_REPOSITORY)
           * q
           * exit
   * **Statistics.** File monthly statistics run by cron and reported by email to DRMS email. See [[https://www.library.umass.edu/wikis/acp/doku.php?id=sfx_statistics_archives_files | SFX Statistics and Archives Files wiki page. ]]
@@ Line 57: / Line 71: @@
 === Other Maintenance  ===
   * **sort services config**: See https://www.library.umass.edu/wikis/acp/doku.php?id=sfx_routine_maintenance#sort_servicesconfig
   * **Cron jobs:** Check regularly as they have disappeared. These are presently running as scheduled jobs see: [[sfx_cron_jobs]]
-  * NERS voting, ELUNA: An email from SFXList notifies when SFX potential targets or software is available for customer voting. See SFX in CORAL, access page has login. See also https://www.library.umass.edu/wikis/acp/doku.php?id=sfx_routine_maintenance#support_cases_content_and_enhancement_requests for details.
+  * **NERS voting, ELUNA:** An email from SFXList notifies when SFX potential targets or software is available for customer voting. See SFX in CORAL, access page has login. There is more info on the SFX Routine Maintenance Page as well
 //[[jmulvaney@library.umass.edu|Primary contact: Jack Mulvaney]]//