Difference between revisions of "Designing Summary Templates"

From IMSMA Wiki
Jump to: navigation, search
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{TOC right}}
 
__NOEDITSECTION__
 
==Summaries==__NOEDITSECTION__
 
 
In the same way that information managers can customise Data Entry Form templates to include only the information that is important to their programmes, managers can also customise Summary templates to display only the information that is most relevant to their programmes.  
 
In the same way that information managers can customise Data Entry Form templates to include only the information that is important to their programmes, managers can also customise Summary templates to display only the information that is most relevant to their programmes.  
 
{{HowTo's
 
{{HowTo's
|[[Customise Views|Customise Summaries]]
+
|[[Summary Templates|Customise]]
|[[Publish and Archive Views|Publish and Archive Summaries]]
+
|[[Publish and Archive Summary Templates|Publish and Archive]]
|[[Delete Views|Delete Summaries]]
+
|[[Delete Summary Templates|Delete]]
 
}}
 
}}
 
Summary customisation works in much the same way as Data Entry Form customisation, where information managers can build Summary templates.  
 
Summary customisation works in much the same way as Data Entry Form customisation, where information managers can build Summary templates.  
  
IMSMA<sup>NG</sup> provides initial templates for each type of item but information managers can change them and even create multiple Summary templates for each type of item so that programmes can switch between different templates as necessary. Following the guidelines below, information managers can design Summary templates to suit their specific programme’s needs.
+
{{IMSMANG}} provides inspiration templates for each type of item but information managers can change them. Following the guidelines below, information managers can design Summary templates to suit their specific programme’s needs.
  
 
<center>
 
<center>
Line 18: Line 15:
 
|-
 
|-
 
| width="300pt" | '''Guideline'''
 
| width="300pt" | '''Guideline'''
| width="300pt" | '''Explanation'''
+
| width="600pt" | '''Explanation'''
 
|-
 
|-
 
| align="left" | Include a table of links
 
| align="left" | Include a table of links
| align="left" | Include a table of links so that links between items in IMSMA<sup>NG</sup> can be viewed.
+
| align="left" | The links between items in {{IMSMANG}} are very important so put the link table where the users may see it without scrolling.
 
|-
 
|-
 
| align="left" | Use tabs to group information
 
| align="left" | Use tabs to group information
| align="left" | Unlike Data Entry Form templates, Summaries can include tabs to group similar information together. Use tabs to make information easier to find and comprehend.
+
| align="left" | Summary templates can include tabs to group similar information together. Use tabs to make information easier to find and comprehend.
 
|-
 
|-
 
| align="left" | Include geospatial data
 
| align="left" | Include geospatial data
| align="left" | Include geospatial information so it can be viewed in one place without needing to open individual Data Entry Forms. The information can also be easily printed from the Summary.
+
| align="left" | The information can also be easily printed from the Summary. The difference between the columns ''X / Lon & Y / Lat'' and ''X / Longitude & Y / Latitude'' is described [[Summary Window#Data area - Geospatial tab|'''here''']].
 
|-
 
|-
| align="left" | Print Summaries before finalizing them
+
| align="left" | Printing Summary items
| align="left" | When printed, a Summary provides an excellent summary of all the information known about an item, so it could be the source for many reports. Print each Summary before finalizing it to ensure it displays the desired data.
+
| align="left" | When you have made changes to a Summary template, do not forget to update the printing iReport template too.
 
|}
 
|}
 
</center>
 
</center>
  
 
{{note|
 
{{note|
* Summary templates are defined for all users of the IMSMA<sup>NG</sup> system and are not customisable for individual users.
+
* Summary templates are defined for all users of the {{IMSMANG}} system and are not customisable for individual users.
* Unlike Data Entry Form templates, Summary templates cannot be exported or exchanged between IMSMA<sup>NG</sup> systems}}
+
* Summary templates cannot be exported or exchanged between {{IMSMANG}} systems}}
  
{{NavBox Getting started with IMSMA}}
+
{{NavBox IMSMA NG Administration}}
 +
 
 +
[[Category:NAA]]

Latest revision as of 15:22, 29 May 2017

In the same way that information managers can customise Data Entry Form templates to include only the information that is important to their programmes, managers can also customise Summary templates to display only the information that is most relevant to their programmes.

Summary customisation works in much the same way as Data Entry Form customisation, where information managers can build Summary templates.

IMSMANG provides inspiration templates for each type of item but information managers can change them. Following the guidelines below, information managers can design Summary templates to suit their specific programme’s needs.

Guidelines for Designing Summary Templates
Guideline Explanation
Include a table of links The links between items in IMSMANG are very important so put the link table where the users may see it without scrolling.
Use tabs to group information Summary templates can include tabs to group similar information together. Use tabs to make information easier to find and comprehend.
Include geospatial data The information can also be easily printed from the Summary. The difference between the columns X / Lon & Y / Lat and X / Longitude & Y / Latitude is described here.
Printing Summary items When you have made changes to a Summary template, do not forget to update the printing iReport template too.
Note.jpg
  • Summary templates are defined for all users of the IMSMANG system and are not customisable for individual users.
  • Summary templates cannot be exported or exchanged between IMSMANG systems