Archive/IMAGE3.0/Discussion items: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* Use the term "overview" for the schematic overviews. use summary in other cases | * 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 | * 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=== | ===Welcome page=== | ||
Revision as of 09:17, 25 July 2013
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.
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;
- The policymakers
- Modellers
- Interested laymen (students, readers of reports, etc)
Component Pages
The headers in the infobox:
- Application => Project/applications
- IMAGE models=>related IMAGE models
Assumptions: What are they exactly. Give some more information on assumptions. Can be done in the description ?
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 baslines 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