My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Amending Chapter 2 Polices & Procedures Governing City-Owned Technologies, Facebook Standards, Social Media and Social Networking Polices and Procedures
sbend
>
Public
>
Common Council
>
Legislation
>
Ordinances
>
2014
>
Amending Chapter 2 Polices & Procedures Governing City-Owned Technologies, Facebook Standards, Social Media and Social Networking Polices and Procedures
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/1/2015 3:28:44 PM
Creation date
12/12/2014 9:13:47 AM
Metadata
Fields
Template:
City Council - City Clerk
City Council - Document Type
Ordinances
City Counci - Date
12/8/2014
Ord-Res Number
10343-14
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
14
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
Ordinance Amending SBMC Creating New Section 2 -9.1 <br />Page 2 <br />Section I. Chapter 2, Article 1 of the South Bend Municipal Code is hereby amended by the <br />inclusion of new Section 2 -9.1 which shall read in its entirety as follows: <br />See. 2-9.1 Policies and Procedures Governing City -Owned Technologies, Facebook Standards, <br />Social Media and Social Networking. <br />(a) Purpose and Intent. The following policies and procedures shall govern the official <br />and the gal personal use of any and all city -owned technologies; and privately owned <br />teehfielegies, .. e of the usage of Council - related Facebook, social media and social networking <br />services and tools by any person elected to serve as a member of the South Bend Common Council. <br />These policies and procedures shall govern various types of communication and public engagement <br />including but not limited to: <br />1 Email and text messaging[ <br />2. Media Sharing — Examples: You Tube, iTunes <br />3. Blogging/Microblogging — Examples: WordPress, Blogger, Twitter <br />4. Social Networking — Examples: Facebook, MySpace, LinkedIn, Ning <br />5. Document and Data Sharing Repositories: Examples: Scribd, S1ideShare, Socrata <br />6. Social Bookmarking — Examples: Delicious, Digg, Reddit <br />7. Widgets — Examples: Google Maps, AddThis, Facebook "Like" <br />(b) City -Owned Technologies. All technology resources owned by the City of South <br />Bend, Indiana, which are permitted to be used by a member of the South Bend Common Council shall be <br />used in compliance with the following regulations: <br />1. Technology resources are to be used primarily to serve the governmental need of the City of <br />South Bend. <br />2. Technology resources maybe used for personal purposes on a limited basis, provided there is: <br />i. No marginal cost to the City of South Bend <br />ii. No interference with government responsibilities <br />iii. No political activities <br />iv. No accessing of sites which promote laws which are contrary to the city, state or federal <br />governments <br />Indiana's Public Access Counselor Luke H. Britt ruled that private email accounts are public record if they involve official <br />business under Indiana's Access to Public Records Act. In the Advisory Opinion in Formal Complaint 14 -FC -199 issued on <br />October 8, 2014, he noted that "when a public official avails himself to any communication medium, whether it is phone, email <br />or text message, he is availing himself of the Indiana access laws when communicating in his official capacity... the public <br />official is basically on the honor system to either produce the requested emails or identify an APRA exception to <br />disclosure... the best transparent practice would be to implement a policy where email communication on private accounts <br />dealing with public business is considered potentially disclosable public record. <br />
The URL can be used to link to this page
Your browser does not support the video tag.