==Data Types=={{TOC right}} ===Items=== In Understanding the IMSMA<sup>NG</sup> {{IMSMANG}} information model, items are is a prerequisite for an information manager to adapt the containers for system to their country specific mine action informationrequirements. An item is an area, activity or event that Some sections will include a mine action programme records information about and stores in IMSMA<sup>NG</sup>. There are six categories list of items, which are described in the table below. Each category requirements that can be characterized used by a type that reflects whether information managers to define and document the item is designed to track process or activity information or the object or product of an activitymodel for a programme.
==Data Types==__NOEDITSECTION__
===Core Data===__NOEDITSECTION__
In the {{IMSMANG}} information model, items are the containers for core data, such as mine action data. An item is an area, activity or event that a programme records information about and stores in {{IMSMANG}}. There are six categories of items, which are described in the table below. Each category can be characterised by a type that reflects whether the item is designed to track process or activity information or the object or product of an activity.
{| class="wikitable"
|+ Items
! Item
! Description
! Type
|-
| HazardLand| Information about an area affected by a hazard
| Object/Product
|-
| Hazard reduction activityActivity| Information about an activity , such as efforts to survey, clear, or reduce the threat of a hazard
| Process/Activity
|-
| Accident
| Information about an accidental event involving a hazard
| Object/Product
|-
| Victim
| Information about a person injured or affected by a hazardan accident
| Object/Product
|-
| Mine Risk Assistance| Information about assistance for a person injured or affected by an accident| Process/Activity|-| Education (MRE) activity| Information about an activity designed to inform or educate people about hazards(e.g. Risk Education or Victim rights)| ObjectProcess/ProductActivity
|-
| Quality Management (QM) activity
| Information about an quality-improvement activity , such as an effort to control and monitor the clearance and/or reduction of hazards land or hazard reduction activities| ObjectProcess/ProductActivity
|-
|}
Items are entered into {{IMSMANG}} by means of a Data Entry Form. Typically, each category of items has its own Data Entry Form template for recording information specific to that category. When entered into {{IMSMANG}}, all Data Entry Form items must be assigned to a Location, which is tied to the country’s gazetteer, or political or administrative structure. The items can then be traced back to the Country Structure so that users can easily report data such as the number and size of hazardous areas within a particular province.
Items are entered into IMSMA<supcenter>NG</sup> by means of a field report. Typically, each category of items has its own field report template for recording information specific to that category. When entered into IMSMA<sup>NG</sup>, all field report items must be assigned to a location, which is tied to the country’s gazetteer, or political or administrative structure. The items can then be traced back to the country structure so that users can easily report data such as the number and size of hazards within a particular province. Part of defining and documenting an information model includes defining the useful information attributes for each IMSMA<sup>NG</sup> item. IMSMA<sup>NG</sup> comes with more than 1,000 data elements already defined as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data elements are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data elements that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data elements may be collected for each IMSMANG item, some elements may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.
{| class="wikitable"
|+ Item Subcategories
! Item
! Subcategory Category Examples
|-
| HazardLand
|
* Battle area* Dangerous area* MinefieldSHA
* CHA
* UXO spotEOD Spot Task* Ammunition Storage
|-
| Hazard reduction activityActivity
|
* Non-Technical survey
* Technical survey
* Clearance
* Completion survey
* Technical survey
* Progress report
|-
| Accident
* Demining accident
* Mine accident
|-
| Victim
|
* Civilian
* Deminer
|-
| Mine Risk Education (MRE) activity
|
* Peer-to-peer
|-
| Quality Management (QM) activity
|
* Quality management
* Quality control
|-
|}
</center>
Part of defining and documenting an information model includes defining the useful information attributes for each {{IMSMANG}} item. {{IMSMANG}} comes with more than 1,000 [[Data Dictionary| data fields already defined]] as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data fields are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data fields that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data fields may be collected for each {{IMSMANG}} item, some fields may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.
Each of the items can be divided into categories or types so users can collect information for each category/type. For example, Land are normally divided into different categories/types and each category of land are managed differently. Using categories/types, information managers can:
Each of the six categories of items can be divided into subcategories or types so users can collect information for each subcategory. For example, users can specify different types of hazards such as dangerous areas, confirmed hazardous areas (CHAs), minefields and battle areas and manage each kind of hazard differently. Using subcategories, information managers can: * create separate workflows for each category/type of hazardLand* create and manage separate data entry formsData Entry Form templates per category/type* differentiate between item categories /types on the map Additionally, information managers can customise the subcategories so that unused subcategories can be removed and other subcategories added. The same is true for all top-level items within IMSMA<sup>NG</sup>, which lets information managers specify their exact information model, including the relationships among item categories, and adjust the model as their needs change over time. To accurately map the information model for a programme, it’s helpful to evaluate the available item subcategories and determine if changes to the information model in IMSMA<sup>NG</sup> are required. While these values can be customized after system setup, understanding the types of information for each item is critical to implementing an effective workflow in IMSMA<sup>NG</sup>. Table 5 shows examples of the possible subcategories of IMSMA<sup>NG</sup> items. [[Image:Understanding IMSMA Information Model - Documenting Items.png|center|500px|''Documenting Items'']]<div align="center">''Documenting Items''</div> ===Auxiliary Data===
In addition to defining Additionally, information managers can customise the required information categories so that unused categories can be inactivated and other categories added. The same is true for IMSMA<sup>NG</sup> all top-level itemswithin {{IMSMANG}}, it is important to define the relevant which lets information managers specify their exact information to be collected about auxiliary data. This includes defining and documenting model, including the country structurerelationships among item categories, ordnance, organisations and places, such adjust the model as military basestheir needs change over time. To accurately map the information model for a Mine Action Programme, hospitals it’s helpful to evaluate the available item categories and cultural sites; any additional CDFs that should determine if changes to the information model in {{IMSMANG}} are required. While these values can be created; and any subcategories customised after system setup, understanding the types of information for each of the auxiliary data typesitem is critical to implementing an effective workflow in {{IMSMANG}}.
{{note|<b>Document the following decisions about items:</b>
* data to be collected and managed in {{IMSMANG}}
* data fields that are not predefined in {{IMSMANG}} and should be created as CDFs
* particularly important, or key, data for the programme
* relevant categories/types for each item
* status values for each item
}}
[[Image:Understanding IMSMA Information Model - Documenting Auxiliary DataExample of Documented Land.png|center|500px|''Documenting Auxiliary Data''300px]]
<div align="center">
''Documenting Auxiliary DataExample of documentation''
</div>
===Auxiliary Data===__NOEDITSECTION__
In addition to defining the required information for {{IMSMANG}} items, it is important to define the relevant information to be collected about Auxiliary data. This includes defining and documenting the [[Standardising_Auxiliary_Data#Country_Structure|Country Structure]], [[Standardising_Auxiliary_Data#Ordnance Classification | Ordnance classification]], [[Standardising_Auxiliary_Data#Organisations |Organisation]] and [[Standardising_Auxiliary_Data#Places|Place]], such as military bases, hospitals and cultural sites; any additional CDFs that should be created; and any subcategories for each of the Auxiliary data types.
==Field Reports {{New_6.0 | In version 6.0 two classifications used for Victim; Cause and Current Views==Needs assessment, and Assistance classification used for Assistance have been added. All three are hierarchy tree-structures using levels.}}
All mine action information is entered into IMSMA{{note|<supb>NG</sup> via a field report, a Document the following decisions about Auxiliary data entry form used to collect information about an item. When a field report is completed, it is either reconciled to an existing item (that is, it is determined to be information about an item that already exists in IMSMA<sup>NG</sup>) or it is reconciled as new (that is, it is determined to be information about an item that does not already exist in IMSMA<sup>NG:</supb>).
* data to be collected and managed in {{IMSMANG}}
* data fields that are not already configured in {{IMSMANG}} and can be created as CDFs
* relevant subcategories for each data type
}}
[[Image:Understanding_IMSMA_Information_Model_Understanding IMSMA Information Model -_Field_Reports_and_Current_ViewsExample of Documented Auxiliary Data ver2.png|center|300px|''Field Reports, Current Views, and Reconciliation'']]
<div align="center">
''Field Reports, Current Views, and ReconciliationExample of Documented Auxiliary Data''
</div>
==Data Entry Forms and Summary items==__NOEDITSECTION__
A '''Data Entry Form''' is a template used for data entry of information e.g. about a victim.
With this approach, users can collect and store multiple field reports about the same item over time so that the entire history of the item is preserved in the system. The approach also provides Data Entry Form(s) for a complete audit trail of all changes made to any mine action information so that information managers can answer specific object (e.g. the question, "What did we know Victim ''Jane Doe'') are summarised and when did we know it?"displayed in a '''Summary'''.
IMSMA<sup>NG</sup> also provides a constantly updated current view of '''Reconciliation''' is the item which represents the sum process of deciding if information about the item at any given time. As subsequent information is collected about should update an existing object or creating a specific attribute of an item, IMSMA<sup>NG<new object/sup> updates the item’s current view on an attribute-by-attribute basis. For example, Field Report #1 collects some initial information about a hazard. It sets the priority to "Medium" and specifies that the hazard contains AP mines and is 25,000 sqm. Field Report #2 updates information about the hazard after a subsequent assessment. The report sets the priority to "High" and specifies the presence of AP and AT mines, but it does not change the size or the status of the hazard. Field Report #3 updates the hazard’s size and status after clearance operations are complete. The figure below shows how the hazard’s current view is updated after all three reports are entered into the systemSummary.
Or with other words, when a Data Entry process is started the first decision is to choose which of the several different methods/actions for Data Entry to use.
With this approach, users can collect and store multiple Data Entry Forms about the same item over time so that the entire history of the item is preserved in the system. The approach also provides a complete [[Image:Understanding_IMSMA_Information_Model_-_Updating_CVs.png|center|500pxAudit log |''Example of Updating Current Views''audit trail]]<div align=of all changes made to any information so that information managers can answer the question, "centerWhat did we know and when did we know it?">''Example of Updating Current Views''</div>
As subsequent information is collected about a specific attribute of an item, {{IMSMANG}} updates the item’s Summary on an attribute-by-attribute basis. The calculation of the Summary is done based on '''Date of Information''' and therefore it is important that Date of information is reflecting the age of the information and not the date of entry into {{IMSMANG}}.
Current view calculations are based on the date of the field report, so it is possible to enter data into the system out of chronological order (that is, to collect past information about an item) without disrupting the current view. For example, if a fourth field report were collected and dated between Field Report #1 and Field Report #2, it would have no effect on the current view as all information in the example was updated with Field Report #2 or later. ===Mapping the Workflows=== The first element of mapping the hazard reduction workflow is to build a map of the relationship between the objects and processes involved in the hazard reduction process. Starting with the first representation of the hazard, the workflow map should describe the processes done to the hazard and the output of the process. The workflow map should trace the entire process from hazard identification through clearance and release of the land according to the operational process in use in the programme. In the example below, a confirmed hazardous area (CHA) is linked to a technical survey that was conducted on the hazard. The survey resulted in a minefield on which a clearance was done, and the clearance resulted in a cleared hazard. Finally, a completion survey was logged to close the hazard. [[Image:Understanding Mine Action Information Management Understanding_IMSMA_Information_Model_- Mapping workflow_Updating_CVs ver2.png|center|''Mapping the Workflow''400px]]
<div align="center">
''Mapping the WorkflowExample of Updating Summary items''
</div>
Data Entry Form #1 collects some initial information about a Land. It sets the priority to "Medium" and specifies that the land contains AP mines and is 25,000 sqm.
This workflow map identifies Data Entry Form #2 updates information about the hazard reduction process that is used within land area after a subsequent assessment. The report sets the programme priority to "High" and can be mapped in IMSMA<sup>NG</sup> to track specifies the clearance presence of hazards. Because IMSMA<sup>NG</sup> supports customisable workflowsAP and AT mines, but it can be used to track different workflows for different objects. For example, a programme may have a separate abbreviated workflow for spot UXO tasks that involve only does not change the identification of size or the UXO hazard (object) and a clearance status of the hazard (process) without additional surveys or steps. This process should also be mapped for implementing in IMSMA<sup>NG</sup>land area.
===Business Rules Updating Structure=======Status Changes====Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure above shows how the land area's Summary is updated after all three reports are entered into the system.
Along with {{Warning| A Data Entry Form that is changing existing information must have a workflow map Date of information that describes is later than the relationship between Data Entry Form that it is updating the various types calculation of objects and processes in a workflow, the status changes or outputs from the process Summary item(s) are critical in adequately mapping the hazard clearance processbased on Date of Information. IMSMA<sup>NG</sup> uses When the status value of items to track where the object or process date is in its workflow. Objects and processes in IMSMA<sup>NG</sup> can have different status values. For example, hazards can be defined as "Active", "Worked On," earlier or "Closedthe '''same'''," while hazard reduction activities that are more process-oriented can the Summary item will '''not''' be "Planned," "Ongoing," "Completed," "Suspended," or "Abortedupdated." Defining a set of status values for each item provides the capability to:}}
* manage workflows according ===Location ===__NOEDITSECTION__A country's official administrative structure, also known as Gazetteer, should be the base for the Country Structure used in {{IMSMANG}}. Sometimes the official administrative structure has not been updated for a long time or it is not detailed enough using it for a geographical placeholder, worksite, for the Mine Action programme and that is why the item Location has been introduced in {{IMSMANG}}. Two fundamental decisions to make when customising {{IMSMANG}} is to decide what Country Structure level Locations will be consistently linked to status* search and report on items based on what concept Locations will represent. Typical concepts that a particular status* display items on the map with different symbols based on their statusLocation is used to represent include:
Some IMSMA<sup>NG</sup> items may have many status values. For example, process-oriented items such as hazard reductions and quality management likely have many status values, but hazards and other object- or output-oriented items typically have only the three status values listed above. Some items like victims and accidents may not need status values depending on how information is used. Defining the possible status values for each object in the workflow as outputs of the processes conducted on them provides *a set of business rules for information management that govern how information should be entered and analysed. ====Example Workflows with Status Changes==== The following figures show how each programme can tailor the system to support a specific hazard clearance/reduction workflow process for each type of hazard, from a traditional process for minefield clearance with multiple steps including a technical survey, clearance and completion survey to a simplified process for UXO clearance that includes only a clearance. Each example involves a single hazard on which one or more hazard reduction work area (where activities are conducted. At each step, information about the hazard’s status and type is updated as a result of the hazard reduction process.taking place) In the figure below, *a CHA is created and its status is set to "Active." A technical survey process is then conducted on the hazard which results in changing the subcategory of the hazard from "CHA" to "Minefield" and defining the hazard’s perimeter. Next, a clearance process is conducted on the minefield that results in updating the status of the hazard to "Worked On." Finally, community (a completion survey is submitted that updates the status group of people affected by the hazard to "Closed." [[Image:Understanding Mine Action Information Management - Example Workflow.png|center|''Example of a Traditional Workflow'']]<div align="center">''Example of a Traditional Workflow''<mine/div> Simpler processes can be defined for other types of hazards. For example, a spot UXO task would likely not go through this complete workflow and instead start with a subcategory of "UXO" and a status of "Open." A clearance could then be conducted and the UXO spot status updated to "Closed," without requiring a completion survey. [[Image:Understanding Mine Action Information Management - Example Workflow 2.png|center|''Example of a Spot UXO Workflow'']]<div align="center">''Example of a Spot UXO Workflow''</div>IED threat) By documenting *the entire process conducted on each type of hazard, including nearest town (the changes in status and type that result from town closest to where the hazard reduction activities, information managers create a complete map of the hazard/hazard reduction workflow that informs how linking and reconciliation decisions should be made and provide a guide to data entry personnel.activity is taking place)
===Progress Reporting Using Locations, users can group data that belongs together or is associated with each other and in that way get a better overview, facilitate searching and creating reports. The Locations is the link between the Country Structure===, whether at the province, district or town level and the Mine Action data. As shown in the figure below, data in {{IMSMANG}} are governed by two simple rules:
Once the hazard and hazard reduction relationships and workflow are defined and documented for each type of hazard, the next step is to define how progress *all data for the hazard clearance processes is collected. Traditionally, incremental progress data is collected using progress reports. These reports are typically linked to the overall clearance operation and are used to collect the incremental progress for a reporting period, usually, the number of mines/UXO cleared, area cleared and hours worked. In IMSMA<sup>NG</sup>, each progress report is stored as a new hazard reduction activity and linked must be assigned to the clearance. As a result, individual progress reports can Location*all Locations must be queried linked to determine how much progress was made during a given reporting period. In addition, aggregate progress information can be queried for each clearance (for example, the total mines that have been reported cleared for a given clearance operation).Country Structure
An alternative approach to storing progress information is to collect incremental progress reports and reconcile them as updates to the clearance using the combine option during reconciliation. Using this method, progress reports do not create independent hazard reduction items; rather, their information is combined with, and added to, the clearance information collected to that point. This approach simplifies the reconciliation step for progress reports as well as provides a simple summary of clearance data on each hazard in the current view. It may, however, become slightly more complicated to determine progress during individual reporting periods. Information managers should assess which approach better meets the needs of their programs when selecting an approach to tracking progress. In the example below, progress reports were collected for three separate reporting periods during a clearance operation. Collecting and linking information in this way makes it easy to determine that in Period 2 (PR-2), 4,500 sqm were cleared and 25 AP mines were found and that, overall, 15,000 sqm were cleared and 61 AP mines were found. A defined, standardized approach to collecting and storing progress information simplifies querying and reporting of statistical information and is a critical element to supporting operational mine action information management needs. [[Image:Understanding Mine Action Information Management - Progress Report Workflow.png|center|''Progress Report Workflow'']]<div align="center">''Progress Report Workflow''</div> ==Reconciliation Process== ===Location Folder=== A location in IMSMA<sup>NG</sup> is a grouping of information, whether logical, geographical or sociopolitical. Using locations, users can group data that belongs together or is associated with each other and handle it as a group, including facilitating data entry, searching and running reports. To do this, locations must link the mine action data to the country’s political or administrative structure (existing gazetteer), whether at the province, district or town level. This method also provides geographical context to the data. As shown in the figure below, locations in IMSMA<sup>NG</sup> are governed by two simple rules: *all mine action data must be linked to a location*all locations must be linked to the country structure [[Image:Understanding IMSMA Information Model - Using Locations to Link Mine Action Data to the Country Structure.png|center|''Using Locations to Link Mine Action Data to the Country Structure'']]
<div align="center">
''Using Locations to Link Mine Action Data to the Country Structure''
</div>
{{note|<b>Document the following decisions about Locations:</b>
* what concept Locations will represent
* what Country Structure level Locations will be linked to
}}
Two fundamental decisions to make when customizing IMSMA<sup>NG</sup> is to decide what country structure level locations will be consistently linked to and what concept locations will represent, Typical concepts that a location is used to represent include: *a work area (where hazards exist and hazard reductions are taking place)*a community (a group of people affected by the mine/UXO threat)*the nearest town (the town closest to where the activity is taking place) [[Image:Understanding IMSMA Information Model - Documenting Locations.png|center|500px|''Documenting Locations'']]<div align="center">''Documenting Locations''</div> ===Assigning and Linking===__NOEDITSECTION__ IMSMA<supb>NGAssigning</supb> provides the capability to assign items to locations and create links between items, a function that shows the relationships between items and processes and that enriches the data collected. Assignments and links are defined during the field report approval process. An item is assigned to one location, which ties the item refers to the country structure and allows for reporting mine action data by area. The same item can then be linked to as many other items as necessary. In this way, IMSMA<sup>NG</sup> supports the idea assignment of linking hazard reductions to hazards, victims to accidents or any an item to any other item. When used with item subcategories, linking adds a powerful capacity to implement an information workflow and create rich and useful data Location for decision makers. To ensure the integrity purposes of this data, system administrators must clearly specify the kinds of links to track in IMSMA<sup>NG</sup>grouping information. See [[Maintaining IMSMA]] for more on this topic. The example below shows how users can build a workflow of complex relationships among top-level All items and item subcategories to model the information management process for their programmes. [[Image:Understanding IMSMA Information Model - Example of How Relationships Among Items are Created.png|center|400px|''Example of How Relationships Among Items are Created'']]<div align="center">''Example of How Relationships Among Items are Created''</div> The next figure shows how the current view changes with each hazard reduction that is linked to the original hazard. The CHA starts with a status of "Open." When the technical survey is linked to the hazard, it changes the hazard subcategory to "Minefield." Then, linking the clearance updates the hazard’s status to "Worked On." Finally, linking the completion survey changes the hazard’s status to "Closed." The result is one hazard whose information is updated over time by the four hazard reductions linked to the hazard. This way to track information can must be used to represent the information management process and status rules accurately for assigned a land release, risk management or other process modelLocation.
<b>Linking</b> refers to the association between items for the purposes of analysis. Linking is optional, for example, when linking Activities to Accidents but linking is very important to do so effective reporting will be possible.
[[Image:Understanding IMSMA Information Model - Example of How Current View Statuses Change{{IMSMANG}} provides the capability to assign items to Locations and create links between items, a function that shows the relationships between items and processes and that enriches the data collected. Assignments and links are defined during the Data Entry Form approval process.png|center|400px|''Example of How Current View Statuses Change'']]<div align="center">''Example of How Current View Statuses Change''</div> The IMSMA<sup>NG</sup> information model An item is flexible enough for each programme assigned to one Location, which ties the item to customise the system country structure and allows for reporting data by area. The same item can then be linked to support its needsas many other items as necessary. For exampleIn this way, programmes that do not conduct MRE {{IMSMANG}} supports the idea of linking activities do not need to complete information about MREsland, and they still retain full utility of the systemvictims to accidents or any item to any other item. SimilarlyWhen used with item categories, programmes that conduct victim tracking linking adds a powerful capacity to implement an information workflow and MRE activities only can disregard hazards create rich and hazard reductions without any loss useful data for decision makers. To ensure the integrity of utility. This flexibilitythis data, however, requires that programmes define system administrators must clearly specify the relevant uses kinds of each itemlinks to track in {{IMSMANG}}.
Although any item The example below shows how users can be build a workflow of relationships among items to model the information management process for their Mine Action Programmes. The figure shows how the Summary changes with each activity that is linked to any other item, not all relationships necessarily make sense for every programmethe original Land. # The diagrams below describe some Land starts its life-cycle as ''SHA'' with a status of Open in this example. # When the more common logical relationships among items clearance starts and can serve as the basis for an information model when implementing IMSMA<sup>NG</sup>first Progress report is linked to the Land, the status should be changed to ''Worked On''. # Finally, after linking the Completion Report the land's status should be updated to ''Closed''.
The result is one Land whose information is updated over time by the three Activities linked to the land. This way to track information can be used to represent the information management process and status rules accurately for a Land Release, Risk management or other process model.
[[Image:Understanding IMSMA Information Model - Example Relationships Among Itemsof How Current View Statuses Change.png|center|400px|''Example Relationships Among Items'']]
<div align="center">
''Example Relationships Among Itemsof How Summary Statuses Change''
</div>
The {{IMSMANG}} information model is flexible enough for each Mine Action Programme to customise the system to support its needs. For example, implementations that do not cover Education activities do not need to complete information about Education activities, and they still retain full utility of the system. Similarly, implementations that only cover Victim tracking and Education activities only can disregard Land and Activities without any loss of utility.
The rationale Although any item can be linked to any other item, not all relationships necessarily make sense for each relationship or link should also be documented so the meaning is understoodevery implementation. For example, a hazard reduction may be conducted on a hazard and an accident may be a result The diagrams below describe some of a hazard or produce a victim. These the more common logical relationships are used when entering data to ensure that among items and can serve as the links between items are available basis for searching and reporting, like an information model when searching for all hazards that have clearances linked to themimplementing {{IMSMANG}}.
[[Image:Understanding IMSMA Information Model - Documenting Assigning and LinkingExample Relationships Among Items.png|center|500px|''Documenting Assigning and Linking''550px]]
<div align="center">
''Documenting Assigning Note: Connections to Country Structure and LinkingLocation have been omitted from the example''
</div>
The rationale for each relationship or link should also be documented so the meaning is understood. These relationships are used when entering data to ensure that the links between items are available for searching and reporting, like when searching for all Land that have Accidents linked to them.
{{note|<b>Document the following business rules about assigning and linking:</b>
* which items will have links between them, for example, Victims should always be linked to Accidents
* rationale or logical meaning of the relationships between items, for example, a link between a Clearance and an Accident means that the Accident happened during the Clearance
* what effects linking has on the items, for example, a link between a Clearance and Land may indicate that the land status should change from ''Open'' to ''Worked on''
}}
===The Workbench=== Items, field reports, current views, assigning and linking come together at the Workbench. The Workbench is a holding area where users enter data into field reports and reconcile each item in the field report either as a new item or as an update to an existing item. Users have the ability to assign field report items to locations and to link items to other items (like linking a technical survey to an existing CHA). They then save the reports in the Workbench pending the appropriate quality checks and approvals. Until a field report is approved, it exists only in the Workbench and does not update any current views. The report can still be modified or deleted. When a field report is approved, however, it becomes part of the current views and cannot be deleted. __NOEDITSECTION__[[Image:Understanding IMSMA Information Model - Adding Field Report Information to the Current ViewWB_Status.png|175px|center|''Adding Field Report Information to the Current View'']]
<div align="center">
''Adding Field Report Information to the Current ViewApproval workflow / Data Entry Form Statuses''
</div>
The Workbench is a holding area / import inbox where Data Entry Forms are found until they are approved. There are four possible steps in the Approval process:
# [[Save Data Entry Forms| Save]]
# [[Submit Data Entry Forms | Submit]]
# [[Reject Data Entry Forms | Reject ]]
# [[Approve Data Entry Forms | Approve]]
For data quality purposes, it is important that the data is adequately checked. With multiple permission levels for the Approval, different users can be assigned different permissions, allowing Mine Action Programmes to implement a data-entry workflow that distinguishes between data '''entry''' and data '''verification''' roles.
For data quality purposesUntil a Data Entry Form is approved, it is important that the data is adequately checked at this stage. IMSMA<sup>NG</sup> allows information managers to control permissions for exists only in the Workbench and other areas does not update any Summary items. The report can still be modified or deleted. The Approval will trigger an update of IMSMA<sup>NG</sup> through the management an existing item (Summary) or creating of a new item depending of users and roleschosen Action. With multiple permission levels for If the WorkbenchSummary item has geospatial data, different users can it may be assigned different permissions, allowing programmes to implement a data-entry workflow that distinguishes between data entry and data verification roles. It is recommended to set up a permission structure that reserves approval authority for field reports for visible in the most trusted usersMap Pane. ====Roles and Responsibilities====
{| class="wikitable"|+ Roles and Responsibilities! Role! Description|-| Data Entry| Users whose primary function is to enter field reports and other data into the system. This role may or may not include the ability to approve field reports.|-| Data Verification| Users who typically perform quality checks on the data entered by Data Entry users. This role is often responsible for verifying the accuracy of the data entered and approving field reports.|-| Operations| Users who typically browse for information within IMSMA<sup>NG</sup> to make operational decisions. Operations users may sometimes be grouped by function (for example, MRE, clearance or victim assistance). These users often perform searches for data, generate reports and analyze the data to support operational needs.|-{NavBox Information Management}}| Systems Administrator| Users who perform information management-specific functions such as creating field report templates, designing reports, backing up and restoring data and other technical functions.|-| Guest| Users with essentially read-only access to browse data.|-|}[[Category:NAA]]
