<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="https://www.loc.gov/MARC21/slim https://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="https://www.loc.gov/MARC21/slim">

  <leader>03808nam a2200277   4500</leader>
  <controlfield tag="001">393961</controlfield>
  <datafield tag="010" ind1=" " ind2=" ">
    <subfield code="a">9780833087102</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">393961</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">20160530d2014       y0pory50      ba</subfield>
  </datafield>
  <datafield tag="101" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="200" ind1=" " ind2=" ">
    <subfield code="a">License plate readers for law enforcement</subfield>
    <subfield code="b">Recurso eletr&#xF3;nico</subfield>
    <subfield code="e">opportunities and obstacles</subfield>
    <subfield code="f">Keith Gierlack ... [et al.]</subfield>
  </datafield>
  <datafield tag="210" ind1=" " ind2=" ">
    <subfield code="a">Santa Monica</subfield>
    <subfield code="c">RAND Corporation</subfield>
    <subfield code="d">2014</subfield>
  </datafield>
  <datafield tag="215" ind1=" " ind2=" ">
    <subfield code="a">1 CD-ROM</subfield>
    <subfield code="d">12 cm</subfield>
  </datafield>
  <datafield tag="225" ind1=" " ind2=" ">
    <subfield code="a">Safety And Justice Program</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">Project supported by Award No. 2010-IJ-CX-K007, awarded by the NationalInstitute of Justice, Office of Justice Programs, U.S. Department of Justice. Ficheiro de 885 KB em formato PDF (124 p.).</subfield>
  </datafield>
  <datafield tag="330" ind1=" " ind2=" ">
    <subfield code="a">Preface. Figures and tables. Summary. Acknowledgments. Abbreviations. Chapter one &#x2013; Introduction. Background. Rationale for NIJ-Sponsored Research. Key influencing factors in LPR utility. Report structure.  Chapt er Two - Framing the LPR environment. Major uses. Reactive policing. Analytic uses. Cost considerations. Benefits and challenges. Benefits. Challenges. Privacy concerns. Chapter Three &#x2013; Methodology. Study population categorization scheme. Department size and population. Border locations. Geographic clusters. Selection criteria within categories. Interview protocol. Chapter Four - LPR uses in different operational environments. Access to resources: Big v. Small. LPR on the border. Geographic clusters. Chapter Five - The legal aspect of LPR privacy concerns. Fourth Amendment. Contemporary Fourth Amendment Doctrine. State Constitutional restrictions.  State regulation of license plate reader use. Specific prohibitions. More-general state restrictions on data collection. Liability risk in use. Constitutionally relevant dimensions. Conclusion. Chapter Six - Common themes and challenges in LPR use. Technology-driven themes. LPR utility depends on data, human resources. Interoperability among jurisdictions requires several elements. Data storage and retention: technology drives. Operationally driven themes. LPR funding is largely external. Major case uses for LPR: often department-specific. System structure and policies vary. Privacy concerns. Benefits and challenges. Benefits. Challenges. Chapter Seven - Agency lessons learned. Estimate and secure the proper amount of funding required. Explore grant options. Be prepared to pay for operations and maintenance. Develop policies for LPR usage, data access, and data storage. Think outside the box when deciding how to employ LPR. Enhance the benefits of LPR via cooperation with other agencies and jurisdictions. Regional cooperatives enhance LPR&#x2019;s utility. Police departments need to link LPR systems to &#x201C;effective&#x201D; data sources. Effective implementation frequently requires cooperation with other agencies. Ensure &#x201C;successful&#x201D; implementation and sustainment. Be prepared and committed for a long learning curve. It helps to have an LPR &#x201C;Champion&#x201D;. Do media outreach to facilitate public acceptance. Plan to maximize use of LPR units. Officer training is important. Allow for officer discretion when acting on LPR hits. Plan for data storage. LPRs generate large amounts of data. Cloud-based data storage lowers costs but runs some risks. Chapter Eight &#x2013; Conclusions. Major use cases. Privacy issues. Interoperability issues. Recommendations for enhanced use of LPR. Appendixes: A. Case study summaries. B. Interview protocol. References.</subfield>
  </datafield>
  <datafield tag="606" ind1=" " ind2=" ">
    <subfield code="a">TECNOLOGIA</subfield>
    <subfield code="9">234237</subfield>
  </datafield>
  <datafield tag="606" ind1=" " ind2=" ">
    <subfield code="a">POL&#xCD;CIA</subfield>
    <subfield code="9">234553</subfield>
  </datafield>
  <datafield tag="606" ind1=" " ind2=" ">
    <subfield code="a">VE&#xCD;CULO AUTOM&#xD3;VEL</subfield>
    <subfield code="9">241256</subfield>
  </datafield>
  <datafield tag="606" ind1=" " ind2=" ">
    <subfield code="a">IDENTIFICA&#xC7;&#xC3;O DE VE&#xCD;CULO AUTOM&#xD3;VEL</subfield>
    <subfield code="9">322619</subfield>
  </datafield>
  <datafield tag="606" ind1=" " ind2=" ">
    <subfield code="a">ESTADOS UNIDOS</subfield>
    <subfield code="9">334103</subfield>
  </datafield>
  <datafield tag="710" ind1=" " ind2=" ">
    <subfield code="a">LICENSE PLATE READERS FOR LAW ENFORCEMENT</subfield>
    <subfield code="9">358130</subfield>
  </datafield>
  <datafield tag="955" ind1=" " ind2=" ">
    <subfield code="x">Oferta</subfield>
  </datafield>
  <datafield tag="995" ind1=" " ind2=" ">
    <subfield code="1">0</subfield>
    <subfield code="4">PJCD_258_000000000000000</subfield>
    <subfield code="5">2022-06-06</subfield>
    <subfield code="6">PJCD258</subfield>
    <subfield code="9">426509</subfield>
    <subfield code="a">PJ</subfield>
    <subfield code="c">PJ</subfield>
    <subfield code="f">PJ1CD258_22</subfield>
    <subfield code="k">PJCD258</subfield>
    <subfield code="n">2022-06-06</subfield>
    <subfield code="o">0</subfield>
    <subfield code="r">MO</subfield>
    <subfield code="x">Oferta</subfield>
  </datafield>
</record>
