Archive/IMAGE3.0/Discussion items

From IMAGE
Jump to navigation Jump to search

This page contains a selection of items concerning the maintenance, use and usability of this wiki that needs discussion. Use concentrates on external use and usability on creating and managing content on the wiki.

Reminderlist

  • Some fields might be hidden for the editors, like component code.
  • There is no popup available with the current version, maybe link the files, like flowcharts to the information page of the file. The chart must be displayed in full glory then....
  • Computer model form: Relation to framework determines some fields. Implement this in the form. Use of modeltype and list of values...
  • Researh organisation autocomplete and check all terms used here. Research organisation is added automatically
  • Acronyms: decide how to
  • check concepts and use

Overdracht

Overzetten van de systemen naar PBL en kijken of het allemaal werkt. Kennisoverdracht:

  • waar wordt de browse data selectie van categorieen geregeld: bij de categorie-pagina kun je aangeven, dan wordt de categorie niet getoond.
  • Hoe gaan we de intern naar extern regelen na initiele opstartvulling? Export va pagina"s ? Hoe gaat dat met ons on hold mechanisme: weten we nog niet zeker. Wikibot en automatisch syncen? Export + import van pagina's? Gaan we over nadenken. Overleg met Jeen.
  • Kan er voor intern gebruik worden gemaakt van de eigen inlognaam en LDAP mechanisme: ja. Doen wij ook bij onze FreshWiki.
  • Rechtenbeheer.
    • Intern Iedereen mag kijken, sommigen schrijven. "Writer"
    • Extern iedereen mag kijken, niemand mag schrijven. "Viewer". Als het open moet worden, moet je dat in LocalSettings.php aanpassen.
  • de referentie procedure (hoe haal je een heleboel referenties tegelijkertijd van EndNote naar de wiki): Beschrijven en overdragen.
  • combineren met andere smw's: wikifarm is een mogelijkheid (let op: Lucene-search extensie moet worden aangepast om goed te werken).
    • themasites voor GISMO, Hyde zetten we die op.

Use

General remarks:

  • Use the term "overview" for the schematic overviews. use summary in other cases
  • Components is a vague term: Pay attention to labels , column headers etc, to make the term and the different types more concrete
  • layout: There are different styles in use for simple 'objects' like references and ... whit a box at teh left side. Have a critical look and use same style for same type of pages.

Welcome page

What should this page contain?

  • It should lead the user to an entry that suits her best.
  • The navigation hints must start with an expressive label and be the same as the labels below the menu options): todo think about names
  • explanation should be short and attract the right person

There are three categories of users;

  1. The policymakers
  2. Modellers
  3. Interested laymen (students, readers of reports, etc)

Component Pages

The headers in the infobox:

  • Application => Project/applications
  • IMAGE models=>related IMAGE models

Probably it is sufficient to have a variable name, source or target and short description of the inputs and outputs ( so no purpose per model). That means that we only need a Variable (or Variableset) category and link the hasoutput and hasinput properties to the variables to create the input and output tables in the component .

The term Assumptions will be replaced by parameters. We need to change that in the structure.

Content pages

Ask Nicole: Is there a possibility to explod/implode on header level?

Overviews

We define three main overviews on components

  • for policymakers : a keyword-> policy intervention-> component overview: suggestion: derive keywords from vocabulaire(max 10 terms)
  • for modellers: the graph based on the dataflows , with components and variable sets
  • for laymen: the general component overview with the conceptual scheme. All components from the scheme should be accessable from here (Note drivers and emissions)

There are more overviews. These can be related and be accessed by making an overview structure: Each overview gets an description and related overviews and optional a picture(like conceptual scheme, venndiagram or thumbnail of table). At the end of an overview the related overviews will be shown and we can make a summary of the overviews.

New overviews:

  • Take the key policy questions (new attribute of components) and show them with the components ( maybe ordered by their type)
  • Graph of input output flows:


Uncertain: galery of baselines and policy figures

Usability

Items on forms, structure, templates etc.

Acronyms

  • Enter acronyms: inline or via an usefull form
  • Sometimes an acronym is also an wiki object, meaning there is (or shoukd be) already a page, for example TIMER isa Computer Model and a acronym. How to handle

Maintenance

  • How to install the wiki, external and internal and. Talk with Jeroen D. (CBO) and technical beheer (BPO).
  • how to regulate the rights
  • How to guarantee maintenance : gardeners and replacement
  • How to handle updates in the environment

Development

How to organize connected wiki applications, like data deliveries, scenariodevelopment, Variables info

Retrieved from "https://models.pbl.nl/index.php?title=Archive/IMAGE3.0/Discussion_items&oldid=5655"