- Don't panic
- Speak to team face-to-face / talk to people who might be able to help
- Identify who can help and decide on incident responders
- Identify what's happening / what has happened and the scope of the incident e.g. outage, privacy leak
- Determine the impact and severity and priority (does it need to be fixed now?)
- Make sure relevant people are made aware, including stakeholders, and keep them up-to-date
- Don't do anything hasty (so no other problems are caused)
- Establish the order to fix things, and delegate
- Identify the best/immediate fix and apply, including considering taking affected services offline
- If incident causes visible disruptionto public services put up relevant alert message
N Pollecutt pollecuttn
pollecuttn
/ Wellcome Collection services
Created
April 25, 2019 14:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * Catalogue API | |
| * Storage API | |
| * Archivematica | |
| * Goobi | |
| * Loris | |
| * IIIF presentation API | |
| * DLCS | |
| * DDS | |
| * Prismic CMS | |
| * What's On |
pollecuttn
/ Incident checklist.md
Created
April 25, 2019 14:34