My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
02-25-2015 Council Packet
>
City Council Packets
>
2010-2019
>
2015
>
02-25-2015 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/23/2015 9:34:46 AM
Creation date
2/23/2015 9:29:26 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
117
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).
View images
View plain text
RELEVANT LINKS: <br />Moberg v. Indep. Sch. Disr. <br />No. 281, 336 N.W.2d 510 <br />(Minn. 1983). See Section 11.- <br />G.-6. Serial meetings. <br />Minn. Stat, § 13.02, subd. 7. <br />See Handbook for Minnesota <br />Cities, Chapter 27 for more <br />information about records <br />management. <br />As a result, councilmembers should make sure that any comments they make <br />on social media are factually correct, and they should not comment on issues <br />that will come before the council in the future for a quasi-judicial decision, <br />such as the consideration of whether to grant an application for a conditional <br />use permit. <br />It is also important to remember that serial discussions between less than a <br />quorum of a public body that is subject to the open meeting law could <br />violate the open meeting law under certain circumstances. Therefore, city <br />councils and other groups to which the open meeting law applies should take <br />a conservative approach and avoid using letters, telephone conversations, <br />email, and other such technology if the following circumstances exist: <br />• A quorum of the council will be contacted regarding the same matter. <br />• City business is being discussed. <br />Another thing councilmembers should be careful about is which email <br />account they use to receive emails relating to city business because such <br />emails would likely be considered government data that is subject to a <br />public -records request under the Minnesota Government Data Practices Act <br />(MGDPA). The best option would be for each councilmember to have an <br />individual email account that the city provides and city staff manage. <br />However, this is not always possible for cities due to budget, size, or <br />logistics. <br />If councilmembers don't have a city email account, there are some things to <br />think about before using a personal email account for city business. First, <br />preferably only the councilmember should have access to the personal email <br />account. Using a shared account with other family members could lead to <br />information being inadvertently deleted. Also, since city emails are <br />government data, city officials may have to separate personal emails from <br />city emails when responding to a public -records request. <br />Second, if the account a city councilmember wants to use for city business is <br />tied to a private employer, that private employer may have a policy that <br />restricts this kind of use. Even if a private employer allows this type of use, <br />it is important to be aware that in the event of a public -records request under <br />the MGDPA, or a discovery request in litigation, the private employer may <br />be compelled to have a search done of a councilmembers' email <br />communication on the private employer's equipment or to restore files from <br />a backup or archive. <br />What may work best is to use a free, third -party email service, such as gmail <br />or Hotmail, for your city account and to avoid using that email account for <br />any personal email or for anything that may constitute an official record of <br />city business since such records must be retained in accordance with the <br />state records retention requirements. <br />League of Minnesota Cities Information Memo: 11/14/2014 <br />Meetings of City Councils Page 21 <br />
The URL can be used to link to this page
Your browser does not support the video tag.