The Photo-Sequence Metadata Gap

Case 23-009185 | Card 8 | 4880 T Street, Sacramento CA 95819

The City's own photograph numbering puts the two pictures behind this case last in their day, after three other cases. The produced Documents inventory [M013] lists five photographs of 4880 T Street dated 04/10/2023: IMG_1372 [M013], IMG_1373 [M013] and IMG_1374 [M013], captioned at the front of the dwelling, at its entry, and "Card left at site" [M013]; then IMG_1492 [M013] and IMG_1493 [M013], both captioned "View from neighbors lot of work performed" [M013]. IMG_1374 and IMG_1492 are 118 numbers apart, and pages produced under Request 26-1863 from three other Sacramento case files carry that same day's photographs inside that interval: IMG_1483 [R.26-1863.1], IMG_1484 [R.26-1863.2], IMG_1486 [R.26-1863.3], IMG_1487 [R.26-1863.3], IMG_1488 [R.26-1863.3] and IMG_1489 [R.26-1863.3]. As produced, four separate case files fall into one ascending 04/10/2023 photo-name sequence, and the two 4880 T backyard frames are its last two.

Those two frames are the only photographs the produced case file [M013] lists behind the verification of the garage addition. Paul Lovato's RE-INSPECTION entry of 04/10/2023 [M001] reads: "I met with neighbors to access their backyard to verify work performed. I did verify there is an addition to the detached garage going on... I took pictures of what I saw from where I was standing. A N&O will be requested." [M001] The City's strongest pages are not in dispute: the inventory dates both frames 04/10/2023 [M013], and the Notice and Order carries "Dated: 04/12/2023" [M124], two days later. That inventory date is the date typed into the case page. The one request drawing the line between the two, Request 26-1963, asked for the system fields behind every entry and said so: "I am asking for the system-created information, not just the activity date typed into the case page or whatever shows up on a print report." [R.26-1963.1] Request 26-1964 asked for the case audit trail. Both were closed the next morning, 05/18/2026, with "The City does not have any records responsive to this request. All records were provided under 26-1549." [R.26-1964.1] The file the City produced under Request 26-1965 in May 2026 [R.26-1965.1] holds no native image file, no created or modified field, and no audit entry for those two frames; the camera's own numbering is the only ordering of that day the City has supplied.

Which produced record fixes when IMG_1492 and IMG_1493 [M013] were captured — the native files, their Date Created and Date Modified fields, or the case audit trail for April 10 to 12, 2023 — when the requests for exactly those, Request 26-1963 [R.26-1963.1] and Request 26-1964 [R.26-1964.1], were closed on 05/18/2026 with "The City does not have any records responsive to this request" [R.26-1964.1], and the only date the City has supplied for them is the one "typed into the case page" [R.26-1963.1]?

IN PLAIN TERMS

The City's file lists five photographs of the property from April 10, 2023: three at the front of the house, two from a neighbor's yard [M013]. Between them the numbering runs 118 higher, and photographs the City produced from three other cases that day [R.26-1863.3] fall in between — so in the City's own sequence the backyard pictures are the last two. They are the only pictures behind the note in which the inspector wrote he had verified an addition to the garage [M001]. The order came two days later [M124]. The date on the two pictures is the one typed into the case page. Asked for the system-created dates [R.26-1963.1] and the audit trail [R.26-1964.1] behind them, the City wrote it had no such records. The question for the City: which record it produced fixes when those two pictures were taken?

RECORD CHAIN

  1. April 10, 2023 — the same day in three other case files. Pages produced under Request 26-1863 carry photographs dated 04/10/2023 from three other Sacramento cases. R.26-1863.1 lists IMG_1483 with a front-of-dwelling caption; R.26-1863.2 lists IMG_1484 as tree damage at a roof; R.26-1863.3 lists IMG_1486 and IMG_1487 as beds in a sunroom, IMG_1488 as a county room-and-board record and IMG_1489 as signs someone is living in a garage, on a page carrying Case 23-007617 and 7311 Krishna Dr.

    The first two pages print neither a case number nor a street address. Their attribution to Case 23-000633 and Case 23-000351 is those pages' provenance in the 26-1863 production [R.26-1863.4], delivered 2026-05-12.

  2. April 10, 2023 — the four files in one sequence. Set out in the order the names run: 1372 [M013], 1373 [M013], 1374 [M013] at 4880 T Street; 1483 [R.26-1863.1]; 1484 [R.26-1863.2]; 1486 [R.26-1863.3], 1487 [R.26-1863.3], 1488 [R.26-1863.3], 1489 [R.26-1863.3] at 7311 Krishna Dr; then 1492 [M013] and 1493 [M013] at 4880 T Street.

    As produced, four separate case files align into one ascending same-day photo-name sequence, with unlisted numbers remaining in the interval.

  3. April 10 and 11, 2023 — where the verification narrative is logged. The RE-INSPECTION narrative [M001] appears twice on the Activities page under 04/10/2023, and again in the Notes section of the same file under 04/11/2023 (Card 7: the two dates carried by one verification narrative, and the produced inventory's lack of any photograph dated 04/11/2023).

    No version of the entry names a photograph, a file name, or a time.

  4. April 12, 2023 — the order, two days after the photographs. The Documents inventory logs the order as no23-009185.pdf, dated 04/12/2023 [M013]; the order's face carries "Dated: 04/12/2023" [M124]. Its paragraph 2 reads: "That the conditions which render the building(s) sub-standard and/or dangerous are set forth on the attached list of violations." [M124]

    Sacramento City Code § 8.100.720(A)(2) [SCC.8.100.720(A)(2)] places in the order itself "a brief and concise description of the conditions found to render the building substandard" [SCC.8.100.720(A)(2)]. The list attached to this order carries the B31 and B59 entries [M125] (Card 1: placeholder entries that name no structure, no work, no location, and no permit) and states "Neither interior nor exterior has been completely inspected." [M125]

    The order's face names no photograph and no file name (Card 9: the packet the City served and the replies it sent carried no picture and said nothing of what any picture showed; Card 2: who inspected before the order issued, and from where).

  5. May 17–18, 2026 — the requests for the dates behind the entries. Thirty-seven months after the photographs were logged, Request 26-1963 asked, for every entry in the activity log, notes, documents, photos, communications and correspondence, for the system fields Date Created, Date Modified, Created By and Modified By, and stated: "I am asking for the system-created information, not just the activity date typed into the case page or whatever shows up on a print report." [R.26-1963.1] Request 26-1964 asked for the case-level audit trail, event log, change history, version history and workflow history.

    Both were received 05/17/2026 and closed the next morning [R.26-1964.1], 05/18/2026, by back-reference to the April 2026 production, Request 26-1549 (Card 4: the City's written completeness determinations; Card 49: the record-integrity notice filed on that April thread, which drew no response).

FULL CIRCLE

The City's first available answer is that the photographs were taken on April 10, 2023: the inventory dates IMG_1492 (1).jpg and IMG_1493.jpg 04/10/2023 [M013], the inspector's entry of that day says "I took pictures of what I saw from where I was standing" [M001], and the order did not issue until "Dated: 04/12/2023" [M124], so where in that day the camera numbered them is immaterial.

The day is conceded; the record behind the day is the gap. The inventory date is the activity date typed into the case page. Request 26-1963 asked for the field behind it and drew the distinction in its own words: "I am asking for the system-created information, not just the activity date typed into the case page or whatever shows up on a print report." [R.26-1963.1] The City closed it the next morning: "The City does not have any records responsive to this request. All records were provided under 26-1549." [R.26-1963.1] Request 26-1549 is the April 2026 case-file export [R.26-1549.1]; the request had asked for what sits behind that export, not the export again. On the City's own answer, the typed date is the only date there is.

The City's second available answer is that IMG_####.jpg names are assigned by a camera and can be renumbered or resequenced when files are uploaded, so the order of the names says nothing about the order of capture.

The records that would say otherwise were asked for and answered. Request 26-1964 sought the case audit trail, event log, change history and version history and was closed on 05/18/2026 [R.26-1964.1] with the same sentence. On the produced record the name sequence is the only ordering of that day the City has supplied, and it is the City's own.

What would defeat this card is one produced record fixing when IMG_1492 [M013] and IMG_1493 [M013] were captured: the native image files, the Date Created and Date Modified fields for those two rows of the Documents inventory, or the case audit trail for April 10 to April 12, 2023. None of the three is in the file the City produced under Request 26-1965 and closed on 05/22/2026 [R.26-1965.1], and Request 26-1963 and Request 26-1964 asked for those categories and were closed with "The City does not have any records responsive to this request. All records were provided under 26-1549." [R.26-1964.1] Card 4 is the completeness baseline (what the file the City produced means, and does not mean).

APPLICABLE LAW

SOURCE CITATIONS USED BY THIS CARD

CARD REFERENCES