ScapePlatformImplementationRisksMitigation: Difference between revisions
Jump to navigation
Jump to search
PRWheatley (talk | contribs) (Created page with "==SCAPE Platform implementation risks and mitigation== *Adopting cutting edge technology risky **Web archiving department already has confidence and experience with Hadoop tec...") |
PRWheatley (talk | contribs) |
||
Line 1: | Line 1: | ||
==SCAPE Platform implementation risks and mitigation== | ==SCAPE Platform implementation risks and mitigation== | ||
*Adopting cutting edge technology risky | *Adopting cutting edge technology is risky | ||
**Web archiving department already has confidence and experience with Hadoop technology | **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 | **Some SCAPE components less well tested in production environments. Early visits to SCAPE Project partners will be used to identify and avoid typical pitfalls |
Revision as of 09:40, 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