ScapePlatformImplementationRisksMitigation: Difference between revisions
Jump to navigation
Jump to search
PRWheatley (talk | contribs) |
PRWheatley (talk | contribs) |
||
Line 8: | Line 8: | ||
**Exploit skills in web archiving department | **Exploit skills in web archiving department | ||
**Utilise training courses early in project to bring key team members up to speed | **Utilise training courses early in project to bring key team members up to speed | ||
*Shared use of cluser may lead to clashes with web archiving department needs | |||
**Coordinate planning of cluster use in advance with web archiving department |
Revision as of 09:41, 5 May 2014
SCAPE Platform implementation risks and mitigation
- Adopting cutting edge technology is risky
- Web archiving department already has confidence and experience with Hadoop technology
- Some SCAPE components less well tested in production environments. Early visits to SCAPE Project partners will be used to identify and avoid typical pitfalls
- Insufficient Hadoop cluster IT support skills
- IT department already familar with maintenance of cluster.
- Insufficient Hadoop skills in the digital preservation department
- Exploit skills in web archiving department
- Utilise training courses early in project to bring key team members up to speed
- Shared use of cluser may lead to clashes with web archiving department needs
- Coordinate planning of cluster use in advance with web archiving department