My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 2011/11/01
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
2010-2019
>
2011
>
Agenda Packets - 2011/11/01
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:50:49 PM
Creation date
7/10/2018 4:00:40 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
11/1/2011
Supplemental fields
City Council Document Type
City Council Packets
Date
11/1/2011
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
135
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br /> <br />This material is provided as general information and is not a substitute for legal advice. <br /> Consult your attorney for advice concerning specific situations. <br />RISK MANAGEMENT INFO RMATION <br />MINNESOTA GOVERNMENT DATA PRACTICES ACT: <br />YOU WANT WHAT? WHEN? <br /> <br />Overview <br /> <br />The Minnesota Government Data Practices Act, Minn. Stat. <br />ch. 13, attempts to balance the public’s right to information, <br />individual’s right to privacy, and government’s need to <br />function responsibly. There is nothing in the Act requiring <br />any city to hand over requested information on the spot. <br />While a great deal of the information at city hall is public <br />and must be released when requested, a city is entitled to <br />establish and follow a process for evaluating and complying <br />with data requests. Simply put, it is much better to take a <br />conservative approach when considering a data request, <br />even if that means the data is not released immediately. In <br />the long run, a delay, during which a city confirms the data <br />being requested and ensures that release is permitted under the Act, may prevent a city from being <br />sued for sharing data that should not have been released. <br /> <br />The Act requires government entities, including cities, to identify the types of data they maintain <br />and determine how each type of data is classified. A city must develop a public document <br />identifying these data categories and classifications for data on individuals. (The Act does not <br />require such a document for data that is not on individuals.). This public document must contain <br />the name, title, and address of the city’s “Responsible Authority” and copies of any forms used to <br />collect private data on individuals (i.e., Tennesen Warning). This document must be updated <br />annually. <br /> <br />While the Act does not require that a data request be in written form, a city may require that data <br />requests be submitted in writing and may require the use of a form designed for this purpose. <br />Cities must respond to data requests appropriately and promptly. More than anything else, what is <br />appropriate and prompt depends upon the scope of the request, and may vary depending upon the <br />size and complexity of a city, the type and/or quantity of data requested, the clarity of the data <br />request, and the number of staff available to respond to the request. <br /> <br /> <br /> <br />Highlight <br /> <br />The general presumption of the <br />Act is simple: government data <br />are public unless otherwise <br />classified by state or federal law. <br />Government data that is <br />collected, created, stored, or <br />maintained by a city are public <br />and are accessible for both <br />inspection and copying. <br />
The URL can be used to link to this page
Your browser does not support the video tag.