Laserfiche WebLink
Item 2 <br />Page 2 of 3 <br />4. Can council choose to set 300 (or some number) for residents and use 100 for business <br />related/or potential lawsuit related (of course there are challenges of figuring out what the <br />use is)? <br />a. Can we ask the purpose — the why? <br />The City cannot require disclosure of the identity of the requestor or state a reason for to justify a <br />request. <br />The City maybe could differentiate based on the data itself but not the requestor. For example, the law <br />allows additional fees to be charged for data that has commercial value or data that has been enhanced <br />by the City at the request of the requestor. Establishing a policy where the City is differentiating <br />between residents and nonresidents or between different data use purposes should not be done. <br />5. Are we required to provide an estimate (we probably would provide a range)? <br />No, but doing so is a good idea prior to actually making the copies so the city does not go through the <br />work of redacting and making copies and then have the requestor refuse to pay. The work around for a <br />requestor is always just to come in and view the data and then request up to 100 (or the page limit) and <br />avoid paying the fees. <br />6. We know the law states "reasonable" with respect to time, want to confirm that "term" <br />includes keeping the requestor updated on the progress — example Fred was on vacation for <br />two weeks and only Fred can explore his email (effectively) which constitutes the majority of <br />the data — as do most of our requests, its almost always emails. <br />There is no requirement that the City keep the requestor updated on progress, but again, this is <br />probably a good idea to avoid any claim that the city is not responding in an "appropriate and <br />prompt" manner (Minn. Stat. 13.02, subd. 2(a)) and when a request for copies is made then the <br />response time must be "as soon as reasonably possible." However, this is more of a policy <br />decision (with legal implications). <br />The "reasonable" standard is subjective to the scope of the request and could also be impacted by <br />things like employee availability, but again, the response time must be "prompt and appropriate." <br />Discussion: <br />Council needs to balance the democratic values of transparency and sharing of public data with <br />imposition to staff time and fiscal consequence that could benefit a few at the expense of many. <br />The legislature provides guidance on this balance, with the 100 page threshold which includes <br />emailing or the making of copies as the staff time to assemble and email is the same as <br />assembling and copying. <br />Staff would endeavor to provide estimates for those exceeding the 100 pages (or some other <br />threshold council could establish) prior to fulfilling that request. <br />An additional issue would be obtaining payment prior to fulfilling the request as we had a recent <br />request that was fulfilled, only to have the requestor not come to pick it up. <br />The issue of large data requests came up at a recent City Manager/Administrator professional <br />meeting in which nearly all those present they impose a fee/charge for large data requests. <br />The Mounds View Vision <br />A Thriving Desirable Community <br />