Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
framework_data_governance [2026/06/01 00:58] – [Update management (needs_update)] sophieframework_data_governance [2026/06/01 01:04] (current) – [Page lifecycle] sophie
Line 51: Line 51:
 | @communicator | User notifications | Communications team | | @communicator | User notifications | Communications team |
 | @support | User support | Customer support team |  | @support | User support | Customer support team |
- 
 ## Page lifecycle ## Page lifecycle
  
 Overview Overview
-image à incerer+ 
 +{{ :framework_data_governance.png?direct |}} 
 +r
 ### Page statuses ### Page statuses
  
Line 105: Line 106:
  
 **Key point**: The *tech_approved* status remains after editorial rejection. Only textual corrections are required; technical validation is not needed again (unless the technical content is modified). **Key point**: The *tech_approved* status remains after editorial rejection. Only textual corrections are required; technical validation is not needed again (unless the technical content is modified).
 +
  
 ### Periodic review (needs_update) ### Periodic review (needs_update)
Line 115: Line 117:
 | deprecated | Content obsolete, no replacement | Marked and archived | | deprecated | Content obsolete, no replacement | Marked and archived |
 | New draft | Major changes / overhaul | Create new page (old one will be automatically superseded) | | New draft | Major changes / overhaul | Create new page (old one will be automatically superseded) |
 +
 +
 ### Update management (needs_update) ### Update management (needs_update)
  
Line 154: Line 158:
 | List of update requests | List of update requests to be processed and initiation of discussions | @users, @maintainers |  | List of update requests | List of update requests to be processed and initiation of discussions | @users, @maintainers | 
 | Communications | Pages that have been modified/added/archived, requiring an announcement | @communicators | | Communications | Pages that have been modified/added/archived, requiring an announcement | @communicators |
- 
 ### Technical Proposal ### Technical Proposal
  
Line 168: Line 171:
 Overview of the rights associated with each of the roles implemented in DokuWiki. Overview of the rights associated with each of the roles implemented in DokuWiki.
  
-^ Action ^ Producers ^ Documenters ^ Maintainers ^ Technical Review ^ Content Review ^  ^ Interoperability Manager ^ Steering Committee ^ Packager ^ Communicator ^ Support ^  ^ Users ^ +^ Action ^ Producers ^ Documenters ^ Maintainers ^ Technical Review ^ Content Review ^ Interoperability Manager ^ Steering Committee ^ Packager ^ Communicator ^ Support ^  ^ Users ^ 
 | Create a page (draft) | yes | yes |  |  |  |  |  |  |  |  |  | | Create a page (draft) | yes | yes |  |  |  |  |  |  |  |  |  |
 | Edit a draft | yes | yes | yes |  |  |  |  |  |  |  |  | | Edit a draft | yes | yes | yes |  |  |  |  |  |  |  |  |
Line 189: Line 192:
  
 ^ DokuWiki Group ^ Permissions ^ ^ DokuWiki Group ^ Permissions ^
-| @producers | Create, edit drafts, submit, view (published + archive) | +| @producers | Create, edit drafts, submit, view (published and archive) | 
-| @documenters | Create, edit drafts, submit, view (published + archive) | +| @documenters | Create, edit drafts, submit, view (published and archive) | 
-| @maintainers | Edit drafts, submit, mark as needs_update, archive, view (published + archive) | +| @maintainers | Edit drafts, submit, mark as needs update, archive, view (published and archive) | 
-| @technical review | Approve level 1a, mark as needs_update, view (published + archive) | +| @technical review | Approve level 1a, mark as needs update, view (published and archive) | 
-| @content review | Approve level 1b, mark as needs_update, view (published + archives) | +| @content review | Approve level 1b, mark as needs update, view (published and archives) | 
-| @steering | Approve level 2, assign updates, mark as deprecated, view (published + archives) | +| @steering | Approve level 2, assign updates, mark as deprecated, view (published and archives) | 
-| @members | View published pages + archives | +| @members | View published pages and archives |
 ## Conclusion ## Conclusion
  
 This document has outlined the data lifecycle and the associated documentation pages that will be integrated into the DocuWiki tool. As such, all functional and organisational roles, along with their associated rights, have been defined. The proposed processes for validating and updating the knowledge base content have also been described. This document has outlined the data lifecycle and the associated documentation pages that will be integrated into the DocuWiki tool. As such, all functional and organisational roles, along with their associated rights, have been defined. The proposed processes for validating and updating the knowledge base content have also been described.
-To inform discussions on data governance, a Data Management Plan is also being developed and will be updated throughout the project. The current draft version is available in the appendix entitled ‘PGD_du_projet_naKnow_(InnoData_Silicium).pdf’.+To inform discussions on data governance, a Data Management Plan is also being developed and will be updated throughout the project. The current draft version is available in the appendix entitled ‘PGD du projet naKnow (InnoData_Silicium)’.