Display: Whenever a field/column for "Year" is displayed, the suffix "(EC)" (Ethiopian Calendar) or "(GC)" (Gregorian Calendar) MUST be added
Data Entry: Appropriate business rules for the year must always be applied, is such a way that it is not possible for the user to enter a GC year when an EC year is requested, or vice versa.
Date Conversion: This field cannot be converted from GC to EC or vice versa
Full Date display
Display: To avoid confusion, all GC dates must be displayed in dd-mmm-yy (01-Jul-13), dd-mmm-yyyy (21-Jul-2013) format, both on-screen and in reports.
Dates displayed as dd/mm/yy (01/07/13) cause confusion between American (who read it as January 7, 2013) and European users (who read this as July 1, 2013).
Data Entry: via EC or GC calendar control as appropriate
Date Conversion: This field is stored in the database as GC, and is converted to EC for display/reporting
Whole-Screen Conventions
Selection screens with cumulative totals
Top of display area shows column titles, etc
Bottom of display area (without having to scroll) shows the relevant cumulative totals
Middle of display area scrolls to show contents of the selectable list
User should not need to scroll to the bottom of the webpage to see the totals
Reports
Report Filters
Selection by Date
For month-based reporting, where appropriate the default option should be a field of "Reporting Month", with the default value of current month and year, with EC/GC determined by the current user selection
If the user is in ECmode and selects "Hamlie 2005", this will display all relevant transactions that occurred from 1 Hamlie 2005 (=08-Jul-2013) through to and including 30 Hamile 2005 (=06-Aug-2013) (30 days in total)
If the user is in GC mode and selects "July 2013", this will display all relevant transactions that occurred from 01-Jul-2013 (=24 Senie 2005) through to and including 31-Jul-2013 (=24 Hamile 2005) (31 days in total)
Reports
Dates in Headings
The Primary Date Format will be specified by the users as part of the report design.
Normally, if The report is in Amharic, or is for DRMFSS internal use, the Primary Date Format will be EC, and the Secondary Date Format will be GC
If The report is for external (donor) use, the Primary Date Format will be GC, and the Secondary Date Format will be EC
Reports that spans a range of dates should show boththe Primary Date Formatand the Secondary Date Format
The Primary Date Format should be in a larger font
The Secondary Date Format should be in a smaller font, in brackets (), and below or after the Primary Date Format
GC dates must always be in the format dd-mmm-yy or dd-mmm-yyyy
Date in Columns
There are four possibilities:
Report Date format is fixed at GC (specified by the users as part of the report design)
Report Date format is fixed at EC (specified by the users as part of the report design)
Report Date format is selected by the user at report generation time (regardless of the user's current language/calendar display setting)
Both GC and EC date formats are shown on the report (desirable for transaction-display reports)
If the report date format is selected by the user at report generation time, the system must 'remember' their preference from one session to the next
GC dates must always be in the format dd-mmm-yy or dd-mmm-yyyy
Report Footers
The following items are MANDATORY in all report (whether standard report or letter-style) footers
Report Name: "Report: xxxxxxx" on the left top of the footer
Print Date: "Printed: dd-mmm-yyyy HH:mm" on the left bottom of the footer, regardless of which Primary Date Format is selected
3.20pm on 1 July 2013 would appear as "Printed: 01-Jul-2013 15:20"
Page Number: "Page x of y" on the right side
Page 6 of a 20-page report would appear as "Page: 6 of 20"
The only exception to these footer rules may be the first page of some reports which will not display the page number. All other footer details will be displayed on all pages of all reports