|
| 1 | +# Documentation |
| 2 | + |
| 3 | +List of required documentats for the SCC, and process, format, and standard location |
| 4 | +for each. |
| 5 | + |
| 6 | +## What and Where |
| 7 | + |
| 8 | +### Business Documentation |
| 9 | + |
| 10 | +Process |
| 11 | + |
| 12 | +* Collaborate on creation in Google Docs |
| 13 | +* Export as a PDF, name with date, store `here <../../formal_docs>`_ |
| 14 | +* Copy to Discourse |
| 15 | + |
| 16 | +Needed docs |
| 17 | + |
| 18 | +* Privacy Policy (Written in 2020. Time to update/review?) |
| 19 | +* Disaster Recovery Plan |
| 20 | +* Data Recovery Process |
| 21 | +* Business Continuity Plan |
| 22 | +Change Management Plan (beta version available for review Specify Change Management Procedure.docx) |
| 23 | +Terms of Use/Service (written in 2020. Time to update/review?) |
| 24 | +License |
| 25 | + |
| 26 | +### Security Documentation |
| 27 | +HECVAT (Final edit needed) |
| 28 | +Security Incident Response Plan |
| 29 | +VPAT2 (last filled out in 2023 should be reviewed and updated) |
| 30 | +Information Security Policy |
| 31 | +Risk Management Program |
| 32 | + |
| 33 | +### Services Agreement Documentation |
| 34 | + |
| 35 | +Migration Agreement |
| 36 | +: Legal agreement for conversions, to be presented to client for signature, with a |
| 37 | + supplementary **Migration Scope** document. |
| 38 | + |
| 39 | +Migration Scope |
| 40 | +: Supplementary document containing metadata about migration source data determined by |
| 41 | + Client and SCC developer analyses of source data, including data type, encoding, and |
| 42 | + size, tree requirements, database number and collection types, projected duration, |
| 43 | + and projected cost. Created from a template for each Data Migration. |
| 44 | + |
| 45 | +Migration Workplan |
| 46 | +: Document listing source data metadata from **Migration Scope** as well as |
| 47 | + Client database and collection configuration requirements, and timetable based on |
| 48 | + projected time for each step of the migration and developer availability. Created |
| 49 | + from a template for each Data Migration. |
| 50 | + |
| 51 | +Hosting Agreement |
| 52 | +: Legal document describing 1) how the SCC enables the Client to remotely access and use |
| 53 | + the Specify software and all its customer data in “Software as a service” mode; and |
| 54 | + 2) explicitly identifies the Specify Cloud Service hosting technical support services, |
| 55 | + software maintenance and updates, price, online availability, backup protocols, |
| 56 | + access restrictions, data ownership, and stakeholder responsibilities. |
| 57 | + |
| 58 | +### Member Agreement Documentation |
| 59 | +Member Agreement |
0 commit comments