Publication process: Difference between revisions

From IMAGE
Jump to navigation Jump to search
 
(32 intermediate revisions by the same user not shown)
Line 3: Line 3:
* External wiki: This is the publishable part of the internal wiki and will be accessible for the outside world via a PBL URL.
* External wiki: This is the publishable part of the internal wiki and will be accessible for the outside world via a PBL URL.


== INFO ==
== The basics ==
CurrentFrameworkVersion: versie nummer voor de hele wiki
*'''CurrentVersion''': This is the version number of a page, given for each page individually
CurrentVersion: versie nummer per pagina
*'''CurrentFrameworkVersion''': This is the version number of the '''Wiki as a whole''', which is only increased when a new release is started.
 
*'''Approved/ unapproved pages''': The external wiki will only show approved pages. An unapproved page will be put to approved by the editors after the approval procedure.  
[[http://www.mediawiki.org/wiki/Extension:Approved_Revs Approved Revs]]
*'''Approve-revisions-permission''': This permission allows you to look at pages which have the unapproved status. On default the latest approved page will be shown, but with this permission a link will be shown which gives access to the latest/unapproved version of the page. This permission is only given to people who have a user-login.  
Approverevisions' permission alleen voor alle pbl-ers, hiermee kan je kijken naar pagina’s die nog unaproved zijn (dit is dus de laatste versie).
*'''Automatic approval''': On default each change will automatically be approved, and is thereby directly visible for external people. Automatic approvals will not be applied to new pages and pages which are actively put to the unapproved status.
 
De eigenschap $egApprovedRevsAutomaticApprovals  staat op true. Hiermee worden alle wijzigingen automatisch op approved gezet en daarmee na een overdracht dus direct zichtbaar voor externe mensen.


== How to handle changes ==
== How to handle changes ==
There are several situations with different solutions:
There are several situations with different solutions:
#'''Minor text change'''
#Minor text change, either a correction or enhancement
#*May be a correction or enhancement: Enter the changes in the wiki.
##Enter the changes in the wiki.
#*No increasing CurrentVersion number and no approvement procedure
## Do not increase the CurrentVersion number and do not apply the approvement procedure
#'''Small adaptations to model components, substantial rewriting of a description or new pages'''
#Small adaptations to model components, substantial rewriting of a description or the creation of new pages
#*Tekst aanpassen
##Adjust the text
#*Na eerste save; de huidige (werk)- versie via the history tab op ‘unaproved’zetten.
##After saving the first time; put the version you are currently working on to 'unapproved' via the history tab on the wiki-bar. All changes after this adjustment will stay on 'unapproved'
#*Alle volgende wijzigingen blijven dan unaproved
## Do this for the whole set of pages where you want to make adjustments. When all changes in this set of pages are done:
#*Doe dit voor de hele set van pagina’s die je moet wijzigen.
##Start the approvement procedure:  
#*Wanneer alle wijzigingen binnen deze set klaar zijn:
##*Check the combined set of changed components and individual pages
#**Start approvement procedure:  
##* '''Increase the Currentversion number of each component you have changed (increase per component, not per page) '''
#**Check de gebundelde gewijzigde componenten en losse pagina’s
##*Editorial step for Editors:
#**Currentversion nummer ophogen per component (niet per pagina) waar je wijziging aanbrengt
##**Check the page and apply the 'approved' status when done
#**Redactionele slag:
#**Editing & aprove status toepassen
* If a page has no approved revision (this of course includes new pages), automatic approvals will not be applied.
* Current version nummer eigenschap toevoegen
* Pakt bij de hij bij de overdracht  de laatste versie of de ‘aproved’versie? Waarschijnlijk geen probleem want externe personen hebben  geen RevisionApprovalPermission en zien de laatste versie dus niet?! (moet dan wel de laaste ‘aproved’versie zien/geen lege pagina)
 
# Substantial change resulting in a new version: When making a substantial change to your model by adding a submodule or changing the conceptual model, ****
 
 
 
 
#Nieuwe release:
#*Maak een archief versie ( evt. in html/pdf vorm, liefst pdf vorm want dan verwachten mensen niet dat de links werken) zie extenties: collection en pdfbook
#*De hele wiki op unaproved zetten ($egApprovedRevsAutomaticApprovals = false;)
#*Wijzigingen slechts op het eind allemaal tegelijk approven.
 
 
 
 
 


[[Category:Help]]
[[Category:Help]]

Latest revision as of 15:34, 13 January 2014

There is an internal PBL wiki and an external wiki. The external wiki is a subset of the internal wiki and is meant to be viewed by webusers. The implementation will probably (discussion item) be by installing one wiki inside the firewall and one wiki outside the firewall. The external wiki will be filled by an import of pages from the internal wiki and periodically updated.

  • Internal wiki: This wiki is visible for PBL employees and external people that can login (?). In principle all contentpages are visible for all these people. However there will be a difference between viewers, writers and administrators, with more options available in this sequence. Viewers can view and discuss; writers will have an extended menu with functions to add content and may edit pages; administrators can change the structure and maintain user rights and use other maintenance functions.
  • External wiki: This is the publishable part of the internal wiki and will be accessible for the outside world via a PBL URL.

The basics

  • CurrentVersion: This is the version number of a page, given for each page individually
  • CurrentFrameworkVersion: This is the version number of the Wiki as a whole, which is only increased when a new release is started.
  • Approved/ unapproved pages: The external wiki will only show approved pages. An unapproved page will be put to approved by the editors after the approval procedure.
  • Approve-revisions-permission: This permission allows you to look at pages which have the unapproved status. On default the latest approved page will be shown, but with this permission a link will be shown which gives access to the latest/unapproved version of the page. This permission is only given to people who have a user-login.
  • Automatic approval: On default each change will automatically be approved, and is thereby directly visible for external people. Automatic approvals will not be applied to new pages and pages which are actively put to the unapproved status.

How to handle changes

There are several situations with different solutions:

  1. Minor text change, either a correction or enhancement
    1. Enter the changes in the wiki.
    2. Do not increase the CurrentVersion number and do not apply the approvement procedure
  2. Small adaptations to model components, substantial rewriting of a description or the creation of new pages
    1. Adjust the text
    2. After saving the first time; put the version you are currently working on to 'unapproved' via the history tab on the wiki-bar. All changes after this adjustment will stay on 'unapproved'
    3. Do this for the whole set of pages where you want to make adjustments. When all changes in this set of pages are done:
    4. Start the approvement procedure:
      • Check the combined set of changed components and individual pages
      • Increase the Currentversion number of each component you have changed (increase per component, not per page)
      • Editorial step for Editors:
        • Check the page and apply the 'approved' status when done