Skip to content

Commit 8822cd3

Browse files
tmoostingclaude
andcommitted
README: the Notion door has read two real exports (since 0.47.0), the folders-by-title layout and the flat one; folders named by title and id still unseen
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 9afba92 commit 8822cd3

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ report = import_notion("Export.zip", "my-world")
105105
print(report.render())
106106
```
107107

108-
A database whose title is one of the 22 types (`Characters`, `Locations`, any case, singular or plural), or that has a `Type` column naming one per row, becomes elements of that type. A column becomes a field when its name matches the field's (`Birth Date` is `birth_date`), and a relation column becomes a link when it matches a link field and its pages are in the export. Every other page becomes a Narrative, and so does each row of a database whose type the door cannot tell (supertype `Article`, the database's name as subtype). Nothing is dropped: a column that doesn't fit is kept as `x_notion_<column>`, and attachments a page links to are copied into `media/notion/`. Ids come from Notion's page ids, so importing the same export twice gives the same folder. The run ends with a report naming every column it could not place and every link it could not resolve, so you can see what to rename in Notion before the next export. No AI, no account. It is built on Notion's documented export shape; no real export has been through it yet.
108+
A database whose title is one of the 22 types (`Characters`, `Locations`, any case, singular or plural), or that has a `Type` column naming one per row, becomes elements of that type. A column becomes a field when its name matches the field's (`Birth Date` is `birth_date`), and a relation column becomes a link when it matches a link field and its pages are in the export. Every other page becomes a Narrative, and so does each row of a database whose type the door cannot tell (supertype `Article`, the database's name as subtype). Nothing is dropped: a column that doesn't fit is kept as `x_notion_<column>`, and attachments a page links to are copied into `media/notion/`. Ids come from Notion's page ids, so importing the same export twice gives the same folder. The run ends with a report naming every column it could not place and every link it could not resolve, so you can see what to rename in Notion before the next export. No AI, no account. It has read two real exports of one small workspace, one with folders for sub-pages and one flat (the door's test fixtures); a third layout, folders named by title and id, is built from Notion's documented shape and not yet seen in a real export.
109109

110110
A world kept in LegendKeeper becomes a folder from LegendKeeper's own export file (Project Settings, Export; the `.lk` file or the JSON one), with no key and no account:
111111

0 commit comments

Comments
 (0)