\ 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.

\

This section describes the various roles associated with groups within the technical infrastructure. It is important to note that a single individual may hold several roles simultaneously.

Note: The role of packager could just as easily be fulfilled within naKnow, or by the developers of the tools or databases that wish to integrate with it.

The roles required for the organisation but which do not require a specific rights group within the infrastructure are as follows:

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.

Summary of the groups to be created within DokuWiki corresponding to the various roles.

Overview image à incerer

Tags associated with documentation pages intended for the general public. Their purpose is to inform the user and do not necessarily correspond to a stage in the data lifecycle. The date of the last tag change will be accompanied by a modification date to enable the user to track the page’s timeline. The validity period for pages is set at one year, after which they are automatically set to ‘needs_update’. However, individual teams may choose to extend or reduce this period based on their expertise.

Tags for internal data lifecycle management.

All stakeholders. As any stakeholder can flag a page as needing updating, a discussion is initiated to assess whether an update is actually required before the process is formally launched. This discussion can be started in the wiki comments.

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).

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.

• An authorised user marks the page as needs update
• A discussion begins with the person who flagged the need for a change, who then changes the status to update review
• If the discussion confirms the need, the status changes to update confirmation and the management committee assigns a lead (after consulting the relevant project manager)
  • The assigned manager changes the page to ‘draft’ and makes the changes
  • The page returns to the normal validation cycle
• If the update is not necessary, no action is taken.
• If an update is required because the data is obsolete, but no project is feasible to replace it, the management committee is notified to decide whether the data should be deprecated.

When a newly published page explicitly references a deprecated page as its replacement, the transition to ‘superseded’ is automatic.

Description of the end-of-life process for the data and its associated documentation page.

All dashboards required for the knowledge base to function properly.

### Technical Proposal

Proposal for technical components to implement the proposed lifecycle. Plugins

1. Approve (https://www.dokuwiki.org/plugin:approve): Management of permissions, groups and file history
   1. Prerequisites: SQLite to manage the approval process
   2. Note: Check compatibility with the tech_approved status and the two-stage workflow
2. Notification (https://www.dokuwiki.org/plugin:notification): Notify the various stakeholders of expected actions

Overview of the rights associated with each of the roles implemented in DokuWiki.

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 ‘PGDduprojetnaKnow(InnoData_Silicium).pdf’.