haunts 0.3.0

How it works

The command will try to access a Google Spreatsheet you must own (write access required), specifically it will read a single sheet at time inside the spreadsheet.

Sheet definition

The referenced sheet must contains a set of columns. Headers names are important but orders matters not. Any additional columns will be ignored.

The partition in multiple sheets is designed to keep every month in a separate sheet, but this is not strictly checked.

Every sheet should contains following headers:

Date

(date)

The day where the event will be created

Start time

(time HH:MM or empty) - _optional_

If povided, the current event will start at given time. This will condition also events defined after this row.

Spent

(number or empty)

How long the event will last. Leave empty to create a full-day event.

Project

(number)

Project name as it’s named in the config sheet (see below)

Activity

(string)

Summary of the event

Details

(string, optional)

Additional text for the event description

Event id

(string)

Leave this empty. It will be filled with the id of the generated event

Link

(text)

Leave this empty. It will be filled with a link to the event inside Google Calendar.

Action

(char)

See below. If empty: it will be filled with an I when an event is created

Configuring projects

The spreadsheet must also contains a configuration sheet (default name is config, can be changed in the .ini) where you must put two columns (with headers):

id

The id of a Google Calendar associated to this project. You must have write access to this calendar.

name

The name of the project, like an alias to the calendar

A project name can be associated to the same calendar id multiple times.

Values in the name column are the only valid values for the Project column introduced above

How events will be filled

Let says you run something like this:

haunts --day=2021-07-08 July

haunts will access the sheet named July in the spreadsheet configured in the .ini file. Only rows where the Date filed will match the --day parameter will be considered.

For every rows that match, haunts will:

• Generate a new event, starting from a default time (this can be configured in the .ini). The event will last for Spent hours

• The next event will start where the previous ended

• If the event will be successfully created, an I will be placed in the Action column. This will make future executions to ignore the line.

• Other columns will be read or filled as described above.

Actions

Possible values you can find (or put yourself) in the Action column:

• I

  execution will just ignore this line

• D

  execution will clear Action, Event id and Link cells for this row. So: next execution will likely fill this line again (this is a poor-man-edit)

OK, but why “haunts”?!

An haunt is a monster from Dungeond&Dragons, which was translated to italian as “Presenza”.

But “presenza” is the same term used in italian for “participation”, so how we call our worklogs.

And filling worklogs haunt us.

0.3.0 (2022-05-02)

• Fixed: START_TIME default was not used. Closes #4

• New: new action: D

• New: added “Start time” feature. Closes #7

• Fix: reduces number of writes. Closes #6

• Fix: do not fail badly when max number of requests per minutes is reached. See #1

• New: added “–config” for initial env configuration, improved documentation

0.2.1 (2022-02-10)

• Fixed full day criteria

0.2.0 (2021-07-29)

• Added support for full-day event

0.1.0 (2021-07-10)

• Initial release