Importing Calendars
Calendaria imports calendar data from other Foundry calendar modules and from external calendar sites.
Supported sources
Section titled “Supported sources”| Source | Live | JSON |
|---|---|---|
| Calendaria JSON | ✓ | |
| Obsidian.MD | ✓ | |
| Fantasy-Calendar.com | ✓ | |
| Mini Calendar | ✓ | ✓ |
| Seasons & Stars | ✓ | ✓ |
| Simple Calendar | ✓ | ✓ |
| Simple Timekeeping | macro¹ |
¹ Simple Timekeeping exports through a macro. See Simple Timekeeping below.
The Obsidian.MD row covers the Calendarium plugin for Obsidian. Upload the plugin’s data.json file.
Request an importer for a source that is not listed.
Import process
Section titled “Import process”Open Settings > Module Settings > Calendaria > Calendaria Settings. The Home tab opens first; click Open Importer in the Active Calendar section. The module settings list also carries a Calendar Importer entry whose Open Importer button opens the same dialog.
- Pick an import source from the dropdown. A ✓ beside a source means its module is installed and enabled.
- Drag the export file onto the drop zone, or click the zone to browse for it. For a source marked with a ✓, click Import from Installed Module instead and skip the file.
- If the source holds more than one calendar, pick one from the Calendar dropdown.
- Review the preview.
- Set each row in the Notes & Events list to Skip, Festival, or Note.
- Click Import.
The X beside the loaded file name clears the file and the preview.
The imported calendar opens in the Calendar Editor. Adjust it there, then click Save.
Import preview
Section titled “Import preview”The preview shows the calendar name, the counts of weekdays, months, moons and seasons, the days per year, and the current date read from the source. Import Options below it holds the Calendar ID and Calendar Name the new calendar will be created under. Both are editable.
Notes and events
Section titled “Notes and events”Each note or event the importer could date gets a row with three radio buttons.
- Skip. The item is not imported.
- Festival. The item becomes a festival on the calendar.
- Note. The item becomes a calendar note backed by a journal entry.
Each row arrives with one option already selected, chosen by the importer from the source data. Change only the rows you disagree with. The three buttons above the list set every row at once.
Current date
Section titled “Current date”The source calendar’s current date appears in the preview. Saving the imported calendar jumps world time to that date, but only when at least one row was imported as a Note. If every row is Skip or Festival, or the source carries no notes, world time is left alone and you set the date yourself from Set Date & Time on the Home tab.
Undated events
Section titled “Undated events”Fantasy-Calendar.com, Obsidian.MD, and Mini Calendar exports can hold events with no date attached. Those events never reach the Notes & Events list, and nothing is created for them in the world. Copy the ones you want out of the source export by hand.
Simple Timekeeping
Section titled “Simple Timekeeping”Simple Timekeeping exports through a macro rather than a direct upload.
- Select Simple Timekeeping in the importer and click Copy Macro. Paste it into a new script macro and save.
- Disable Calendaria, enable Simple Timekeeping, then reload the world.
- Run the macro. It downloads
stk-export-*.json. - Re-enable Calendaria, reload, then upload the JSON through the importer.
Post-import
Section titled “Post-import”The save dialog carries a Set as Active Calendar checkbox that switches to the new calendar immediately.
A calendar whose ID matches an existing calendar is saved under that ID with a numeric suffix.
Festivals detected during import are not listed on the Festivals tab until you save. The tab shows a notice counting the imported festivals that will be created on save. Save the calendar, then reopen it to edit them.
Troubleshooting
Section titled “Troubleshooting”Import fails
Section titled “Import fails”The importer prints the reason in a red panel below the Import Source fieldset. A parse failure names the JSON error. A validation failure names the missing piece, such as a calendar with no months, a month with no days, or a missing time configuration. Re-export from the source application and try again.
Missing data
Section titled “Missing data”- Complex recurrence patterns may simplify to basic yearly or monthly recurrence.
- Custom fields unique to the source may not transfer.
- OR-based conditions from Fantasy-Calendar are split into separate notes, each renamed with a branch counter appended to the event name.
- Ordinal recurrence from Seasons & Stars, the Nth weekday of a month, imports as the first of the month. Nothing marks the change in the importer.
- Month-only conditions from Fantasy-Calendar import as a festival spanning that entire month.
- Intercalary months from Simple Timekeeping do not import as months. Each becomes a festival, so the month count in the preview is lower than the source calendar’s.
- Multi-day events keep their duration on import.
Notes not appearing
Section titled “Notes not appearing”Imported notes belong to the imported calendar. Check that it is the active calendar, and that the notes fall inside the date range on screen.
Report an importer issue if a supported source still fails to import.