My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2008_0428
Roseville
>
City Council
>
City Council Meeting Minutes
>
200x
>
2008
>
CC_Minutes_2008_0428
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/20/2008 2:04:04 PM
Creation date
6/13/2008 9:40:44 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
4/28/2008
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
26
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
Regular City Council Meeting <br />Monday, Apri128, 2008 <br />Page 8 <br />Clarification was sought by individual Councilmembers and provided by staff that <br />the mailing list included a general geographic mailing area, as requested by the <br />applicant for the surrounding neighborhood, and was not specifically addressed as <br />a response to those who had communicated with the City, as the letter may have <br />indicated in the first paragraph. Staff noted that this was current policy to make a <br />mailing list available to the public, and further noted that personal information in- <br />cluded in the Council packet and made public had been redacted prior to distribu- <br />tion. <br />Applicant, Mark Smith, 19545 Hampshire Court, Prior Lake, MN (owner <br />and CEO of Cash-n-Pawn) <br />Mr. Smith apologized that, in the haste of he and his partner to get the letters out <br />in the mail, they made the wording generic, indicating that it was in response to <br />previous correspondence to the city regarding their application, rather than ad- <br />dressing those previously addressed concerns, and as a general information com- <br />munication to the entire neighborhood. Mr. Smith took full responsibility, and <br />asked that City staff not be blamed for his error in attempting a more intensive <br />broadcast of information, rather than his personally going door-to-door in the <br />neighborhood. Mr. Smith advised that the Frequently Asked Questions enclosure <br />with the letter was an attempt to respond to previously voiced or written com- <br />ments and concerns, included in previous public agenda packets at the Planning <br />Commission and/or City Council level. <br />Mr. Smith recognized the misconceptions and past images of pawnshops, and of- <br />fered to answer specific questions on the operation of his business. Mr. Smith <br />noted that going into the Planning Commission meeting, there had been lots of <br />opposition, but after due diligence and dialogue, views had changed. Mr. Smith <br />spoke to his support at the legislature of the State's Automatic Pawn System <br />(APS) and spoke in support of other state and city regulatory requirements. <br />Mr. Smith reviewed the pawn process and identification required of the seller and <br />merchandise; regulatory compliance with law enforcement agencies and require- <br />ments; statistical information that less then one percent of the applicant`s business <br />involved the Police Department; misconceptions that pawnshops traffic stolen <br />material; typical clients using pawnshops; and the majority of the business (60%) <br />in the retail market. Mr. Smith advised that every transaction was entered in the <br />APS system with that information submitted on a daily basis to the National <br />Crime Information Center (NCIC). Mr. Smith noted that any stolen merchandise <br />required him to take a financial loss, thus providing additional incentive for him <br />to operate with integrity. Mr. Smith further reviewed the state and city regula- <br />tions under which he operated, in addition to the $10,000 annual license fee, and <br />per transaction fee, with any noncompliance making his license subject to revoca- <br />tion. <br />
The URL can be used to link to this page
Your browser does not support the video tag.