Talk:Guidebook: Difference between revisions

From Opasnet
Jump to navigation Jump to search
(process and product descriptions within the toolbox - incomplete)
No edit summary
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Article templates -- [[User:Mikko Pohjola|Mikko Pohjola]] 14:56, 17 January 2008 (EET) ==
'''Brief guidance to the guidebook page content


The guidance system will be composed of pages describing processes relevant to risk/impact assessment, pages describing the kinds of products that these processes (are intended to) produce (and the kinds of products that can be used in/by these processes?). In addition, the guidebook content can be complemented with some so-called ''glue pages'', which could contain information that is not easily captured in the process/product structure. <span style="color:red;"> ...which are on the top-level of the Guidebook and give a short overview over the topic linking to the respective process and product articles. </span> An example of a glue page is [[Guidebook]], which is the ''starting page'' of the guidebook and has a ''table of contents'' -like structure and perhaps some introductory text. In addition to the above-mentioned contents, the guidebook will also include descriptions of the context and the theoretical foundations of what the rest of the guidebook describes.
The [[Guidebook]] page is a table of contents for the actual Intarese guidebook, which has dozens of separate pages, linked to on the Guidebook page. A typical item in the table of contents looks like this:


Processess are events, or composites of events, in which various pieces of input information are manipulated and formed into new products of information; the output. A process is “something you do”. Processes relevant to risk/impact assessment are captured into the guidance system as descriptions of these processes, possibly also including the tools relevant to the process and descriptions of how to manage the process. A process object can be e.g. in the form of a method description (calculation, formal discussion, etc.) describing also the tools, models and other means that are used in applying the method.
;Method article name WPX.X: Purpose of the method. | Categories: [[:Category:Method]] | Tools: [[Reporting tool]]
* Method article name is the name of the method to be described, including the link to the actual page.
* WPX.X is the workpackage is that is responsible for producing the article.
* Purpose is the essence of the method: why is it performed. The whole content of the article is conditional to the purpose of the method.
* Categories link to pages that have applied this method. Usually they are products that are produced by using the method.
* Tools are practical software or other tools that make it easier to apply the method.


Product objects in the guidebook are pieces of information that describe what '''kinds''' of products are produced by the risk/impact processes (and/or what '''kinds''' of products can be used in/by them?). The actual outputs of the processes, the products themselves, do not belong to the guidebook, but instead to the [[Data center|data center]].


Process and product descriptions in the guidebook are structured objects, i.e. they have a pre-defined format (see the template descriptions below). The theoretical and contextual descriptions are unstructured, i.e. freely formed, information.
The following types of links are useful in the guidebook:
* <nowiki>[http:www.site.org/page link] Link to an external source</nowiki>
* <nowiki>[[Link|Link name]] link to a page in Heande main namespace ("Link name" shown on the page)</nowiki>
* <nowiki>[[Help:Link|]] Link to a page in another namespace (the namespace is not shown)</nowiki>
* <nowiki>[[:intarese:Link|]] link to a page in Intarese wiki</nowiki>
* <nowiki>[[:en:Link|]] link to a page in the English Wikipedia</nowiki>


Most objects belonging to the guidebook are process descriptions.


'''Template: process description
==Processes and products in guidebook==


;Summary: The summary of a process is a very short overview of the process, and may contain all types of information that are considered relevant for this specific process (max words: 250?)
{{discussion
;Name: The name of the process should be unique (there should not be two objects (processes, products or product descriptions) with identical names). The name should be chosen so that it is descriptive, unambiguous and not easily confused with other processes, products or product descriptions. (max words: 20?)
|Statements= All content in the guidebook, excluding theoretical foundations and glue pages, should be process descriptions
;Purpose: (This is the same as Scope in the general object attribute list.) The general purpose of every process is to manipulate information in aim to produce a particular information product. The process-specific purpose describes the intended product of this particular process. This should contain all relevant information needed to distinguish the process from other processes. (max words: 400?)
|Resolution=
;Structure of the process: (This is the same as the Result (of the process description) in the general object attribute list.) The result section has three sub-attributes.  (max words: 3000?)
|Argumentation =
:;Input format: The input data, variable or parameter types, their syntax, and other relevant information is described here.
{{defend|2|On the level of actual assessment there are the processes themselves and the products (structured descriptions of reality) themselves. A guidebook should be about the processes and the about the products, i.e. it should contain process descriptions and product descriptions. Because the types of products that different processes produce are already described under the ''structure of the process/output format'' attribute, there is no need to make separate product descriptions.|--[[User:Mikko Pohjola|Mikko Pohjola]] 13:15, 18 January 2008 (EET)}}
:;Procedure: The actual process – how it works and how to do – is described here. It consists of e.g. the mathematical formula to calculate the result. The procedure uses algebra or other explicit methods if possible.  
::;Management: A complex process may require that also the management process of the procedure is described. The procedure may for example be a mathematical algorithm. The management process is a computer software that runs the algorithm, so that when you have the software, the management is a trivial task. If you do not have the management process - well, good luck to you and your calculator. So, actually models and software are procedures that have the management process packed into the same neat package. An other example of a management process is a guidance by the U.S.EPA about how to plan and organise for stakeholder meetings. The actual procedure here is to obtain information and feedback from the stakeholders.
:; Output format: shortly describes the format of the product of the process, which should fulfil the purpose as described in the scope. It furthermore links – if applicable – to the product object.
;Rationale: (This is the same as the Definition (of the process description) in the general object attribute list.) This attribute answers to the following questions: What is known about a good process for this purpose? How do you know that the procedure described is good? (max words: 2000)
;See also: See also links to pages (both internal guidebook pages and external) which relate to the process subject. All subjects that could be relevant for readers of this page can be listed here. (max links: 20?)
;References: All references, as used in the texts above. (max references: 30?)


{{attack|3|When there is a clear 1 – 1 relationship between process and product (eg DALY process – DALY product), we will only ask for description of either process or product, in order to avoid confusion. In most cases, the process is the important object that needs to be described, and in practice the methods etc. described in the guidebook will be process descriptions. When there is no such direct 1 – 1 relationship, we will ask for separate description of process and product. An example of this is meta-analysis (process), and the exposure response function (ERF) (product). Even though the process of meta analysis can lead to an estimation of the ERF, the meta analysis can also lead to an estimation of another product (e.g. severity weight), and an ERF (the product) can also be derived from another process (e.g. expert judgement).|--[[User:Anne.knol | Anne Knol]]}}


'''Template: product description
{{comment|1|I think, the processes and products should be put together and not separated too much.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 17:29, 14 January 2008 (EET)}}
{{comment|4|Well, it seems there are no products as such... At least not in the methods-parts. maybe in the Intarese-Framework-Part but that's fine because one special framework is described there and the methods in the methods-chapters are generic for all frameworks.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 09:31, 18 March 2008 (EET)}}
}}


Products, describing real-world entities ("zero meta level") and being products of the assessment (sub-)processes, are located in the  data centre. Product descriptions, to the extent that they are necessary, are included in the guidebook as universal products.
==Frameworks in guidebook==


{{discussion
|Statements= Guidebook contains descriptions of a general assessment framework and the Intarese framework
|Resolution= Accepted.
|Argumentation =
{{attack_invalid|1|Why is cost-benefit analysis "another framework" in the guidebook?|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 10:27, 17 January 2008 (EET)}}
:{{attack|2|Intarese framework is not limited to CBA, and therefore CBA is another framework with a more limited scope.|--[[User:Jouni|Jouni]] 00:41, 8 March 2008 (EET)}}
}}


'''Template: product
==Tools in guidebook==


;Summary: The summary of a product is a very short description of the product, and may contain all types of information that are considered relevant for this specific product (max words: 250?)
{{discussion
;Name: The name of the product should be unique (there should not be two products or processes with identical names). The name should be chosen so that it is descriptive, unambiguous and not easily confused with other products or processes. (max words: 20?)
|Statements= Tools are operational descriptions of managing particular sub-processes and they are mostly described together with the particular methods they relate to
;Scope: The scope of the product gives a research question that this product object aims to answer. The scope includes – if applicable – its spatial, temporal, or other limits (system boundaries). A product object may also be a generic one applying to any spatio-temporal locations. Whether these are just variables, and how they are used in the Guidebook is under study. (max words: 400?)
|Resolution=
;Definition: The definition describes the data and reasoning that tells us what the answer to the question in the scope is. In the case of a variable, it has four sub-attributes:
|Argumentation =
:; Data: What data or observations are available about this object?
{{comment|1|Result database is described as a tool in two places|--[[User:Jouni|Jouni]] 16:22, 30 January 2008 (EET)}}
:; Causality: What variables affect the result of this object when they change (i.e., which variables are causally related to this one)?
}}
:; Unit: What is the measurement unit of the result?
;: Formula: How is the result derived or computed?.
:Definition may link to the process(es) that lead to this product, explaining shortly why these processes are relevant. (max words: 3000?)
;Results: Contains the answer to the question presented in the scope. Usually the text is short (max 500 words), but the result tables or figures may be extensive; there is no upper limit.
;See also: See also links to pages (both internal resources centre pages and external) which relate to the product. All subjects that could be relevant for readers of this page can be listed here. (max links: 20?)
;References: All references, as used in the texts above. (max references: 30?)


==Step-specific methods==


'''Practical information for both templates
{{discussion
|Statements= Step-specific methods are all modelling methods
|Resolution= Not accepted.
|Argumentation =
{{attack|1|Step-specific information to be included in an assessment can also be obtained by other means than modeling, e.g. direct observation or measurement. Of course, if we use modeling in a very broad sense to mean all kinds of information collection and manipulation for the purpose of synthesizing it as a part of a particular assessment, the term is acceptable. Restricting the guidebook to cover only modeling methods related to specific in the way it is commonly understood would be too constrained.|--[[User:Mikko Pohjola|Mikko Pohjola]] 13:01, 1 February 2008 (EET)}}
:{{defend|2|I agree to Mikkos comment and we should also include other means, e.g. biomonitoring.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 09:55, 7 March 2008 (EET)}}
{{comment|3|But, is it still a process to collect and provide biomonitorindata?|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 10:35, 7 March 2008 (EET)}}
:{{defend|4|Yes, these are processes that should be described in the Guidebook.|--[[User:Jouni|Jouni]] 00:41, 8 March 2008 (EET)}}
}}


{{comment|#(number): |General information on how the sentences should be structured etc. (see also my first version and the project that RIVM already have conducted.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 12:50, 14 January 2008 (EET)}}
==Information processing methods by sub-processes==


Any section may contain a "more" button to more detailed information that is hidden by default to increase readability. The content is still directly relevant for the section. In addition, if there is a lot of further background information available about the object, e.g. its history, current practice, etc.) which is useful but not required to utilise the object, a background article can be created and linked to from the object. A background article can be freely structured, but an established encyclopedia article structure is recommended.
{{discussion
|Statements= Information processing methods (other than assessment process management methods) should be separated into information collection and information synthesis methods
|Resolution= Accepted.
|Argumentation =
{{defend|1|Making a distinction between processes that relate to collecting, manipulating or creating information in a non-predefined format (as defined by the general assessment framework) and processes that relate to synthesizing the information into the predefined format could bring some clarity to understanding their roles in relation to the products of the assessment as well as their mutual roles in the overall assessment process.|--[[User:Mikko Pohjola|Mikko Pohjola]] 13:41, 1 February 2008 (EET)}}
:{{defend|2|I agree. How/where would you do that? will you do that? we could add (later in the Guidebook) the picture you presented in Kuopio with the information processes and the difference of synthesising and manipulation.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 09:58, 7 March 2008 (EET)}}
}}


== Assessing uncertainty ==


'''Process/ product structure in Intarese
{{comment|1|Will a paragraph on uncertainty be at all relevant processes, e.g. emission calculation, ERFs etc.?|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 15:13, 11 February 2008 (EET)}}
:{{comment|2|Assessing uncertainty will be about the general concepts, and they will apply to all variables, including those that you mention.|--[[User:Jouni|Jouni]] 00:41, 8 March 2008 (EET)}}


Elements of the Intarese method as developed in SP1 relate to either a process, or a product, or both. The graph below gives an idea of processes and products as developed in the Intarese project (graph should be improved/updated, if we want to present such a graph!) . For all processes and products, information needs to be provided in the guidance system.  
{{attack|3|But the actual appliance of the general methods should be explained at the relevant processes. e.g. in emission calculation it would also say that the emission factor is more uncertain than the activities. or s.th. in that direction. s.th. specific for THIS purpose.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 09:28, 10 March 2008 (EET)}}


When there is a clear 1 – 1 relationship between process and product (eg DALY process – DALY product), we will only ask for description of either process or product, in order to avoid confusion. In most cases, the process is the important object that needs to be described in the method guidebook. When there is no such direct 1 – 1 relationship, we will ask for separate description of process and product. An example of this is the process meta analysis, and the product exposure response function (ERF). Even though the process of meta analysis can lead to an estimation of the ERF, the meta analysis can also lead to an estimation of another product (e.g. severity weight), and an ERF (the product) can also be derived from another process (e.g. expert judgement).
==Discussion on some particular page contents==


How should an article about disability-adjusted life years be structured? The question is not at all obvious, so the different options were tested in a [http://heande.pyrkilo.fi/heande/index.php?title=Heande:Guidebook_specification&oldid=3472 previous version of this page]. Only the conclusions are presented here.  
'''Assessment (universal product)
* Scope. What is the use purpose of an (impact) assessment? (To answer a policy information need) 3, 6, 12
*Definition
**What is an impact assessment
**Different assessments: HIA, RA, IA... 4-5 (possibly own articles)
:{{comment|4|This part describes the process of performing an impact assessment. It goes not into details about the methodologies|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:02, 14 January 2008 (EET)}} {{attack|#(number): |No, this is an overview.|--[[User:Jouni|Jouni]] 23:05, 15 January 2008 (EET)}}
 
'''Performing an impact assessment (process description:assessment framework) 10
*Scope: Purpose of making an impact assessment is to produce an assessment product.
{{comment|1|What would this be? A general purpose? something like policy consulting???|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:02, 14 January 2008 (EET)}}
*Definition
**General methodology 10 ({{comment|2|would be the same as the assessment framework? equals dimension "work environment" number 3.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:02, 14 January 2008 (EET)}})
**description of methodology used 11
*Result
**Inputs
**Procedure: Phases of an impact assessment 16
***Scoping an impact assessment 26
****Selecting indicators 50
***Applying general information
***Drawing a causal diagram 34 Links: [[Help:Causal diagram]] | Links to alternatives: Causal chain, impact pathway, DPSEEA, DPSIR
***: {{comment|3|Discussing with some colleagues here at USTUTT they said it would be good to describe the differences and communalities between causal chain, impact pathway approach, DPSEEA, DPSIR. Where would this belong to?|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:06, 14 January 2008 (EET)}}
***: {{comment|5|Perhaps these descriptions should be included in the links to the different alternatives? Ex give the differences and communalities between causal diagram and impact pathway in the linked section of impact pathway and so on?|--[[User:Kb|Kb]] 13:43, 18 January 2008 (EET)}}
***Designing variables
***Executing variables and analyses
***[[Reporting an assessment]]
**Outputs
 
'''Reporting an assessment (process description) 67
*Scope
*Definition: different approaches
*Result
**Reporting uncertainties 70, 73 (incl. qualitative and quantitative uncertainties)
 
'''Stakeholder involvement (process description) 68
 
Issue framing (process description:issue framing)
:{{comment|1|Where would be the boundaries to "process: assessment framework?"|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:02, 14 January 2008 (EET)}}
* Scope:
**Purpose, questions 27
**Indicator selection 50
**Boundaries 29
**Scenarios 30-33
*Definition
**Variables
 
'''Emission modelling (process description) 36-39
*Scope: purpose of emission modelling
*Definition: background
*Result:
**How to model 37
**Sectoral, spatial, and temporal resolution 38
**Uncertainties 39
 
'''Source-to-exposure modelling (process description) 40
*Scope: purpose
*Definition: Different types 41
*See also: pointers to resource centre 42
*Direct approach: measure data
({{comment|1|whatever. biomarkers, concentrations...|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:02, 14 January 2008 (EET)}})
*Uncertainties 43
 
'''Exposure-response function modelling (process description)
*Scope 45
*Definition:
**Different types 46
**How can they be derived? 47-48
**Uncertainties 49
 
'''Risk characterisation (process description) 51
*Scope
*Definition:
:{{comment|1|maybe we could summarise "DALYs / QUALYs and monetary valuation under "aggregation". But I don't know how to do this at the moment.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:02, 14 January 2008 (EET)}}
 
'''Disability-adjusted life year (process description) 52
*Scope
*Definition:
** How are they derived 54
**Alternatives 53
 
'''Monetary valuation (process description) 59
*Scope: Why do we need monetary values 60
*Definition
** Why do we choose monetary values and not utility points? 61
*Result
** How are monetary values derived 63
 
'''Uncertainty assessment (process description)  39, 43, 49, 58, 65, 69
*Scope: Purpose of uncertainty assessment
*Definition: Different approaches
**Qualitative methods eg pedigree matrix 71
**Quantitative methods 72-73
**When to use which method? 73
*Result
**Uncertainty of the result: parameter uncertainty
**Uncertainty of the definition: model uncertainty
**Uncertainty of the scope: relevance
 
'''Uncertainty tools (process: tool) 76
:{{attack|1|This does not belong into the Guidebook but it is good to keep it in mind.|--[[User:Alexandra Kuhn|Alexandra Kuhn]] 18:02, 14 January 2008 (EET)}}
 
'''Propagating uncertainties (process description) 72
*Scope
*Definition: approaches
**Monte Carlo 72
**Bayesian analysis 72
 
'''Impact assessment (product:assessment)
:{{attack|1|What should this be? Why should we have that? Scenarios etc. should be positioned under the process as the user should be explained how to build a scenario. |--[[User:Alexandra Kuhn|Alexandra Kuhn]] 17:26, 14 January 2008 (EET)}}
* Scope:
**Purpose, questions 27
**Boundaries 29
**Scenarios 30-33
*Definition
**Variables
**Analyses
*Result
**Results
**Conclusions
 
==The pages of the Pyrkilo guide 2==
 
The table contains all pages that are attached to the [[Intarese:Help:Pyrkilo guide 2]] page. The second column (where it should go) talks about where the current content of the page should go. It does not imply that the scopes of the old and the new page should be the same.
 
{| {{prettytable}}
|+In the Guidebook
!The location in Intarese (links redirect to the current page)
!Where it is now
|-
| [[Intarese:Help:Analysis tool]]||Tool:Analysis tool
|-
| [[Intarese:Help:Applying general information]] ||Method:Applying general information
|-
| [[Intarese:Help:Class]] ||Universal products:Class
|-
| [[Intarese:Help:Collaborative workspace]] ||Tool:Collaborative workspace
|-
| [[Intarese:Help:Designing variables]]|| Method:Designing variables
|-
| [[Intarese:Help:Dispute]]|| Method:Dealing with disputes
|-
| [[Intarese:Help:Drawing a causal diagram]]|| Method:Drawing a causal diagram
|-
| [[Intarese:Help:Executing variables]]|| Method:Executing variables
|-
| [[Intarese:Help:External model]]|| Tool:External model
|-
| [[Intarese:Help:Extracted model]]|| Tool:Extracted model
|-
| [[Intarese:Help:Issue framing tool]]|| Tool:Issue framing tool
|-
| [[Intarese:Help:Mass collaboration]]|| Method:Mass collaboration
|-
| [[Intarese:Help:Model extractor]]|| Tool:Extracted model tool
|-
| [[Intarese:Help:Object design tool]]|| Tool:Object design tool
|-
| [[Intarese:Help:Purpose of a risk assessment]]|| Method:Defining the purpose of an assessment
|-
| [[Intarese:Help:Reporting a risk assessment]]|| Method:Reporting an assessment
|-
| [[Intarese:Help:Reporting tool]]|| Tool:Reporting tool
|-
| [[Help:Result database]]|| Tool:Result database
|-
| [[Intarese:Help:Risk assessment structure]]|| Universal product:Assessment
|-
| [[Intarese:Help:Scoping a risk assessment]]|| Method:Scoping an assessment
|-
| [[Intarese:Help:The phases of a risk assessment]]|| Method:Performing an assessment
|-
| [[Intarese:Help:Universal information structure for risk assessment products]]|| Theoretical foundation:Universal products
|-
| [[Intarese:Help:Users of the pyrkilo method]]|| Method:Defining the users of an assessment
|-
| [[Intarese:Help:Variable]]|| Universal products:Variable
|-
| [[Intarese:Help:Variable transfer protocol]] || Method:Variable transfer protocol
|-
| [[Intarese:Help:Managing stakeholder involvement]]|| Method:Organizing stakeholder information
|-
| [[Intarese:Help:Variable definition]]|| Universal products:Variable
|-
| [[Intarese:Help:Plausibility tests]]|| Universal products:Variable
|-
| [[Intarese:Help:General properties of good risk assessments]]|| General assessment framework:Purpose and properties of good assessments
|-
| [[Intarese:Help:Performance]]|| General assessment framework:Evaluating assessment performance
|-
| [[Intarese:Help:Societal role of risk assessment]]|| General assessment framework:Societal context of assessments
|-
| [[Intarese:Help:Open participation in risk assessment]]|| Method:Participating in assessments
|-
| [[Intarese:Help:Risk assessment process]]|| Theoretical foundation:General processes
|-
| [[Intarese:Help:Uncertainty]]|| Method:Assessing uncertainty
|-
| [[Intarese:Help:Contributing to a discussion]]|| Method:Dealing with disputes
|}


In this ontology, the scope can be seen as a research question. The answer to this question is the result, and the definition tells how this result can be or was achieved.


{| {{prettytable}}
{| {{prettytable}}
!Approach
|+In other parts of the Guidance system
!Scope
!The location in Intarese (links redirect to the current page)
!Definition
!Where it is now
!Result
|-
|-----
| [[Intarese:Help:Causality]] ||Glossary:Causality
!Method (process description object)
|-
|'''DALY estimation''' is a process for measuring summarised burden of disease adding up increased mortality (years of life lost) and years lived with disability.<br>
| [[Intarese:Help:Decision variable]]|| Glossary:Decision variable
'''Purpose:''' DALY translates the impacts of diseases into life years based on their severity and duration, so that different diseases can be measured using a single currency, the life year. DALYs are based on disease-specific weights. (In contrast, QALYs evaluate the quality of life in a certain health state, not disease.) <br>
|-
'''The research question:''' What is a good way to estimate DALYs?
| [[Intarese:Help:Value judgement]]|| Glossary:Value judgement
|The definition contains the reasoning and motivation for calculating DALYs. It compares and discusses different alternatives. It contains links to methodology articles. It is also open for comments and further developments.
|The result describes the state-of-the-art method and formulas.<br>
Formula: DALY = life-years lost YLL (due to mortality) + life-years with disease YLD = YLL + number of disease cases * severity weight of the disease * the duration of the disease. The severity weights for diseases come from the variable [[Variable:Disability-adjusted weights for diseases]] The result is motivated by the content of the definition. Sub-attributes of the result include input (the upstream variables), procedure (the calculations), and output (format of the process output).
|}
|}


Conclusions:
#The process description (method) seems to be the most suitable object for DALY. The result attribute of the DALY process description describes the state-of-the-art procedure for estimating DALYs. If there is not a single best method, several methods can be described. The definition would then discuss the good and bad properties of each method, and their limitations. Usually a process is a general one, and therefore it will produce a large number of products for specific purposes in several risk assessments. There is no need to describe a "generalized product", as all general information is already described in the process description.
#The '''purpose''' of all process descriptions is to describe a good process for achieving the outcome described in the '''scope'''. Thus, scope belongs to the purpose of a particular process description object.
#The '''definition''' of a process description describes the information you need to understand whether some procedure is suitable and good for the purpose. The definition gives rationale for the procedure selected.
#To be precise, a process description is a product object that describes how to actually do the work. The doing itself is the process object, but that is something that vanishes as soon as the work is done and the product has been produced. We try to be precise when talking about the process or process description. However, we do not emphasize their differential nature (process vs. product, respectively), because the difference between doing and talking about doing is probably clear to the reader until someone tries to define that difference using metaphysical terminology.


Example: products and processes in the Intarese guidance system
{| {{prettytable}}
|+The new location not yet clear
!The current location in Intarese
!Where it should go
|-
| [[Intarese:Help:Copyright issues]]|| Method:Dealing with copyright issues
|-
| [[Intarese:Help:Data gateway]]|| Tool:Data gateway
|-
| [[Intarese:Help:Encyclopedia on environmental health]]|| Glossary:Encyclopedia on environmental health
|-
| [[Intarese:Help:Guidebook on risk assessment]]|| Glossary:Guidebook
|-
| [[Intarese:Help:Integrated resource platform]]|| Glossary:Resource platform
|-
| [[Intarese:Help:Open risk assessment (toolbox)]]|| Glossary:Open assessment
|-
| [[Intarese:Help:Pyrkilo method (summary)]]|| Glossary:Pyrkilo method
|}

Latest revision as of 11:18, 16 November 2009

Brief guidance to the guidebook page content

The Guidebook page is a table of contents for the actual Intarese guidebook, which has dozens of separate pages, linked to on the Guidebook page. A typical item in the table of contents looks like this:

Method article name WPX.X
Purpose of the method. | Categories: Category:Method | Tools: Reporting tool
  • Method article name is the name of the method to be described, including the link to the actual page.
  • WPX.X is the workpackage is that is responsible for producing the article.
  • Purpose is the essence of the method: why is it performed. The whole content of the article is conditional to the purpose of the method.
  • Categories link to pages that have applied this method. Usually they are products that are produced by using the method.
  • Tools are practical software or other tools that make it easier to apply the method.


The following types of links are useful in the guidebook:

  • [http:www.site.org/page link] Link to an external source
  • [[Link|Link name]] link to a page in Heande main namespace ("Link name" shown on the page)
  • [[Help:Link|]] Link to a page in another namespace (the namespace is not shown)
  • [[:intarese:Link|]] link to a page in Intarese wiki
  • [[:en:Link|]] link to a page in the English Wikipedia


Processes and products in guidebook

How to read discussions

Fact discussion: .
Opening statement: All content in the guidebook, excluding theoretical foundations and glue pages, should be process descriptions

Closing statement: Resolution not yet found.

(A closing statement, when resolved, should be updated to the main page.)

Argumentation:

←--2: . On the level of actual assessment there are the processes themselves and the products (structured descriptions of reality) themselves. A guidebook should be about the processes and the about the products, i.e. it should contain process descriptions and product descriptions. Because the types of products that different processes produce are already described under the structure of the process/output format attribute, there is no need to make separate product descriptions. --Mikko Pohjola 13:15, 18 January 2008 (EET) (type: truth; paradigms: science: defence)

⇤--3: . When there is a clear 1 – 1 relationship between process and product (eg DALY process – DALY product), we will only ask for description of either process or product, in order to avoid confusion. In most cases, the process is the important object that needs to be described, and in practice the methods etc. described in the guidebook will be process descriptions. When there is no such direct 1 – 1 relationship, we will ask for separate description of process and product. An example of this is meta-analysis (process), and the exposure response function (ERF) (product). Even though the process of meta analysis can lead to an estimation of the ERF, the meta analysis can also lead to an estimation of another product (e.g. severity weight), and an ERF (the product) can also be derived from another process (e.g. expert judgement). -- Anne Knol (type: truth; paradigms: science: attack)

----1: . I think, the processes and products should be put together and not separated too much. --Alexandra Kuhn 17:29, 14 January 2008 (EET) (type: truth; paradigms: science: comment)

----4: . Well, it seems there are no products as such... At least not in the methods-parts. maybe in the Intarese-Framework-Part but that's fine because one special framework is described there and the methods in the methods-chapters are generic for all frameworks. --Alexandra Kuhn 09:31, 18 March 2008 (EET) (type: truth; paradigms: science: comment)

Frameworks in guidebook

How to read discussions

Fact discussion: .
Opening statement: Guidebook contains descriptions of a general assessment framework and the Intarese framework

Closing statement: Accepted.

(A closing statement, when resolved, should be updated to the main page.)

Argumentation:

⇤--1: . Why is cost-benefit analysis "another framework" in the guidebook? --Alexandra Kuhn 10:27, 17 January 2008 (EET) (type: truth; paradigms: science: attack)

⇤--2: . Intarese framework is not limited to CBA, and therefore CBA is another framework with a more limited scope. --Jouni 00:41, 8 March 2008 (EET) (type: truth; paradigms: science: attack)

Tools in guidebook

How to read discussions

Fact discussion: .
Opening statement: Tools are operational descriptions of managing particular sub-processes and they are mostly described together with the particular methods they relate to

Closing statement: Resolution not yet found.

(A closing statement, when resolved, should be updated to the main page.)

Argumentation:
----1: . Result database is described as a tool in two places --Jouni 16:22, 30 January 2008 (EET) (type: truth; paradigms: science: comment)

Step-specific methods

How to read discussions

Fact discussion: .
Opening statement: Step-specific methods are all modelling methods

Closing statement: Not accepted.

(A closing statement, when resolved, should be updated to the main page.)

Argumentation:

⇤--1: . Step-specific information to be included in an assessment can also be obtained by other means than modeling, e.g. direct observation or measurement. Of course, if we use modeling in a very broad sense to mean all kinds of information collection and manipulation for the purpose of synthesizing it as a part of a particular assessment, the term is acceptable. Restricting the guidebook to cover only modeling methods related to specific in the way it is commonly understood would be too constrained. --Mikko Pohjola 13:01, 1 February 2008 (EET) (type: truth; paradigms: science: attack)

←--2: . I agree to Mikkos comment and we should also include other means, e.g. biomonitoring. --Alexandra Kuhn 09:55, 7 March 2008 (EET) (type: truth; paradigms: science: defence)

----3: . But, is it still a process to collect and provide biomonitorindata? --Alexandra Kuhn 10:35, 7 March 2008 (EET) (type: truth; paradigms: science: comment)

←--4: . Yes, these are processes that should be described in the Guidebook. --Jouni 00:41, 8 March 2008 (EET) (type: truth; paradigms: science: defence)

Information processing methods by sub-processes

How to read discussions

Fact discussion: .
Opening statement: Information processing methods (other than assessment process management methods) should be separated into information collection and information synthesis methods

Closing statement: Accepted.

(A closing statement, when resolved, should be updated to the main page.)

Argumentation:

←--1: . Making a distinction between processes that relate to collecting, manipulating or creating information in a non-predefined format (as defined by the general assessment framework) and processes that relate to synthesizing the information into the predefined format could bring some clarity to understanding their roles in relation to the products of the assessment as well as their mutual roles in the overall assessment process. --Mikko Pohjola 13:41, 1 February 2008 (EET) (type: truth; paradigms: science: defence)

←--2: . I agree. How/where would you do that? will you do that? we could add (later in the Guidebook) the picture you presented in Kuopio with the information processes and the difference of synthesising and manipulation. --Alexandra Kuhn 09:58, 7 March 2008 (EET) (type: truth; paradigms: science: defence)

Assessing uncertainty

----1: . Will a paragraph on uncertainty be at all relevant processes, e.g. emission calculation, ERFs etc.? --Alexandra Kuhn 15:13, 11 February 2008 (EET) (type: truth; paradigms: science: comment)

----2: . Assessing uncertainty will be about the general concepts, and they will apply to all variables, including those that you mention. --Jouni 00:41, 8 March 2008 (EET) (type: truth; paradigms: science: comment)

⇤--3: . But the actual appliance of the general methods should be explained at the relevant processes. e.g. in emission calculation it would also say that the emission factor is more uncertain than the activities. or s.th. in that direction. s.th. specific for THIS purpose. --Alexandra Kuhn 09:28, 10 March 2008 (EET) (type: truth; paradigms: science: attack)

Discussion on some particular page contents

Assessment (universal product)

  • Scope. What is the use purpose of an (impact) assessment? (To answer a policy information need) 3, 6, 12
  • Definition
    • What is an impact assessment
    • Different assessments: HIA, RA, IA... 4-5 (possibly own articles)
----4: . This part describes the process of performing an impact assessment. It goes not into details about the methodologies --Alexandra Kuhn 18:02, 14 January 2008 (EET) (type: truth; paradigms: science: comment) ⇤--#(number):: . No, this is an overview. --Jouni 23:05, 15 January 2008 (EET) (type: truth; paradigms: science: attack)

Performing an impact assessment (process description:assessment framework) 10

  • Scope: Purpose of making an impact assessment is to produce an assessment product.

----1: . What would this be? A general purpose? something like policy consulting??? --Alexandra Kuhn 18:02, 14 January 2008 (EET) (type: truth; paradigms: science: comment)

  • Definition
    • General methodology 10 (----2: . would be the same as the assessment framework? equals dimension "work environment" number 3. --Alexandra Kuhn 18:02, 14 January 2008 (EET) (type: truth; paradigms: science: comment))
    • description of methodology used 11
  • Result
    • Inputs
    • Procedure: Phases of an impact assessment 16
      • Scoping an impact assessment 26
        • Selecting indicators 50
      • Applying general information
      • Drawing a causal diagram 34 Links: Help:Causal diagram | Links to alternatives: Causal chain, impact pathway, DPSEEA, DPSIR
        ----3: . Discussing with some colleagues here at USTUTT they said it would be good to describe the differences and communalities between causal chain, impact pathway approach, DPSEEA, DPSIR. Where would this belong to? --Alexandra Kuhn 18:06, 14 January 2008 (EET) (type: truth; paradigms: science: comment)
        ----5: . Perhaps these descriptions should be included in the links to the different alternatives? Ex give the differences and communalities between causal diagram and impact pathway in the linked section of impact pathway and so on? --Kb 13:43, 18 January 2008 (EET) (type: truth; paradigms: science: comment)
      • Designing variables
      • Executing variables and analyses
      • Reporting an assessment
    • Outputs

Reporting an assessment (process description) 67

  • Scope
  • Definition: different approaches
  • Result
    • Reporting uncertainties 70, 73 (incl. qualitative and quantitative uncertainties)

Stakeholder involvement (process description) 68

Issue framing (process description:issue framing)

----1: . Where would be the boundaries to "process: assessment framework?" --Alexandra Kuhn 18:02, 14 January 2008 (EET) (type: truth; paradigms: science: comment)
  • Scope:
    • Purpose, questions 27
    • Indicator selection 50
    • Boundaries 29
    • Scenarios 30-33
  • Definition
    • Variables

Emission modelling (process description) 36-39

  • Scope: purpose of emission modelling
  • Definition: background
  • Result:
    • How to model 37
    • Sectoral, spatial, and temporal resolution 38
    • Uncertainties 39

Source-to-exposure modelling (process description) 40

  • Scope: purpose
  • Definition: Different types 41
  • See also: pointers to resource centre 42
  • Direct approach: measure data

(----1: . whatever. biomarkers, concentrations... --Alexandra Kuhn 18:02, 14 January 2008 (EET) (type: truth; paradigms: science: comment))

  • Uncertainties 43

Exposure-response function modelling (process description)

  • Scope 45
  • Definition:
    • Different types 46
    • How can they be derived? 47-48
    • Uncertainties 49

Risk characterisation (process description) 51

  • Scope
  • Definition:
----1: . maybe we could summarise "DALYs / QUALYs and monetary valuation under "aggregation". But I don't know how to do this at the moment. --Alexandra Kuhn 18:02, 14 January 2008 (EET) (type: truth; paradigms: science: comment)

Disability-adjusted life year (process description) 52

  • Scope
  • Definition:
    • How are they derived 54
    • Alternatives 53

Monetary valuation (process description) 59

  • Scope: Why do we need monetary values 60
  • Definition
    • Why do we choose monetary values and not utility points? 61
  • Result
    • How are monetary values derived 63

Uncertainty assessment (process description) 39, 43, 49, 58, 65, 69

  • Scope: Purpose of uncertainty assessment
  • Definition: Different approaches
    • Qualitative methods eg pedigree matrix 71
    • Quantitative methods 72-73
    • When to use which method? 73
  • Result
    • Uncertainty of the result: parameter uncertainty
    • Uncertainty of the definition: model uncertainty
    • Uncertainty of the scope: relevance

Uncertainty tools (process: tool) 76

⇤--1: . This does not belong into the Guidebook but it is good to keep it in mind. --Alexandra Kuhn 18:02, 14 January 2008 (EET) (type: truth; paradigms: science: attack)

Propagating uncertainties (process description) 72

  • Scope
  • Definition: approaches
    • Monte Carlo 72
    • Bayesian analysis 72

Impact assessment (product:assessment)

⇤--1: . What should this be? Why should we have that? Scenarios etc. should be positioned under the process as the user should be explained how to build a scenario. --Alexandra Kuhn 17:26, 14 January 2008 (EET) (type: truth; paradigms: science: attack)
  • Scope:
    • Purpose, questions 27
    • Boundaries 29
    • Scenarios 30-33
  • Definition
    • Variables
    • Analyses
  • Result
    • Results
    • Conclusions

The pages of the Pyrkilo guide 2

The table contains all pages that are attached to the Intarese:Help:Pyrkilo guide 2 page. The second column (where it should go) talks about where the current content of the page should go. It does not imply that the scopes of the old and the new page should be the same.

In the Guidebook
The location in Intarese (links redirect to the current page) Where it is now
Intarese:Help:Analysis tool Tool:Analysis tool
Intarese:Help:Applying general information Method:Applying general information
Intarese:Help:Class Universal products:Class
Intarese:Help:Collaborative workspace Tool:Collaborative workspace
Intarese:Help:Designing variables Method:Designing variables
Intarese:Help:Dispute Method:Dealing with disputes
Intarese:Help:Drawing a causal diagram Method:Drawing a causal diagram
Intarese:Help:Executing variables Method:Executing variables
Intarese:Help:External model Tool:External model
Intarese:Help:Extracted model Tool:Extracted model
Intarese:Help:Issue framing tool Tool:Issue framing tool
Intarese:Help:Mass collaboration Method:Mass collaboration
Intarese:Help:Model extractor Tool:Extracted model tool
Intarese:Help:Object design tool Tool:Object design tool
Intarese:Help:Purpose of a risk assessment Method:Defining the purpose of an assessment
Intarese:Help:Reporting a risk assessment Method:Reporting an assessment
Intarese:Help:Reporting tool Tool:Reporting tool
Help:Result database Tool:Result database
Intarese:Help:Risk assessment structure Universal product:Assessment
Intarese:Help:Scoping a risk assessment Method:Scoping an assessment
Intarese:Help:The phases of a risk assessment Method:Performing an assessment
Intarese:Help:Universal information structure for risk assessment products Theoretical foundation:Universal products
Intarese:Help:Users of the pyrkilo method Method:Defining the users of an assessment
Intarese:Help:Variable Universal products:Variable
Intarese:Help:Variable transfer protocol Method:Variable transfer protocol
Intarese:Help:Managing stakeholder involvement Method:Organizing stakeholder information
Intarese:Help:Variable definition Universal products:Variable
Intarese:Help:Plausibility tests Universal products:Variable
Intarese:Help:General properties of good risk assessments General assessment framework:Purpose and properties of good assessments
Intarese:Help:Performance General assessment framework:Evaluating assessment performance
Intarese:Help:Societal role of risk assessment General assessment framework:Societal context of assessments
Intarese:Help:Open participation in risk assessment Method:Participating in assessments
Intarese:Help:Risk assessment process Theoretical foundation:General processes
Intarese:Help:Uncertainty Method:Assessing uncertainty
Intarese:Help:Contributing to a discussion Method:Dealing with disputes


In other parts of the Guidance system
The location in Intarese (links redirect to the current page) Where it is now
Intarese:Help:Causality Glossary:Causality
Intarese:Help:Decision variable Glossary:Decision variable
Intarese:Help:Value judgement Glossary:Value judgement


The new location not yet clear
The current location in Intarese Where it should go
Intarese:Help:Copyright issues Method:Dealing with copyright issues
Intarese:Help:Data gateway Tool:Data gateway
Intarese:Help:Encyclopedia on environmental health Glossary:Encyclopedia on environmental health
Intarese:Help:Guidebook on risk assessment Glossary:Guidebook
Intarese:Help:Integrated resource platform Glossary:Resource platform
Intarese:Help:Open risk assessment (toolbox) Glossary:Open assessment
Intarese:Help:Pyrkilo method (summary) Glossary:Pyrkilo method
Retrieved from "https://en.opasnet.org/index.php?title=Talk:Guidebook&oldid=11810"