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)- 07:10, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10064 of page Neighbourhood interrelations should be included in the generator patrolled
- 07:10, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10063 of page Provide procedures and structure for complete data flow patrolled
- 07:09, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10062 of page Providing procedures and structure for data flow from selection of field sample, performing field patrolled
- 07:08, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10061 of page The DSS models built must match the knowledge of the local forest managers, so the ability for local patrolled
- 07:07, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10060 of page The adoption of the collaborative learning method made possible to gradually select the conceptual patrolled
- 07:06, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10059 of page To compare the current and the past quantitative/qualitative parameters of the forest, great effort patrolled
- 07:06, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10058 of page To meet the needs of customer - the Forest Service - and to obtain satisfying results the patrolled
- 07:04, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10057 of page Users preferred enhanced functionality rather than useability patrolled
- 07:03, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10056 of page Using Actor Network Theory in the design stage can help in understanding the dynamism of the network patrolled
- 07:02, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10055 of page DSS allowed to explain better some technical concepts to non-professional stakeholders patrolled
- 07:00, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10054 of page From a management perspective, to avoid the complication of testing something new, the models used patrolled
- 06:59, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10053 of page Metodology and results are transparent and easy-to-share to non-expert stakeholders patrolled
- 06:58, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10052 of page Regular ongoing engagement helped maintain interest of users patrolled
- 06:31, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10051 of page The activation of an iterative process through periodical meetings permitted to all the stakeholders patrolled
- 06:26, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10050 of page The use of structured output (maps, tables and charts) makes the methodology and the results more patrolled
- 06:25, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10049 of page Need of a moderator function patrolled
- 06:22, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10048 of page The choice to develop the system in an Excel environment was based on the status of computer patrolled
- 04:57, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10046 of page Need of a moderator function patrolled
- 04:57, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10047 of page The choice to develop the system in an Excel environment was based on the status of computer patrolled
- 04:56, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10045 of page The use of structured output (maps, tables and charts) makes the methodology and the results more patrolled
- 04:56, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10044 of page The activation of an iterative process through periodical meetings permitted to all the stakeholders patrolled
- 04:56, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10040 of page DSS allowed to explain better some technical concepts to non-professional stakeholders patrolled
- 04:56, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10041 of page From a management perspective, to avoid the complication of testing something new, the models used patrolled
- 04:56, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10042 of page Metodology and results are transparent and easy-to-share to non-expert stakeholders patrolled
- 04:56, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10043 of page Regular ongoing engagement helped maintain interest of users patrolled
- 04:51, 29 July 2013 SeanGordon (Talk | contribs) deleted page System requirement and design (moved to Has DSS development stage)
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10037 of page To meet the needs of customer - the Forest Service - and to obtain satisfying results the patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10038 of page Users preferred enhanced functionality rather than useability patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10039 of page Using Actor Network Theory in the design stage can help in understanding the dynamism of the network patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10033 of page Providing procedures and structure for data flow from selection of field sample, performing field patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10034 of page The DSS models built must match the knowledge of the local forest managers, so the ability for local patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10035 of page The adoption of the collaborative learning method made possible to gradually select the conceptual patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10036 of page To compare the current and the past quantitative/qualitative parameters of the forest, great effort patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10032 of page Provide procedures and structure for complete data flow patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10031 of page Neighbourhood interrelations should be included in the generator patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10027 of page As the core of forest DSS are models describing the development of trees and stands (growth and patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10028 of page Enabling the analyses of several ecosystem services (timber and non-timber resources) in one and the patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10029 of page It would have been better to involve some end users at earlier stages of the system development patrolled
- 04:50, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10030 of page Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use patrolled
- 03:08, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10026 of page A financial analysis is an important component in the discussion about the preferences of different patrolled
- 02:57, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10025 of page Form:Lesson patrolled
- 02:53, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10024 of page Form:Case patrolled
- 02:40, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10023 of page Form:Case patrolled
- 02:25, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10022 of page Form:Case patrolled
- 02:15, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10021 of page Adoption patrolled
- 02:14, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10020 of page Installation patrolled
- 02:13, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10019 of page Dissemination patrolled
- 02:13, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10018 of page Dissemination patrolled
- 02:12, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10017 of page Testing patrolled
- 02:11, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10016 of page Design patrolled
