TimeslotDAG
TimeslotDAG is a helper library to work with calendar periods in a graph pattern. It has no support for periods under a day, nor deals with timezones in any way.
It was written as a companion library for the olap-in-memory library, which itself is a companion library for monitool, a full-featured monitoring platform targeted at humanitarian organizations.
TimeslotDAG does not aim in any way to replace full-featured date libraries.
The main goals were:
- Have an easier API than prevalent date libraries for the task at hand (business intelligence / OLAP).
- Immutable, easy to localize, easy to serialize objects.
- Lightweight enough to be called thousand of times when aggregating report data.
- Meet specific needs
- Proper epidemiological weeks numbering.
- Splitted weeks.
- Weeks starting on Saturday (Middle east).
TimeslotDAG runs in both NodeJS and the browser, and has no production dependencies.
Typescript and Flow typings are provided for auto-completion and type-checking, and should work without out of the box.
npm install timeslot-dagconst slot = TimeSlot.fromValue('2010-01')
slot.periodicity // 'month'
slot.firstDate // Date('2010-01-01')
slot.lastDate // Date('2010-01-31')
slot.previous() // TimeSlot('2009-12')
slot.next() // TimeSlot('2010-02')
...TimeSlots can be built in two ways.
// With the constructor by passing a *slot identifier*, which is a unique string representing any given slot.
const slot1 = TimeSlot.fromValue('2010') // '2010' is a slot identifier
// With any date which is inside of the desired range, and the periodicity name
const slot2 = TimeSlot.fromDate(new Date('2010-05-25T03:00:00Z'), 'year')
// Both slots that were created in this sections are equal.
slot1 == slot2 + month_week_sat <--+
| |
+ month_week_sun <--+
| |
+ month_week_mon <--+
year <--+ semester <--+ quarter <--+ month <-----+ +--+ day
+ week_sat <--+
| |
+ week_sun <--+
| |
+ week_mon <--+
The year, semester, quarter, month and day periodicities, represent what is expected in the Gregorian calendar.
The week_sat, week_sun and week_mon periodicities represent 7 days weeks, repectively starting on saturday, sunday or monday.
// The week starts on Monday 23rd, and finishes on Sunday 29th.
const date = new Date('2020-03-23T00:00:00Z')
const slot = TimeSlot.fromDate(date, 'month_week_mon')
// Weeks are numbered in the year
slot.value // '2020-W13-mon'
slot.next().value // '2020-W14-mon'
// Slot duration is always 7 days.
slot.firstDate // Date(2020-03-23)
slot.lastDate // Date(2020-03-29)
slot.next().firstDate // Date(2020-03-30)
slot.next().lastDate // Date(2020-03-05)The month_week_sat, month_week_sun, month_week_mon represent weeks which are splitted at month boundaries, repectively starting on saturday, sunday or monday.
This is commonly used when data is collected weekly in order to power reports which are delivered both weekly and monthly, to avoid introducing errors.
// The week starts on 23rd, and finishes on 29th of march
const date = new Date('2020-03-23T00:00:00Z')
const slot = TimeSlot.fromDate(date, 'month_week_mon')
// Slot duration is 7 days
slot.value // '2020-03-W5-mon'
slot.firstDate // Date(2020-03-23)
slot.lastDate // Date(2020-03-29)
// Next slot duration is 2 days (until end of the month)
slot.next().value // '2020-03-W6-mon'
slot.next().firstDate // Date(2020-03-30)
slot.next().lastDate // Date(2020-03-31)
// Next slot duration is 5 days (so that next slot is aligned with monday)
slot.next().next().value // '2020-04-W1-mon'
slot.next().next().firstDate // Date(2020-04-01)
slot.next().next().lastDate // Date(2020-03-05)
// Next slot will be 7 days againSlots identifiers are constructed to be alphabetically sortable inside each periodicity, and represent a unique period across all periodicities.
Those characteristics make them well-behaved with OLAP tools (PowerBI, Tableau, ...).
They are formatted in the following way:
- day:
[yyyy]-[mm]-[dd] - week_sat:
[yyyy]-W[ww]-sat - week_sun:
[yyyy]-W[ww]-sun - week_mon:
[yyyy]-W[ww]-mon - month_week_sat:
[yyyy]-[mm]-W[w]-sat - month_week_sun:
[yyyy]-[mm]-W[w]-sun - month_week_mon:
[yyyy]-[mm]-W[w]-mon - month:
[yyyy]-[mm] - year:
[yyyy]
const slot = TimeSlot.fromValue('2010-03-01')
slot.humanizeValue('en') // 'March 01, 2010'
slot.humanizePeriodicity('en') // 'Day'
slot.humanizeValue('fr') // '01 Mars 2010'
slot.humanizePeriodicity('fr') // 'Jour'English, French and Spanish are supported.
To avoid bundling all locales if using webpack, use either IgnorePlugin or ContextReplacementPlugin.
The slot.toParentPeriodicity(newPeriodicity) method allows knowing in which parent slot the current slot is included.
Aggregating between year, semester, quarter, month, day and splitted weeks (month_week_*) is trivial and behaves like expected in the Gregorian calendar.
To aggregate TimeSlots with periodicity week_* (normal 7 days weeks) into months or larger periods, the week will go in the month which contains the most days.
// Tuesday
const date = new Date('2019-12-31T00:00:00Z')
const slot = TimeSlot.fromDate(date, 'day')
// List of periodicities this TimeSlot can be grouped into
slot.parentPeriodicities // ['month_week_sat', ..., 'semester', 'year']
// Both the day and containing week starting on saturday are 2019,
// however the containing week starting on monday is 2020
slot.toParentPeriodicity('year') // TimeSlot('2019')
slot.toParentPeriodicity('week_sat').toParentPeriodicity('year') // TimeSlot('2019')
slot.toParentPeriodicity('week_mon').toParentPeriodicity('year') // TimeSlot('2020')The slot.toChildPeriodicity(newPeriodicity) method allows listing the children slots which make up the current slot.
The same rules than with slot aggregation are used.
// Tuesday
const date = new Date('2019-12-31T00:00:00Z')
const slot = TimeSlot.fromDate(date, 'week_mon')
// List of shorter periodicities which can compose this TimeSlot
slot.childPeriodicities // ['day', 'month_week_mon']
// Disagregate into those
slot.toChildPeriodicity('day') // [TimeSlot('2019-12-30'), ..., TimeSlot('2020-01-05')]
slot.toChildPeriodicity('month_week_mon') // [TimeSlot('2019-12-W6-mon'), TimeSlot('2020-01-W1-mon')]Did you consider using any of the other alternatives? They are likely to be better maintained!
The most well-known are:
- Going native - JavaScript Date objects represent a single moment in time in a platform-independent format.
- Luxon - A powerful, modern, and friendly wrapper for Javascript dates and times.
- date-fns - Modern JavaScript date utility library
- Moment.js - Parse, validate, manipulate, and display dates and times in JavaScript.
- js-joda - Immutable date and time library for javascript
- day.js - Fast 2kB alternative to Moment.js with the same modern API
- Support other calendars used in administrations/healthcare around the world