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:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10121 of page Voting approaches can successfully be applied to participatory planning of forestry patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10120 of page Users preferred enhanced functionality rather than useability patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10119 of page Use of the DSS has been considered successful by the participating organizations, even though it has patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10118 of page Threshold values and weights used in a decision process have strong effect on the results patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10117 of page The use of the DSS improved communication among the planning team by providing a framework of the patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10116 of page The use of EMDS allowed the planning team to identify priority area for restoration treatments that patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10115 of page The software did not provide much support for formatting of the outputs in a format that could be patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10114 of page The scope of the modeling project can change significantly during the project patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10113 of page The kinds of DSS traditionally used to calculate timber harvest levels are now being used to model patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10112 of page The analysis team used internal prototyping, which helped train the staff and identify possible patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10111 of page The DSS usage enabled the planning team to measure the achievement of the restoration goals patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10110 of page The DSS models built must match the knowledge of the local forest managers, so the ability for local patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10109 of page The DSS gave the forest manager the opportunity to experiment how their emphasis towards certain patrolled
- 07:06, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10108 of page Students studying forest management planning procedures and processes were very useful ‘guinea pigs’ patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10107 of page Spatial variation between regions led to the development of different regional models, which led to patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10106 of page SIPAFIT sub-systems have been useful in training activities, and can be very useful to explain and patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10105 of page SIPAFIT can act sometimes as a referee to settle arguments among experts, users and stakeholders patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10104 of page Running the DSS required special skills, therefore the local planning team required considerable patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10103 of page Results are always strongly dependent on the quality of the underlying data patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10102 of page Requirement of specialized skills can discourage some potential users patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10101 of page Provide missing help/documentation service patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10100 of page Projection of stand development increases knowledge base patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10099 of page Pareto Frontier Techniques are useful for multi-criteria forest management planning patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10098 of page Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10097 of page Need of a moderator function patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10096 of page Model building was rapid, it was assembling the data that took by far the most time patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10095 of page Lack of proper documentation and support services (manual, website, etc) can severely limit the patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10094 of page Growth and Yield models are a key component of forest DSS patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10093 of page From a management perspective, to avoid the complication of testing something new, the models used patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10092 of page Forest managers have to analyze how their forest management interventions effect the landscape patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10091 of page Enlarged decision space patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10090 of page Enlarge the decision space by generating a large set of potential management alternatives patrolled
- 07:05, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10089 of page Embedding a DSS in a GIS software allows obtaining information at different spatial scales using the patrolled
- 07:03, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10088 of page Despite the widely use and acceptance of the DSS there was still a lack of expertise to patrolled
- 07:03, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10087 of page DSS helped document and apply decision criteria consistently, and therefore produced a more patrolled
- 07:02, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10086 of page Analysis at the landscape level allowed the integration of concerns about multiple resources as well patrolled
- 06:52, 30 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10085 of page An iterative process of presenting results to subject matter experts enabled them to better patrolled
- 07:14, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10068 of page As the core of forest DSS are models describing the development of trees and stands (growth and patrolled
- 07:13, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10067 of page Enabling the analyses of several ecosystem services (timber and non-timber resources) in one and the patrolled
- 07:12, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10066 of page It would have been better to involve some end users at earlier stages of the system development patrolled
- 07:11, 29 July 2013 SeanGordon (Talk | contribs) automatically marked revision 10065 of page Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use patrolled
- 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
