My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
8.5. SR 08-19-2013
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2011 - 2020
>
2013
>
08-19-2013
>
8.5. SR 08-19-2013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2013 10:18:32 AM
Creation date
8/16/2013 9:25:52 AM
Metadata
Fields
Template:
City Government
type
SR
date
8/19/2013
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
8
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
City of <br /> Elk Request for Action <br /> River <br /> To Item Number <br /> Mayor and City Council 8.5 <br /> Agenda Section Meeting Date Prepared by <br /> General Business August 19, 2013 Scott Baumgartner, City Prosecuting Attorney <br /> Item Description Reviewed by <br /> Review and Provide Comment on Amendments to Cal Portner, City Administrator <br /> Various Section of the City Code Regarding Reviewed by <br /> Offense Classifications/Fines Peter Beck, City Attorney <br /> Action Requested <br /> Review and comment on spreadsheet. Staff will bring this item back to the September 3, 2013, Council <br /> meeting for formal adoption of an ordinance. <br /> Background/Discussion <br /> The courts have begun a project to add local ordinance and administrative rule violations to the MN <br /> Court Information System(MNCIS) offense code table. Adding ordinance violations to the MNCIS <br /> offense code table will allow fine amounts and other unique offense data to auto populate in MNCIS the <br /> same way it does today for statutory violations. Currently,the MNCIS offense code table does not <br /> include unique offense codes for individual ordinance and administrative rule violations. The <br /> consequences if valid, current, and complete ordinance data is not added to the MNCIS offense code <br /> table include: <br /> • If the MNCIS offense code table and charged ordinances do not match, eCitations and <br /> eComplaints will be auto rejected and initiation of paper citations and complaints into <br /> MNCIS will be delayed until the issue of unmatched charge codes is resolved. <br /> • MNCIS will assign the incorrect case type and/or level of offense, resulting in incorrect case <br /> processing and incorrect collateral consequences for offenders. <br /> • Incorrect codes and/or descriptions of ordinance violations could result in a higher volume <br /> of contested hearings and possible dismissals. <br /> For these reasons, the courts wanted to provide prosecuting agencies with an opportunity to validate and <br /> supplement the current local ordinance data for their jurisdictions so valid, current,and complete <br /> ordinance data gets inputted into the MNCIS offense code table to avoid citation entry delays and <br /> rejected efilings. <br /> It's important to note that although prosecuting agencies can recommend that an ordinance violation be <br /> payable and the corresponding fine amount, only judges have the authority to designate an ordinance <br /> violation as payable and set the payable fine amount (See Minn.R.Crim.P. 23.03). <br /> Included with this report is a table identifying the city's most commonly cited ordinance violations, their <br /> designated level of offense,whether they are payable offenses, and if so,the designated fine amount. The <br /> redlining identifies changes, additions, and deletions to what the courts previously had on file for the city. <br /> P a w E R E U 6 Y <br /> NaA f RE] <br />
The URL can be used to link to this page
Your browser does not support the video tag.