Laserfiche WebLink
MmRR )20?.U3tN), suhp. <br />2 <br />See Chapter 4, Section I-B- <br />I. <br />Minn. Slat 913(iU 1. whd <br />IPAD 97-6021 fan 1 i, <br />1997)', and 9?-U I4 (Apr. 1. <br />1997). <br />M1finn. Slat ~ I1}9}, <br />Minn Srat § I}U.OS_ <br />Mayors may wonder what right of access they themselves have to <br />data that isn't public. Whether an elected official or staff, the law <br />says that access is limited to individuals "whose work assignments <br />reasonably require access." Whether the mayor falls into that legal <br />description is a question for each city to decide with the help of the <br />city attomey. For this reason, mayors shouldn't be surprised if they <br />don't get a key to the city offices just because the mayor of another <br />city does. And of course, there's always a difference between <br />whether one can access private or confidential data and whether one <br />should. <br />Since the data a person collects, creates, receives, maintains, or <br />disseminates in the capacity of mayor is government data, a mayor <br />may wish to be careful about where that data is created, collected, <br />etc. Government data can easily, even accidentally, be created at <br />home that is both public and subject to a retention schedule. Also, <br />mayors may wish to take care in what they say in their official <br />capacity within a-mails and even text messages. <br />The MGDPA states that correspondence between individuals and <br />elected officials is private-though either party may make it public. <br />At the same time, correspondence between elected officials and <br />employees is public un ess t-T t'ns informations ecificall <br />c assf le as non- u Ic. 1s even applies to the city administrator's <br />s a us reports to the city council. The attomey-client privilege, <br />however, would apply to documents created for the purpose of <br />giving legal advice, such as a letter between the city attomey and a <br />city official. <br />The Open Meeting Law prohibits the closing of a meeting solely to <br />discuss private data (except in limited circumstances clearly listed in <br />the statute), and provides that private data may be discussed openly <br />at any public meeting without fear of liability or penalty as long as <br />the release of the data is reasonably necessary to conduct the <br />business the data relates to. If private data needs to be discussed at a <br />public meeting, it is recommended that the city try to protect the <br />information by assigning numbers, letters, or similar designations to <br />it, and that those designations be used instead of the actual data. <br />Discussing private data in a closed meeting does not change the fact <br />that it is private. Therefore, even though an open meeting might have <br />just occurred in which private data was discussed, that data shouldn't <br />be discussed with family, friends, or the media as if it is now public <br />information. <br />While inmost cases private data may be discussed in an open <br />meeting without fear of liability, mayors should remember the <br />situations mentioned in [he previous section in which the Open <br />Meeting Law requires a meeting to be closed. <br />~" <br />MiMnoo <br />Ma}on I S <br />Asa~o,ian«: <br />