Changes

Building Searches

2,770 bytes removed, 16:22, 29 May 2017

no edit summary

{{TOC right}}

__NOEDITSECTION__

The mine action information collected and stored in IMSMA^NG {{IMSMANG}} is useless without the ability to find it and use it to make operational decisions. That’s why IMSMA^NG {{IMSMANG}} includes a robust data search mechanism that provides an easy-to-use, multilevel interface for building and running searches. As with other parts of IMSMA^NG, the search functionality is divided into a customisation mode, where information managers can prepare simple or complex searches, and an execution mode where data entry personnel can run prebuilt searches. This simplifies the user experience and ensures consistency of use by sharing identical searches with all users. The IMSMA^NG {{IMSMANG}} search function has three primary purposes:

*to navigate to data

*to prepare data for reports and analysis

Information managers can customise IMSMA^NG The navigation and map display searches for each of these purposes are typically designed to meet the specific needs find a single record or a set of the programmerecords. Particularly, customizing These searches are generally simpler than the search functionality other kinds of searches and are designed to facilitate access return records that users can browse through to programme find the necessary data and reporting is a key component of implementing and managing a programme’s information workflow.

<center>{| class="wikitable" width="750"|-| align="center" colspan="4" | '''Table 14. Options for Using Searches'''|-| width="245pt" | '''Option''' | width="155pt" | '''Use or purpose'''| width="245pt" | '''Example criteria'''| width="155pt" | '''Example parameters'''|-| align="left" | '''Navigation and map display''' || align="left" | Search for items by a specific ID | align="left" | Find all hazards with a local ID that includes = “MF-001” | align="left" | Set the local ID as a parameter to be supplied when the search is run|-| align="left" rowspan="2" | These The reporting searches are typically designed more complicated than navigation searches since they are intended to find a single record or return a set of recordsto populate a report directly without any additional user interaction. These searches are generally simpler than the other kinds can also be saved and run independently of searches reports and are designed to return records that users can browse through to find the necessary used for browsing data. || align="left" | Search for items by type| align="left" | Find all hazards with a mine action are type = “Minefield”| align="left" | Mine Action Area Type|-| align="left" | Search for items by date| align="left" | Find all hazard reductions between January 1 and February 1| align="left" | The date range|-| align="left" rowspan="4" | '''Reporting and data quality analysis'''

Reporting searches are typically more complicated than navigation searches since they are intended to return a set of records to populate a report directly without any additional user interaction. These searches can also be saved and run independently of reports and used for browsing data. Data quality analysis searches help identify possible data problems and ensure that mine action programme-specific workflow steps are being followed. These searches can be used to help protect data integrity.| align="left" | Report on clearance efforts | align="left" | Find all hazard reductions where the type = “Progress Report” and the status = “Completed” and the dates are between January 1 and February 1| align="left" | The date range|-| align="left" | Report on hazards cleared by an organisation| align="left" | Find all hazards that are linked to hazard reductions whose type = “Clearance” and the organisation = “XYZ Org”| align="left" | Mine Action Area Type|-| align="left" | Search for all hazards with AP mines| align="left" colspan="2" | Find all active hazards with antipersonnel mines or that have clearances linked to them that have found antipersonnel mines|-| align="left" | Data quality checks| align="left" colspan="2" | Find all hazards whose status is “Worked On” with no active hazard reductions

Find In {{IMSMANG}} we refer to different types of functionality in the Search menu:*'''simple''' as in only one filter option may be used*'''advanced''' as in more than one filter option may be used and complex critera using AND / OR is possible to define*'''saved''' searches which are prepared by information managers for usage by all clearances that are not linked to a hazardusers.

Find Saved searches simplifies the user experience and ensures consistency of use by sharing identical searches with all users. Of course all victims with no link users have the ability to save searches which is a convenient way to accident|}</center>re-use favourite searches.

Particularly, creating saved searches facilitates access to programme data. Reporting is a key component of implementing and managing a mine action programme’s information workflow. The {{IMSMANG}} version 6.0 database is pre-populated with saved searches developed by GICHD that may be customised to meet the specific needs of the mine action programme. ==Building Simple Searches==__NOEDITSECTION__Building searches The simple search options in IMSMA^NG is a simple three-step process the Search menu function exactly as all other filters in which information managers determine:{{IMSMANG}}, see [[Search Items]].

#==Advanced Searches==__NOEDITSECTION__The item to different types of search for#criteria (e.g. subobject and geo area) are described in [[Search by Subobject]] and [[Search by Map Area]], respectively. The attributes of the item possibility to use in AND / OR and to specify the searchparts makes the Advanced searches very flexible.  #Whether ==Using Prompt==__NOEDITSECTION__When the prompt function is used in Advanced searches the re-usability and user-friendliness are greatly increased. For example, if a user wants to find all of progress reports submitted by the "XYZ" organisation and another user wants to have the same search but for the "ABC organisation, it is better to save one search and prompt on Organisation. ==SQL criteria must ==__NOEDITSECTION__While the {{IMSMANG}} search functionality is extremely flexible allowing searches on CDFs, customised option list values and links among items, there are cases where users may want to run more complex searches that cannot be met (AND) or any of built using the Advanced search interface. For these cases, {{IMSMANG}} includes a special SQL search criteria that allows information managers to use a SQL query as filter criteria must be met (OR).

Following these three steps, users can build Creating searches as simple or as complex as using SQL criteria requires a detailed understanding of PostgreSQL's SQL syntax and the examples below:{{IMSMANG}} data model. Your [[Information Management Team | GICHD IM Advisor]] may support you in developing the SQL.

*find hazards with an ID of “MF-101”*find victims who are children and were injured To use SQL criteria, simply provide a valid SQL statement in 2010*find progress reports about work done by XYZ organization on hazards in Province ABC between 2008 and 2010*find all clearances completed on hazards with antipersonnel minesthe following format:

When a search is designed, it can be given a name and description and then saved for later useSELECT [item_guid] FROM [item_table] WHERE. Saving a search saves the criteria of the search rather than the search results. This means that searches are automatically updated when additional data is added to the system, ensuring that searches return the most up-to-date data. For example, an information manager can build a search called “Open Hazards” that finds 25 hazards with a status of “Open.” If 10 additional hazards are entered into the system with a status of “Open,” the search would find 35 records when it is run again. In this way, searches are dynamically updated as data is added to the system, allowing information managers to assess data trends over time using consistent search criteria. Information managers can also use an existing search as a template to create other searches by using the “Save as” functionality.

==Using Search Parameters==Search parameters allow users to change one or more search criteria when running a search. For example, if a user wants to find all progress reports submitted by “XYZ” organisation, they can build a search for “XYZ progress reports.” If another user wants to search for progress reports submitted by “ABC” organisation, they can build another search for “ABC Progress Reports.” Alternatively, an information manager can build The SQL query may be complex with left joins and subqueries but may only have '''one search with a parameter for “Organisation” that allows users to provide different values for ''' output column which should be the organisation when running item_guid of the searchSearch target i. This makes one search, for example, “Progress Reports by Organisation,” available for multiple purposes. The ability to build dynamic searches allows information managers to customise e if your search capabilities to meet the needs of various stakeholders within their programmestarget is Land then only output column should be hazard_guid.

{{note|Searches can include geospatial data as a parameter which allows users We strongly recommended to define develop and test the SQL query with a geospatial extent to search withinSQL tool before pasting it into the SQL criteria since {{IMSMANG}} does not provide SQL debugging support. For the purposes of searching, records without geospatial data are defined as “outside” the geospatial extent}}

==Building Complex Saved Searches==__NOEDITSECTION__While Saving a search saves the criteria of the search rather than the IMSMA^NG search functionality is extremely robust—allowing results. This means that searches on CDFs, customised option list values and links among items— there are some cases where users may want automatically updated when additional data is added to run more complex searches that cannot be built using the standard search interface. For these casessystem, IMSMA^NG includes a special Structured Query Language (SQL) search functionality ensuring that allows information managers to provide SQL syntax for executing searches. Creating searches are returning results using SQL criteria requires a detailed understanding of relational databases, SQL and the IMSMA^NG updated data model and should only be undertaken by advanced users.

==Inspiration Saved Searches==__NOEDITSECTION__{{IMSMANG}} version 6.0 database is pre-populated with 40 different data quality Saved searches of different kinds:* suspected duplicates** e.g "Victim Duplicate Name & Date Of Birth"* items without any geographical data** e.g. "Accident Without Geodata"* items that do not have any links to other items** e.g. "Assistance Without Links To use SQL criteria, simply provide a valid SQL statement in the following format:Victim"* items which are assigned to different locations** e.g. "Land & Activity Not Same Location"* task as Search target** e.g. "Land Included In More Than One Task"* possible mine action process quality issues** e.g. "Status Open with links to Activity or QM"

SELECT [item_guid] FROM [item_table] WHERE{{note | These Saved searches should be seen as '''inspiration''' and should be adapted to each mine action programme's processes...For example, SELECT hazreduc_guid FROM hazreduc WHERE hazreduc_localID =’ÇL-001’}}

Using SQL criteria, information managers can design complicated searches that can then be saved and run by users with no understanding of SQL. In this way, {{NavBox IMSMA^NG unleashes the full power of SQL criteria, joins and subqueries in an easy-to-run interface.Administration}}

{{note|* It is recommended that information managers test their SQL in an external SQL editor prior to using it within IMSMA^NG since IMSMA^NG does not provide SQL debugging support.* Information managers can build complicated queries using SQL and combine them with other criteria, including parameters, to provide virtually unlimited search capabilities to IMSMA^NG users}}[[Category:NAA]]

• ← Older edit

Alnaucler

NoPublic, bureaucrat, administrator

6,632

edits