= Stakeholder Analysis = The below table lists the currently identified stakeholders of the DOMS project. Each stakeholder entry specifies what role the stakeholder has in the project, what the stakeholder's contribution to the project is, the importance of the stakeholder and any tasks the stakeholder has special interests in. The importance of a stakeholder is rated with a number between 1 and 5, where 1 is the most important, however, only stakeholders that have unrestricted powers over the project (i.e. the power to terminate the project) should have a rating of 1, which usually is limited to the project owner, however, in reality it may include a few more stakeholders. ## NOTE: Please make sure that a stakeholder page has been created for the stakeholders you add to the below table. ## If no such page exists then please create it using the StakeholderTemplate. ||'''Stakeholder''' ||<16% bgcolor="#cccccc" style="vertical-align: top;">'''Role in the project''' ||<16% bgcolor="#cccccc" style="vertical-align: top;">'''Contribution''' ||<10% bgcolor="#cccccc" style="vertical-align: top;">'''Importance (1-5)''' ||||<16% bgcolor="#cccccc" style="vertical-align: top;">'''Especially relevant for task''' || ||[[StakeHolderSteeringGroup|Steering Group]] ||Mission Control ||Guidance regarding scope and strategy||<: style="vertical-align: top;">1 || || ||[[StakeHolderTheITStaff|The IT Staff]] ||Must maintain the system after deployment. Handle files. ||Requirements to maintenance tools. File access layer.||<: style="vertical-align: top;">2 || || ||[[StakeHolderInternalContentOwners|Internal Content Owners]] ||Content providers||Contribute collections to be put in DOMS. Has contact to external content owners.||<: style="vertical-align: top;">2 || || ||[[StakeHolderTheWebTeam|The Web Team]] || Creators of Summa.||Summa. Primary front end. User knowledge.||<: style="vertical-align: top;">2 || || ||[[StakeHolderLibraryUsers|Library users]] || End users of DOMS material ||Requirements to dissemination and access rights; feedback||<: style="vertical-align: top;">3 || || ||[[StakeHolderTheFedoraCommunity|The Fedora Community]] || Creators of Fedora||Metadata management software for DOMS. Repository knowledge ||<: style="vertical-align: top;">3 || || ||[[StakeHolderTheSBLibrarians|The SB Librarians]] ||Marketing and guidance on DOMS material. ||Requests from Library users wrt. popular material||<: style="vertical-align: top;">3 || || ||[[StakeHolderCopyrightHolders|Copyright holders (Copydan)]] ||Legal representatives of some external content contributors ||Requirements to enforce content owners copyrights ||<: style="vertical-align: top;">3½ || || ||[[StakeHolderHelpdesk|Helpdesk]] ||Future software support on DOMS||First line of defence||<: style="vertical-align: top;">4 || || ||[[StakeHolderDatatilsynet|Datatilsynet]] ||Authority in charge of protection of sensitive data ||Requirements to access control, logging, and data correlation of sensitive data ||<: style="vertical-align: top;">4 || || ||[[StakeHolderDKAAI|DK-AAI]] ||Coordinating project of Authorization and Authetication Infrastructure ||Gives a framework for handling access rights||<: style="vertical-align: top;">4 || || ||[[StakeHolderPlanets|Planets]] ||Provider of digital preservation services ||Digital preservation planning, characterisation and action (migration)||<: style="vertical-align: top;">4 || || ||[[StakeHolderDPE|DPE]] || Provider of digital preservation coordination, and TDR certification||A TDR framework. Contact with other European instutions doing TDR work ||<: style="vertical-align: top;">5 || || ||[[StakeHolderMjoelner|Mjølner]] || External developer of GUI ||A GUI-generator ||<: style="vertical-align: top;">- || ||