HL-012 · DATA PRACTICES
Due-process disclosure and statutory data access are related but distinct.
SOURCE HIERARCHY
Read the City rule first, then applicable Minnesota authority, the national constitutional standard, judicial interpretation, and the original record. The final layer states the supported application and its limits.
01
The current §170.10 source and City open-information materials provide the local procedural setting, but the reviewed Saint Paul rule does not itself establish an automatic right to the complete investigative file before this informal appeal. L-01
02
Minnesota Statutes §§13.03, 13.04, and 13.82 separately govern public-data access, data-subject access and accuracy challenges, and specified law-enforcement data. Each requires an actual request, identified data, classification, and response record before a statutory violation can be assessed. L-07 L-08 L-09
03
The Fourteenth Amendment asks whether material evidence was disclosed sufficiently for a meaningful response. That procedural question is distinct from statutory data access and does not automatically create civil discovery in an informal appeal. US-01 US-03
04
Goss, Brock, and Mathews address notice, supporting-evidence substance, and process appropriate to the stakes. None holds that Minnesota’s Data Practices Act automatically required Saint Paul to produce its entire file before this hearing. SC-01 SC-03 SC-04
05
The transcript records counsel asking “what actually the reports were” and “who made them.” Later correspondence and produced materials must be evaluated against the exact request and response chain; the reviewed record does not establish a completed pre-hearing Chapter 13 request. R-05 R-09 R-10
06
The sources support separate due-process-disclosure and MGDPA analyses. They do not establish automatic prehearing production, a completed statutory violation, or that all responsive data would have been public.
The hearing record shows a request to understand “what actually the reports were.” That raises a procedural question about knowing and answering material evidence. A separate MGDPA claim requires an actual Chapter 13 request, recipient, requested data, classification, response, and timing. The reviewed materials do not yet establish a pre-hearing Chapter 13 request or an MGDPA violation. R-05 L-07 L-08 L-09
Did the appeal process provide a meaningful opportunity to know and answer evidence materially relied upon?
Was a request made, what data were public or accessible to the data subject, how were records classified, and how did the City respond?
| Date | Request | Recipient | Response / production | Classification or timing issue |
|---|---|---|---|---|
| Before April 17 hearing | No Chapter 13 request identified in reviewed material | Unresolved | Unresolved | Do not characterize automatic nonproduction as an MGDPA violation |
| April 17 hearing | Counsel requested the reports and who made them in the appeal proceeding | Parks Director / City counsel | Information and police material were offered for later follow-up | Procedural disclosure question; not automatically a Chapter 13 request |
| April 20–22 | Later counsel/City record exchange | Counsel | CAD, later staff material, complaints, and production confirmation appear in the reviewed record | Need the complete request and response chain before assessing MGDPA timing |
Section 13.04, subdivision 4 may provide a process for a data subject to contest public or private data about that person. This page does not state that Josh submitted or completed such a challenge.
The MGDPA does not automatically require the City to hand over its complete file before an appeal hearing. Each record’s classification and each actual request must be established. The separate due-process disclosure question may still remain.