Repository navigation
Data and Export
When you save an association in Learn → Learn dates, the entry contains:
| Field | Description |
|---|---|
| Number / year | The digit string you want to remember |
| Mnemonic | Your memory phrase or word |
| Note | Optional plain text, maximum 1024 characters |
| Major system | The Major system the entry was created under |
| Word language | The language the mnemonic word came from, when it came from a dictionary |
| Favourite | Whether you starred the entry |
| Timestamps | Created / updated times |
| ID | Stable identifier used for editing and import merge |
An entry you typed by hand has no word language, because a hand-written mnemonic has no dictionary provenance.
Data is stored locally on the device.
Export/import covers only your saved mnemonic entries. It does not export:
- the bundled historical event dataset;
- the Major System dictionaries;
- derived skeletons, Major codes, or dictionary suggestions (those are recalculated in the app);
- your statistics and achievements, your interface language, or the Major system and word languages you have selected.
From Options → Data, you can export saved entries to a versioned JSON file and share or save it with the system UI. Export is always started by you: the app prepares the file and hands it to the system share sheet, and you decide where it goes.
Import validates the file first. The app shows a short summary — how many entries were found, how many are new, how many already exist — and asks for confirmation before merging.
Merge rule: if an imported entry has the same ID as a local entry, the local entry wins and the conflicting import is skipped. New IDs are added. A file with any invalid item is rejected as a whole.
Older export files remain importable. Fields added in later versions are optional when reading, so a file written by an earlier version of Dzejnik loads unchanged.