Daylight Saving Time
Also known as DST. The convention of advancing clocks so that afternoons have more daylight and mornings have less. Typically clocks are adjusted forward one hour near the start of spring and are adjusted backward in autumn. Many countries observe DST; details vary by location and change occasionally.
Glossary
date-time Section
Use this configuration section to specify options for populating the DATE_TIME table. To configure a custom calendar, create a similar section that has the same options; name the section by using the date-time- prefix.
Job_InitializeGIM populates data in all configured calendars when it initializes the Info Mart database.
Job_MaintainGIM subsequently maintains the calendars in accordance with options that are specified in the [date-time] and custom [date-time-*] configuration sections. The maintenance job automatically adjusts for special requirements such as daylight saving time (DST) and fiscal years that do not start on the same day every year (floating fiscal years).
date-time-max-days-ahead
Default Value: 366
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies, in number of days, how far ahead the calendar dimension table will be populated. The default value specifies that the calendar dimension will be populated up to a year in advance (365 days + 1 day for leap years). Genesys does not recommend that you populate the calendar tables more than a year in advance, in case there are changes to DST or other international time standards that might invalidate the prepopulated data.
Note: Ensure that you populate the calendar far enough ahead to meet the requirements of your reporting intervals.
date-time-min-days-ahead
Default Value: 183
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies, in number of days that remain in the prepopulated calendar, when the calendar table will be updated with the next batch of days ahead. The default value specifies that the maintenance job will update this calendar approximately 6 months before it expires.
date-time-start-year
Default Value: 2012
Valid Values: 1970-2038
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Modified: 8.1.1 (in release 8.1.0, the default value was 2010)
Specifies the year that the calendar starts. When you are setting this option, ensure that you choose a start year that provides sufficient buffer to prevent inconsistencies or unexpected missing dimensions around the start of the calendar. Genesys recommends that you set the value so that the calendar starts at least one year prior to any date that might be encountered in the data. Be aware that Genesys Info Mart uses GMT for internal time references, and this affects exactly when the calendar starts.
For example, if the other [date-time] options that affect the start date are set so that the calendar will start at 00:00 AM on January 1, 2012, and the date-time-tz option is set to Eastern European Time (GMT + 2), the calendar table will be populated with dimensions starting at 02:00 AM on January 1, 2012.
date-time-table-name
Default Value: DATE_TIME
Valid Values: Any string that is a valid table name for your RDBMS
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies the name of the table in the Info Mart database schema. You must manually modify the script that creates the custom calendar table, to specify this value as the table name.
date-time-tz
Default Value: GMT
Valid Values: Any valid Java time zone
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies the time zone for the calendar. You can use any valid time zone that is supported by the version of the Java Runtime Environment (JRE) that runs the Genesys Info Mart Server. For more information about supported time zones, see the documentation about calendar time zones on the Java developer website or other public resources.
Sample public resources:
- http://www.java2s.com/Tutorial/Java/0120__Development/GettingallthetimezonesIDs.htm
- http://en.wikipedia.org/wiki/Zone.tab
first-day-of-week
Default Value: 1
Valid Values: 1-7 (Sunday-Saturday)
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies the day of the week that is considered to be the start of the week. For example, 1 (Sunday) is usually the first day of the week in the United States; for countries that use the ISO 8601 standard, 2 (Monday) is the first day of the week.
fiscal-year-start
Default Value: No default value
Valid Values: Any valid combination of month and day, in M-d format
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: fiscal-year-week-pattern is set to a valid pattern
Introduced: 8.1.1
Specifies the month and day that the fiscal year starts. For example, 1-1 means January 1; 10-1 means October 1. This functionality was introduced in release 8.1.1.
- If simple-week-numbering=true, every fiscal year starts on the fixed date that is specified by this option.
- If simple-week-numbering=false, the fiscal year starts on the first day of the week that contains the date that is specified by this option; however, the actual start date depends on the value of the first-day-of-week option.
Genesys Info Mart adjusts automatically for the floating fiscal year. For example, if simple-week-numbering=false, fiscal-year-start=3-1, and first-day-of-week=1, then:
- Fiscal year 2012 starts on February 26.
- Fiscal year 2013 starts on February 24.
- Fiscal year 2014 starts on February 23.
fiscal-year-week-pattern
Default Value: none
Valid Values: none, 544, 454, 445
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies the pattern for the number of weeks in each month of a fiscal quarter. For example, 544 means 5 weeks in the first month, 4 weeks in the second month, and 4 weeks in the third month of each quarter. A value of none means that the calendar will not be a fiscal one.
min-days-in-first-week
Default Value: 1
Valid Values: 1-6
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: simple-week-numbering=false
Specifies the minimum number of days from the new year that must be in the first week of the year, if simple week numbering is not used and there are no partial weeks in the calendar year. The ISO 8601 standard does not use simple week numbering.
The ISO 8601 definition of the first week in the year is the week that has the first Thursday in it. To conform to the ISO 8601 standard, set simple-week-numbering=false, first-day-of-week=2, and min-days-in-first-week=4.
For example, if simple-week-numbering=false, first-day-of-week=2, and January 1 of the new year is on a Friday, there are 3 days from the new year in the week that starts on Monday, December 28. Therefore:
- If the value of this option is set to 1, the calendar will count the first week of the new year as starting on Monday, December 28.
- If the value of this option is set to 4, the week that starts on Monday, December 28, will be assigned to the previous year, and the calendar will count the first week of the new year as starting on Monday, January 4.
simple-week-numbering
Default Value: true
Valid Values: true, false
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies whether the calendar year and the week-numbering year coincide. For simple week numbering, Week 1 always begins on the first day of the calendar year (for Gregorian calendars, January 1; for fiscal calendars, the day that is specified in the fiscal-year-start option). As a result, the first and last weeks of the year might be partial weeks, because the first week will not necessarily start with the day that is specified by the first-day-of-week option. To comply with ISO 8601 week numbering, set the value of this option to false.