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/07/20 21:34] – [Functional roles (with DokuWiki group)] marieframework_data_governance [2026/07/20 21:37] (current) – [Update management (needs_update)] marie
Line 14: 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, Archive (upon decision of the steering committee) | @maintainers |  +| 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/software | Convert data format for export prior to publication | @packager |  | Packager | Ensure data is formatted to be compatible with other databases/software | Convert data format for export prior to publication | @packager | 
 | 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 | +| Support | Manage user feedback | Collect feedback. Mark as `needs_update` | @support | 
 | Users | Use the data | View only | @members |  | Users | Use the data | View only | @members | 
  
Line 108: 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 118: 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)