Niko on 19 Nov, 2016 05:06 PM
You would have to bring the ICS file into some kind of CSV file. Each line from the CSV file will be a timing in Timelime after the export. The timing's task is determined by the import tokens "Task (top level)" and "Subtask...".
I think there are some tools that can convert ICS to CSV, but I have never tried it myself. You will have to bring the ICS file into a suitable CSV format that Timelime CSV Import can read.
Fr. George Mang...
on 19 Nov, 2016 07:54 PM
One other question I have is “how many, and what tokens” are enough. It seems that when I have too many, and take one out, I get the message there are not enough; and when I add one extra, I get the message there are too many.
Niko on 20 Nov, 2016 01:55 PM
The date and times of each timing must be unambiguously declared for a row.
For example you can select the "Date", "Start Time", and "Duration" tokens.
But selecting the "Date", "Start Time", "End Time", and "Duration" tokens is too much information.
If you have redundant fields in the CSV file, you can just put an "Ignore" token at the appropriate place.