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 />On occasion, a complaint will result in a city taking disciplinary action against an employee. Prior <br />to what is called a “final disposition” only the existence and status of the complaint are public. <br />Once a final disposition occurs, then the disciplinary action is public along with specific reasons <br />for the action and data documenting the basis for the action. It is important to note that if no <br />disciplinary action is taken, no final disposition occurs. When this happens, only the existence and <br />status of the complaint are public. When discipline is imposed, the key is determining when the <br />disposition is final. <br /> <br />For a non-union employee, final disposition occurs when a city makes its final decision about <br />discipline. For a union employee, if arbitration under a union contract is a possibility, final <br />disposition occurs at the end of the arbitration proceedings or at the expiration of the time period <br />during which arbitration may be requested. <br /> <br />Other Issues to Note <br />While there are probably as many potential data practices issues and questions as there are <br />Minnesota cities, some issues tend to come up repeatedly. Some of the more common data <br />practices issues and considerations are noted in the following sections. <br /> <br />Elected Officials <br />The Act addresses data on applicants for election or appointment separate from personnel data. <br />However, the Responsible Authority may determine that elected and appointed officials are to be <br />treated as employees for purposes of applying the Act. In that case, both the personnel data noted <br />in the Act and the following are considered public data on applicants for election or appointment: <br />name, city of residence, education and training, employment history, volunteer work, awards and <br />honors, and prior government service or experience. <br /> <br />Law Enforcement Data <br />Law enforcement agencies are responsible for a tremendous amount of data. Both because of the <br />frequency with which law enforcement data are requested and because of the potentially sensitive <br />nature of the data, it is essential to have a well thought-out policy documenting procedures for <br />requesting and releasing law enforcement data. The following describes the classification of <br />commonly requested law enforcement data: <br /> <br />“Request for service data” are collected or created when a member of the public requests law <br />enforcement services. Request for service data are public data and include data on the nature of the <br />request or activity complained of, the name and address of the person making the request, the time <br />and date of the request, and the response initiated by the law enforcement agency. <br /> <br />The audio recording of a 911 call made to request service from a law enforcement, fire, or medical <br />agency is private data with respect to the individual making the call. However, a written transcript <br />of the audio tape is public, unless it reveals the identity of an individual who is entitled to privacy. <br /> <br />“Response or incident data” are collected or created by a law enforcement agency documenting the <br />agency's response to a request for service or describing actions taken by the agency on its own <br />initiative. Response or incident data are public data and include the date, time, and place of the
The URL can be used to link to this page
Your browser does not support the video tag.