Peg Ostrander
River cruise account (the Douro, 2025)
saved Apr 3, 2019 07:50
1linked record
Fields
| Name | River cruise account (the Douro, 2025) |
|---|---|
| Passcode variant | Web Login |
| Passcode | Douro-Oct-2025! |
| peg.ostrander@badgermail.example | |
| Description | Made for the October 2025 cruise. Kept for the brochures, and for 2027. |
Linked to
1 record→ the link goes from this record; ← it comes from the other one. These are the edges the build gives the app. A name in the text is only a match on the words and is never treated as a link.
Comments
0
Comments are added in the local viewer; this copy is read-only.
In the app
missing
From the app's own code (viewer/app_export.sh): Not made yet: run viewer/app_export.sh retired-couple.
One step out
As the app receives it
1
The graph nodes the build makes for it: the record, and its phones, emails, addresses, pictures and files.
{
"$type": "n_type_passcode",
"id": "n_pc_cruise_account",
"createdAt": "1554277858673",
"name": "River cruise account (the Douro, 2025)",
"passcodeVariant": "Web Login",
"email": "peg.ostrander@badgermail.example",
"passcode": "Douro-Oct-2025!",
"description": "Made for the October 2025 cruise. Kept for the brochures, and for 2027."
}
Source
personas/retired-couple/records/passcodes.yaml:457
- id: pc-cruise-account kind: passcode for: me name: River cruise account (the Douro, 2025) passcodeVariant: Web Login email: peg.ostrander@badgermail.example passcode: "Douro-Oct-2025!" description: Made for the October 2025 cruise. Kept for the brochures, and for 2027.