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)- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9760 of page Metodology and results are transparent and easy-to-share to non-expert stakeholders patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9759 of page Actor Network Theory provides a suitable lens for exploring both technical and human aspects of DSS institutionalization in the forestry domain patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9758 of page Biomasfor allows to obtain information at different spatial scale patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9757 of page Requirement of specialized skills can discourage some potential users patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9756 of page The scope of the modeling project can change significantly during the project patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9755 of page The kinds of DSS traditionally used to calculate timber harvest levels are now being used to model patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9754 of page Need of a moderator function patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9753 of page Need for new models for the later use of a tool patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9752 of page The tracing of the actor network supported the identification of the key actors influencing the collaborative DSS implementation and institutionalization patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9751 of page The tracing of the current actor network interactions made the group realize that they need a different kind of stakeholders from what they previously thought patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9750 of page The analysis of the actor network interactions allowed to identify the criticalities to be solved in order to develop the collaborative process patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9749 of page Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9748 of page Projection of stand development increases knowledge base patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9747 of page Provide missing help/documentation service patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9746 of page An iterative process of presenting results to subject matter experts enabled them to better patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9745 of page Enlarged decision space patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9744 of page The choice to develop the system in an Excel environment was based on the status of computer patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9743 of page Plan the system architecture based on a broad view of future possibilities patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9742 of page Provide a simple version of the DSS, which new users can try out and learn quickly patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9741 of page Results are always strongly dependent on the quality of the underlying data patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9740 of page The user has to be aware of the possibly large impact that the chosen land indicators and threshold patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9739 of page Neighbourhood interrelations should be included in the generator patrolled
- 19:33, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9738 of page Students studying forest management planning procedures and processes were very useful ‘guinea pigs’ patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9737 of page It is necessary to know which data will be use as variables in the models before designing the DSS patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9736 of page Use of the DSS has been considered successful by the participating organizations, even though it has patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9735 of page Voting approaches can successfully be applied to participatory planning of forestry patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9734 of page The software did not provide much support for formatting of the outputs in a format that could be patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9733 of page Provide procedures and structure for complete data flow patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9732 of page From a management perspective, to avoid the complication of testing something new, the models used patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9731 of page Despite the widely use and acceptance of the DSS there was still a lack of expertise to patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9730 of page The DSS models built must match the knowledge of the local forest managers, so the ability for local patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9729 of page Running the DSS required special skills, therefore the local planning team required considerable patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9728 of page Enabling the analyses of several ecosystem services (timber and non-timber resources) in one and the patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9727 of page Group participation with knowledgeable people is a good way to ensure that the decision hierarchy is patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9726 of page Providing procedures and structure for data flow from selection of field sample, performing field patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9725 of page As the core of forest DSS are models describing the development of trees and stands (growth and patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9724 of page Getting joint funding from both the forest and environmental sectors can be a successfull for patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9723 of page Threshold values and weights used in a decision process have strong effect on the results patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9722 of page Visualization of the preliminary actor network made the people explicity include the DSS in a planning process. patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9721 of page The analysis team used internal prototyping, which helped train the staff and identify possible patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9720 of page DSS helped document and apply decision criteria consistently, and therefore produced a more patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9719 of page Afforestion and deforestation options should be included in the management options patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9718 of page A more informative output should be generated with clear graphs and maps indicating long-term patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9717 of page Enabling the analyses of several ecosystem services patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9716 of page End user engagement throughout the development and deployment cycle is very important patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9715 of page Model building was rapid, it was assembling the data that took by far the most time patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9714 of page Spatial variation between regions led to the development of different regional models, which led to patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9713 of page Embedding a DSS in a GIS software allows obtaining information at different spatial scales using the patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9712 of page Stakeholder involvement patrolled
- 19:32, 2 May 2013 SeanGordon (Talk | contribs) automatically marked revision 9711 of page Use of adequate DSS development methodology patrolled
