S2 Edits from the app in the research

What the app sends to the research, when, what the research does with it and what it does not accept. Describes the Strom app 3.21.2 (and the research 1.25.2). How the app connects with the research is described in S1. What becomes of an edit of a proven fact is described in R5.2.

S2.1 The tree in the app is the main one

The tree in the app and the tree in the research are two copies. Edits from the app go to the research by sending the whole tree. The research compares what it gave the app, what arrived and what it has now, and writes only what changed in the app. What the research does not write stays in the app and is visible.

• Limits:
  • What the research did by itself meanwhile is never taken as an edit from the app that would undo it.
  • A tree from another program or an older export without the record of the research version it came from: the research takes only new facts and only shows the differences.
  • One send is one entry in the research's history with one source, and it can be undone (S2.7).
• Since: research 1.0.0

S2.2 When edits are sent

Each tree from the research has its own way of sending. It is chosen in the window Research for this tree, section Sending changes.

• Limits:
  • Default option: Manually for a research with an agent, Automatically for a Strom archive and for a research waiting for an agent. A tree connected to the research before app 3.9.0 sends automatically. For such a tree and for a tree opened from the research the app asks once How should changes go to the research?; the way used so far is marked (so far).
  • Automatically sends edits after 2 minutes without another edit, on switching to another tree and on leaving the page. It sends only to a running research and always for one tree at a time.
  • A tree followed live is read-only and sends nothing (S1).
  • The research is not running: edits wait and are sent after it starts. Send can start it through a link in the terminal.
  • The app waits at most 2 minutes for the research's answer. Then it shows "The research didn't answer in time"; the edits stay in the app.
  • After switching from Only load from the research, the first send is always manual through What will be sent.
  • Edits are sent only from the computer on which the research runs. A phone does not send edits (S5).
• Controls: app: Research → Other actions → Research for this tree… → Sending changes; the button Send (Send to research); Send now; Send without preview next time
• Since: app 3.9.0 (research 1.12.0); sending on leaving the page from app 3.16.0

S2.2.1 What will be sent

Before a manual send the app shows the list What will be sent: changed people (new person, deleted, name, birth, death, marriage, event, godparents, witnesses), changed sources with the places where they are cited, couples, places with new coordinates and surname variants. Each group has its own section. After writing it shows in the same way What was written with the sections Written and Not written.

• Limits: when the exact list cannot be computed, the tree is sent as it is and the research writes only the differences.
• Since: app 3.14.0

S2.2.2 Folio, image and call number from the app

An app that keeps the source's fields (A3.9) sends the research the call number, folio, image and other location by fields. The research compares them by fields and writes an edit as an edit of the source's page.

• Deletion: a folio, image or call number a person deletes in the app is deleted by the research too. Undoing the send (S2.7) brings them back.
• Limits:
  • an older app that does not know the fields deletes nothing. An edit of the whole page from an older app replaces the locator and deletes the folio and image entered (undoing brings them back);
  • a value that the app's file still names is not deleted: a folio or image in the page (PAGE), a call number as the whole page or on its own line of the source's note ("Call number: …", in any language). It is better that it stays than that something the app did not see as a field is deleted;
  • the call number of the book and the image number from registered scans are not fields of the source: a deletion in the app does not change them;
  • for a source read by the research, neither an edit nor a deletion is written into the source; a note is written beside it ("folio: removed in the Strom app (was fol. 12v)").
• In the list What will be sent (S2.2.1) a changed call number, folio or image is a change of the source's page.
• Since: app 3.27.0 with research 1.31.0

S2.3 What the research does with sent edits

A research with an agent writes a send at once. A new fact or person from the app is always a Lead with the source "Edits in the Strom app", never Proven. A change of a fact proven by a record becomes a conflict. The detailed rules are in R5.2; transcriptions of sources from the app in R3.5.1.

• Limits:
  • With the research option sync.review on, the research does not write a send at once. It waits for a person's word in the terminal (R6); the app meanwhile shows Waiting for confirmation in the research.
  • After writing, the app loads the research's new version by itself when nothing would be lost in the app.
  • Conflicts that arose from a send are shown by the app with the message Written, N conflicts to decide with Show. They are decided in the research (Decide in the research); until then the value from the app stays in the app.
• Controls: terminal: strom config set sync.review on|off, strom config set sync.edits conflict|user (R5.2.1). App: the window Research for this tree shows what the option means ("Changes are written in the research only after confirmation.").
• Since: research 1.5.0; sync.review from 1.12.0

S2.4 A Strom archive and a research without an agent

A Strom archive and a research waiting for its agent mirror the tree from the app: the word from the app holds. They write every send at once, even when sync.review is on.

• Limits:
  • A change of a fact proven by a record does not create a conflict; the fact from the record is withdrawn with a reason. A conflict of parents and a conflict of a removed person arise here too (R5.2.1).
  • What is deleted in the app, the research sets aside with a reason, and it can be restored.
  • What the Strom archive has and this window of the app never had, the archive does not delete. The app says so at the unwritten edits: the Strom archive still keeps it: this window never had these details.
  • Tasks to verify a transcription from the app do not arise here, because nobody reads (R3.5.1).
• Since: research 1.12.0

S2.5 What the research does not accept

The research can refuse a send as a whole, or write only a part. Edits it did not write stay in the app and nothing is lost.

• Limits:
  • The research postpones writing when the tree is sealed on another computer (Take over on this computer), when the files in a cloud folder are not downloaded yet, or when the disk is full. Until then the edits wait unsent.
  • When the research writes only a part, the app shows Written N, not written M and the reason at each unwritten edit (for example "no common ground: choose in the research").
  • After a refusal, automatic sending stops. It sends again by itself only after the next edit.
• Controls: app: The research didn't accept the changes in the research panel, Try again, Details (to pass on)
• Since: app 3.11.0 (research 1.12.0); postponed writing from research 1.20.0
• From research 1.26.0: a large family tree (roughly 1,500 people and more) taken over on Windows is written whole. Before, it ended with a git error about a command too long (ENAMETOOLONG) and nothing was written.

S2.6 A person removed in the app

A research with an agent does not delete by itself a person or a fact that disappeared in the app. It only notes the removal, and the app says at the unwritten edits: "removed here only: the research noted the removal but deletes nothing by itself; it can be deleted in the research". A Strom archive mirrors the removal (S2.4).

• Limits: when one window of the app removes a person and the person is edited elsewhere meanwhile, the research asks whether the person stays in the tree (R5.2, point 6). The app shows one question per person:
  • Removed in another window: Return to the tree, or Keep removed;
  • Edited elsewhere: Remove from the tree, or Keep in the tree. The research confirms the decision. Then the app loads its version.
• Since: research 1.0.0; the question about a removed person from app 3.16.0 (research 1.20.0)

S2.7 Undoing a send

A send can be undone in the research. The edits in the app stay; only the changes of that send leave the research.

• Limits:
  • From the app the last send can be undone within 7 days. It is confirmed in the research's terminal.
  • After an undo the app sends nothing more until one is chosen: Send again, or keep the undo with Load the research's version (replaces the edits from the app, a backup stays).
  • Loading the research's version can be undone with Restore the state before loading.
• Controls: app: Research → Other actions → Undo last send · terminal: strom sync undo
• Since: app 3.4.0, research 1.0.0
• From research 1.26.0: only a person may undo a send (strom sync undo) and discard a sent tree that waits (strom sync discard); the research refuses the agent. The edits in the app stay after discarding and can be sent again.