File documents from storage

The dry run: what filing this project's folder would do, before anything is written.

This is the only dry run there is. It reads the folder mapped to this project, lists what filing would do to the register, and writes nothing until you accept it.

A connection is workspace-wide and a folder is per project, so the workspace sync page reports the connection and this page does the filing.

Reading the plan

The plan lists what would be added and what would be superseded. Nothing is deleted by a sync. The counts at the top are the whole plan; below them the rows are a sample, capped so a first read of a large folder is a page and not a wall, and applying files everything counted whether or not its row was drawn. While the library is being read the page says so; the first read of a large folder takes a while, and every read after an apply covers only what changed. A file that has disappeared from the folder does not remove the document that was filed from it, because the register is the record and the folder is only where the file happened to live.

Versions of one document

Two files that read as versions of one document, once words like revised, final, v2 and a date are stripped from their names, are listed as a pair for a person to rule on; the sync never decides which governs. A name that is only a kind of document is not a name: every invoice is not a version of the first invoice, so a stem that strips to one kind word pairs with nothing.

Where it starts from

The first run reads the whole folder. Every run after that reads only what has changed since the last one, because the register remembers where the previous read stopped. A folder too large for one run is read across several: the first run files what it read and says so, and the next continues from that point rather than from the top. Choosing a different folder for the project starts a fresh read of the new one.

When the library cannot be read, the page says so in place of a plan, and the apply button waits. The sentence says which it was: Microsoft asking for a pause before the folder is read again, with how long; a connection that has lapsed and needs reconnecting in Settings; a connection that cannot read this library; or no answer at all. A short pause is waited out inside the read without your noticing. Nothing on the register changes on a failed read.

Which library is read

Only the one you picked, and the server holds that line, not the picker. A library can be saved for the workspace or for a project only if it is one the connected account can see, from the same list the picker offers; anything else is refused with a sentence saying so. Changing the folder inside a library that is already saved asks nothing, so a folder can move while storage is unreachable.