Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| framework_data_governance [2026/06/01 01:01] – [Rights matrix] sophie | framework_data_governance [2026/07/20 21:37] (current) – [Update management (needs_update)] marie | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ## Introduction | ## Introduction | ||
| - | \ | + | |
| The purpose of this document is to outline the **data lifecycle** and the associated **documentation** within the framework of data governance for the naKnow organisation’s knowledge base. Topics covered include the **definition of the various roles** involved, their rights, the **lifecycle of data and data documentation pages**, as well as all the associated **validation and update processes**. | The purpose of this document is to outline the **data lifecycle** and the associated **documentation** within the framework of data governance for the naKnow organisation’s knowledge base. Topics covered include the **definition of the various roles** involved, their rights, the **lifecycle of data and data documentation pages**, as well as all the associated **validation and update processes**. | ||
| **Functional roles** are assigned within the project team, with the method left to the discretion of those involved. By contrast, **organisational roles** (project manager and partner manager) are assigned by the management committee. | **Functional roles** are assigned within the project team, with the method left to the discretion of those involved. By contrast, **organisational roles** (project manager and partner manager) are assigned by the management committee. | ||
| ## Roles | ## Roles | ||
| - | \ | ||
| ### Functional roles (with DokuWiki group) | ### Functional roles (with DokuWiki group) | ||
| Line 15: | Line 14: | ||
| | Producers | Create raw scientific content (research, experiments) | Create/edit pages | @producers | | | Producers | Create raw scientific content (research, experiments) | Create/edit pages | @producers | | ||
| | Documenters | Format content into a standard format (on the same pages as the Producers). Aim to make content accessible to a wider audience. A parallel can be drawn with editors in the scientific process | Edit pages, finalise drafting | @documenters | | | Documenters | Format content into a standard format (on the same pages as the Producers). Aim to make content accessible to a wider audience. A parallel can be drawn with editors in the scientific process | Edit pages, finalise drafting | @documenters | | ||
| - | | Maintainers | Ensure consistency between pages and monitor validation processes, Verify the data lifecycle, Raise alerts | Edit pages, Mark as needs_update, | + | | Maintainers | Ensure consistency between pages and monitor validation processes, Verify the data lifecycle, Raise alerts | Edit pages, Mark as `needs_update`, Archive (upon decision of the steering committee) | @maintainers | |
| - | | Technical Review | Technical review / Data LCA | Approve level 1a (technical quality), Mark as needs_update | @technical review | | + | | Technical Review | Technical review / Data LCA | Approve level 1a (technical quality), Mark as `needs_update` | @technical review | |
| - | | Content Review | Check clarity and editorial quality (popularisation) | Approve level 1b (editorial quality), Mark as needs_update | @content review | | + | | Content Review | Check clarity and editorial quality (popularisation) | Approve level 1b (editorial quality), Mark as `needs_update` | @content review | |
| | Interoperability manager | Ensure compatibility between data and calculators to guarantee their integrated operation within the naKnow ecosystem | Convert data format for interoperability between calculators | @interoperability manager | | | Interoperability manager | Ensure compatibility between data and calculators to guarantee their integrated operation within the naKnow ecosystem | Convert data format for interoperability between calculators | @interoperability manager | | ||
| | Steering Committee (SC) | Validate strategy, coordinate | Approve Level 2 (publication). Assign updates. Mark as deprecated | @steering | | | Steering Committee (SC) | Validate strategy, coordinate | Approve Level 2 (publication). Assign updates. Mark as deprecated | @steering | | ||
| | Packager | Ensure data is formatted to be compatible with other databases/ | | Packager | Ensure data is formatted to be compatible with other databases/ | ||
| | Communicator | Inform the community of updates, archiving and changes made to the database | Communicate changes within the database | @communicator | | | Communicator | Inform the community of updates, archiving and changes made to the database | Communicate changes within the database | @communicator | | ||
| - | | Support | Manage user feedback | Collect feedback. Mark as needs update | + | | Support | Manage user feedback | Collect feedback. Mark as `needs_update` |
| | Users | Use the data | View only | @members | | | Users | Use the data | View only | @members | | ||
| Line 36: | Line 35: | ||
| **Note**: Project managers have autonomy over decisions within their own areas of responsibility. The management committee handles cross-functional decisions and consults with them to assign updates. | **Note**: Project managers have autonomy over decisions within their own areas of responsibility. The management committee handles cross-functional decisions and consults with them to assign updates. | ||
| + | |||
| ### DokuWiki Groups | ### DokuWiki Groups | ||
| Line 55: | Line 55: | ||
| Overview | Overview | ||
| - | image à incerer | + | |
| + | {{ : | ||
| ### Page statuses | ### Page statuses | ||
| Line 106: | Line 108: | ||
| **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) | + | |
| The periodic review is triggered by the data lifecycle. The content is marked as requiring an update. If the need for an update is confirmed, **the new page is not visible to @members**. | The periodic review is triggered by the data lifecycle. The content is marked as requiring an update. If the need for an update is confirmed, **the new page is not visible to @members**. | ||
| Line 116: | 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 166: | Line 166: | ||
| - **Note**: Check compatibility with the `tech_approved` status and the two-stage workflow | - **Note**: Check compatibility with the `tech_approved` status and the two-stage workflow | ||
| - **Notification** (https:// | - **Notification** (https:// | ||
| + | |||
| ### Rights matrix | ### Rights matrix | ||
| Line 191: | Line 192: | ||
| ^ DokuWiki Group ^ Permissions ^ | ^ DokuWiki Group ^ Permissions ^ | ||
| - | | @producers | Create, edit drafts, submit, view (published | + | | @producers | Create, edit drafts, submit, view (published |
| - | | @documenters | Create, edit drafts, submit, view (published | + | | @documenters | Create, edit drafts, submit, view (published |
| - | | @maintainers | Edit drafts, submit, mark as needs_update, archive, view (published | + | | @maintainers | Edit drafts, submit, mark as needs update, archive, view (published |
| - | | @technical review | Approve level 1a, mark as needs_update, view (published | + | | @technical review | Approve level 1a, mark as needs update, view (published |
| - | | @content review | Approve level 1b, mark as needs_update, view (published | + | | @content review | Approve level 1b, mark as needs update, view (published |
| - | | @steering | Approve level 2, assign updates, mark as deprecated, view (published | + | | @steering | Approve level 2, assign updates, mark as deprecated, view (published |
| - | | @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’. | ||