Nested Knowledge

Bringing Systematic Review to Life

User Tools

Site Tools


wiki:policies:disaster

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:policies:disaster [2023/10/10 20:18]
katcow
wiki:policies:disaster [2024/03/04 00:00] (current)
katcow
Line 54: Line 54:
 |EuropePMC| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.| |EuropePMC| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.|
 |DOAJ| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.| |DOAJ| |Yes|Yes|When a disruption occurs, manual and recurring searches fail. Upon recovery, our system automatically begins rerunnning scheduled failed searches.|
 +|Abstra|Abstra|Yes|No|Disruptions may impact the timeliness of customer support actions. |
  
 ==== Roles and Contacts ==== ==== Roles and Contacts ====
Line 66: Line 67:
 === Loss of Function of Critical Applications === === Loss of Function of Critical Applications ===
  
-  * In the case of the loss of functionality to AutoLit or Synthesis, the CTO will be notified and we will send out a Site Disruption message to all users. The CTO and development team will assess the extent of any lost capabilities and timeline to restoration, and then communicate with company leadership regarding a recovery plan of specific functions.+  * In the case of the loss of functionality to AutoLit or Synthesis for at 30 or more minutes, the CTO will be notified and we will send out a Site Disruption message to all users. The CTO and development team will assess the extent of any lost capabilities and timeline to restoration, and then communicate with company leadership regarding a recovery plan of specific functions.
   * In the case of the loss of functionality to any other key/critical applications, the CTO will be notified; Site Disruption messages will only be sent to users in the case that this impacts end user functions. In consultation with company leadership, the CTO and development team will create a plan to either restore function or shift to a different software provider.   * In the case of the loss of functionality to any other key/critical applications, the CTO will be notified; Site Disruption messages will only be sent to users in the case that this impacts end user functions. In consultation with company leadership, the CTO and development team will create a plan to either restore function or shift to a different software provider.
-  * In case of outages, the CEO will email account representatives for customers with a proposed restoration timeline and details regarding the outage. +  * In case of outages, the CEO or another leader will email account representatives for customers with a proposed restoration timeline and details regarding the outage.
-      * Outages will also be communicated on Twitter @nestedknowledge+
  
 === Recession Planning === === Recession Planning ===
wiki/policies/disaster.1696969106.txt.gz · Last modified: 2023/10/10 20:18 by katcow