New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
PageTemplates/Workplan/Action (diff) – NEMO

Changes between Version 12 and Version 13 of PageTemplates/Workplan/Action


Ignore:
Timestamp:
2016-10-12T15:28:51+02:00 (7 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PageTemplates/Workplan/Action

    v12 v13  
    11= ''`${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`'' 
    22 
    3 ''For each institute, the NEMO Officer [[BR]] 
    4 The development process of each action of the yearly workplan should be described only in one wiki page based on this template and created in the workplan tree with the pattern `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`''.[[BR]] 
     3''Per institute, the NEMO Officer creates a wiki page for each action of the yearly workplan using this template. The pattern for the page name to place it in the workplan tree with is `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`''. 
    54 
    65''The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.[[BR]]'' 
     
    109== Help 
    1110 
    12 The action has to be detailed briefly in the 'Summary' sub-page (ordinary wiki page) for later inclusion in the 'Shared Actions' or institute page. Out of this, the rest of the page can be edited on-line inside the form fields considering the color code, record your modifications by clicking on the 'Save ...' button at the end of the section. This is the color code for the fulfilment of this form: 
     11The action has to be detailed briefly in the 'Summary' sub-page (ordinary wiki page) for later inclusion in the 'Shared Actions' or institute page. Out of this, the rest of the page can be edited on-line inside the form fields considering the color code, record your modifications by clicking on the 'Save ...' button at the end of the section. This is the color code for the fulfilment of different sections of this form: 
    1312{{{#!th style="background:lightgrey" 
    1413PI(S) 
     
    3433}}} 
    3534 
    36 '''There is absolutely no risk for all form content to make any modification in the wiki page as long as you edit out of `{{{TracForm ... }}}` processor'''. The data of a form field is stored in a different database from the wiki page, so you can delete a version or submit a new one without danger.[[BR]] 
    37  
    38 The `wysiwyg` view will alter the interpretation of the Trac processors `{{{#!th ... }}}` or `{{{#!td ... }}}` in the table.[[BR]] 
    39 To keep a preview, you can tick the box `edit side-by-side` at top right of the editing frame. It will part your screen with the editing view on the left and the preview on the right so you can control your changes. If you get by default the 'wysiwyg' view, this is due to your last editing work and can be changed in a simple manner. 
     35{{{#!div class="important" 
     36The informations inside the form fields and this wiki page itself are stored in 2 separate databases. As a consequence, there is absolutely no risk to make any modification in the page itself as long as you don't change `{{{TracForm ... }}}` processors.[[BR]] 
     37If you edit it in a classical way, use `textearea` instead of `wysiwyg` view because it doesn't handle well the Trac processors `{{{#!th ... }}}` or `{{{#!td ... }}}`. To keep a preview, you can tick the box `edit side-by-side` at top right of the editing frame. Your default view depends on your last editing work so can be changed in a simple manner. 
     38}}} 
    4039 
    4140== Summary [=#summary]