All public logs
From COST Action FP0804: FORSYS
Combined display of all available logs of COST Action FP0804: FORSYS. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).
(newest | oldest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500)- 06:58, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10527 of page Stakeholder involvement patrolled
- 06:57, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10526 of page Stakeholder involvement in DSS design patrolled
- 06:57, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10525 of page Use of adequate DSS development methodology patrolled
- 06:57, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10524 of page Need for new models for the later use of a tool patrolled
- 06:54, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10523 of page Need for new models for the later use of a tool patrolled
- 06:53, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10522 of page Use of adequate DSS development methodology patrolled
- 06:52, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10521 of page Stakeholder involvement in DSS design patrolled
- 06:52, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10520 of page Stakeholder involvement patrolled
- 06:52, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10519 of page Actor Network Theory provides a suitable lens for exploring both technical and human aspects of DSS institutionalization in the forestry domain patrolled
- 06:51, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10518 of page Decision criteria beyond the state of the ecosystem (for example, social values fire risk, economic patrolled
- 06:49, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10517 of page The very easy user-friendly interface of the software and the clearness of method can be exploited patrolled
- 06:48, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10516 of page The development of large and enduring systems requires a long term approach patrolled
- 06:46, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10515 of page Lack of proper documentation and support services (manual, website, etc) can severely limit the patrolled
- 06:46, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10514 of page The choice to develop the system in an Excel environment was based on the status of computer patrolled
- 06:45, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10513 of page Plan the system architecture based on a broad view of future possibilities patrolled
- 06:44, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10512 of page The scope of the modeling project can change significantly during the project patrolled
- 06:43, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10511 of page The use of structured output (maps, tables and charts) makes the methodology and the results more patrolled
- 05:19, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10510 of page It is necessary to know which data will be use as variables in the models before designing the DSS patrolled
- 05:17, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10509 of page Provide missing help-documentation service patrolled
- 05:16, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10508 of page The definition of standardized and specific criteria for selecting and zoning forest compartment patrolled
- 05:16, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10507 of page An optimisation module comparing alternative scenarios based on multi-criteria analysis should be patrolled
- 05:15, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10506 of page A financial analysis is an important component in the discussion about the preferences of different patrolled
- 05:15, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10505 of page DSS can help in varying the treatment according to more than one forest function patrolled
- 05:14, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10504 of page Embedding a DSS in a GIS software allows obtaining information at different spatial scales using the patrolled
- 05:13, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10503 of page To compare the current and the past quantitative-qualitative parameters of the forest, great effort patrolled
- 05:12, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10502 of page The fact that ProgettoBosco is conceived according to the criteria and indicators of sustainable patrolled
- 05:11, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10501 of page Afforestion and deforestation options should be included in the management options patrolled
- 05:09, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10500 of page It should be possible to specify the rotation time of a species not only by age but also by target patrolled
- 05:08, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10499 of page Neighbourhood interrelations should be included in the generator patrolled
- 02:52, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10498 of page Provide a simple version of the DSS, which new users can try out and learn quickly patrolled
- 02:48, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10497 of page Need of flexibilization of analytical tools - no overdesigned tool that provides too much features for the use patrolled
- 02:48, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10496 of page Need of flexibilization of analytical tools - no overdesigned tool that provides too much features for the use patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10495 of page Running the DSS required special skills, therefore the local planning team required considerable patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10494 of page SIPAFIT sub-systems have been useful in training activities, and can be very useful to explain and patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10493 of page Interpretative case studies can help reduce the gap between research and practice patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10492 of page Use of the DSS has been considered successful by the participating organizations, even though it has patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10491 of page Visualization of the preliminary actor network made the people explicity include the DSS in a planning process patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10490 of page End user engagement throughout the development and deployment cycle is very important patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10489 of page DSS allowed to explain better some technical concepts to non-professional stakeholders patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10488 of page The DSS gave the forest manager the opportunity to experiment how their emphasis towards certain patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10487 of page The use of the DSS improved communication among the planning team by providing a framework of the patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10486 of page DSS helped document and apply decision criteria consistently, and therefore produced a more patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10485 of page An iterative process of presenting results to subject matter experts enabled them to better patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10484 of page Spatial variation between regions led to the development of different regional models, which led to patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10483 of page The analysis team used internal prototyping, which helped train the staff and identify possible patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10482 of page The software did not provide much support for formatting of the outputs in a format that could be patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10481 of page The activation of an iterative process through periodical meetings permitted to all the stakeholders patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10480 of page Stakeholders contribution in ranking forest functions patrolled
- 02:36, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10479 of page Need of a moderator function patrolled
- 02:35, 9 September 2013 SeanGordon (Talk | contribs) automatically marked revision 10478 of page Group participation with knowledgeable people is a good way to ensure that the decision hierarchy is patrolled
