Can I document a dataset without an account or upload?

Local browser workflow

There is no account, no sign-in and no server-side project. You open a local file, the parser and the profiler run inside the page, and the authored project is saved into this browser's storage on this device. Every station, including export, works without a network connection once the page is loaded.

Offline shell boundary

The first load needs the network, because that is when the shell installs itself for offline use. After that the studio opens in airplane mode, and any later change to the product arrives only the next time you load it online. A second browser, a second profile or a second device starts empty, because storage is per browser and per origin.

Export for continuity

Browser storage is a working copy, not an archive: clearing site data, a private window, a device reset or a new laptop removes it. Download a versioned checkpoint on a schedule you can actually keep, store it where you control it, and import it once into a second profile so you know the file restores. Import validates the digest and replaces the project only afterwards, so a damaged file leaves your work alone.

Worked example from the sample project

Load the studio once over the network and wait for the shell to install, then switch the device to airplane mode and reopen it. The sample project, or your own, opens and every station works: import a local file, author folios, run the review, freeze an edition and export the packet. Nothing about documenting a dataset needs a server.

The corollary is the part worth planning around. Browser storage is a working copy, and a cleared profile, private browsing, a device reset or a new laptop will all remove it. Download a versioned checkpoint, keep it somewhere you control, and restore it once into a second browser profile so you know the file you are keeping is a file that works. The digest embedded in the checkpoint detects accidental or hostile modification, and import replaces a project only after validation, so a bad file leaves your work alone rather than half-overwriting it.

What this does not do

• You cannot install the shell offline; the first load needs the network.
• Browser storage is not an archival guarantee and offline reopening is not an availability guarantee.
• A checkpoint digest detects modification but does not authenticate an author.

Do this in the studio

Export a checkpoint on a schedule you can keep, not when you remember.

1. Open the Editions station and download a versioned checkpoint.
2. Store it in a location you control, not only the browser download folder.
3. Test a re-import at least once so you know the file restores.

Open the studio at the Editions station

Related reading

• End to end worked example
• Security and local-data model
• The handoff packet