Slashdot Mirror


OneDOJ to Offer National Criminal Database to Law Enforcement

Degrees writes "The Washington Post is reporting that the Justice Department is building a massive database, known as 'OneDOJ'. The system allows state and local police officers around the country to search millions of case files from the FBI, Drug Enforcement Administration and other federal law enforcement agencies. The system already holds approximately 1 million case records and is projected to triple in size over the next three years. The files include investigative reports, criminal-history information, details of offenses, and the names, addresses and other information of criminal suspects or targets. From the article: 'Civil-liberties and privacy advocates say the scale and contents of such a database raise immediate privacy and civil rights concerns, in part because tens of thousands of local police officers could gain access to personal details about people who have not been arrested or charged with crimes. The little-noticed program has been coming together over the past year and a half. It already is in use in pilot projects with local police in Seattle, San Diego and a handful of other areas, officials said.'"

2 of 184 comments (clear)

  1. Re:About time by fyngyrz · · Score: 5, Insightful

    The USSC has already established that local, state and federal government can accumulate information on people when it feels that such accumulation is in its interests, and further, that it can expose that information to the public, making a complete mockery of any idea of privacy.

    The precedent was set using sex offenders and in particular, those sex offenders who had been convicted prior to the instantiation of the registry laws. Forcing those individuals to be on those lists was ruled "not punishment" and hence not subject to ex post facto as laid out in the constitution and subsequent court decisions.

    Now the government can list anyone, anytime, on any list it likes, and there is nothing US citizens can do. Other lists have been showing up and causing trouble such as the no-fly list. Nothing anyone can do about that, either. Lists aren't a bad thing, according to every branch of the government.

    The fact is, when US citizens gave up those freedoms to hand that little extra bit of crucifixion to sex offenders, you gave it up for everyone else, too. US citizens should have screamed bloody murder at the registry laws, you should have screamed bloody murder at any attempt at ex post facto punishment, and you should have screamed bloody murder at the USSC's ridiculous decision that "registry" is a local, state and federal interest.

    The dead, smug silence at the fate of the sex offender - and the "terrorist" - has led the USA to a pitiful shadow of the freedom it once stood for. Sophistry has undermined ex post facto, habeas corpus, the commerce clause, the 2nd amendment, freedom of speech, and now... now you're worried about the feds sharing information. Good luck climbing back up that slope.

    --
    I've fallen off your lawn, and I can't get up.
  2. Some Concerns and Questions by martyb · · Score: 5, Insightful

    Sigh. I don't know where to begin.

    First off, I understand there is some not insignificant value to this idea. The concept of making it easier for law enforcement to gather already available information on a suspect is quite laudable. It bothers me when I hear of how a suspect in a "major investigation" was actually picked up on an unrelated offense, and let go, because the arresting officers were unaware of the other outstandings on the person. It would be nice if we could stop this from happening. In fact, I'm sure many lives could be saved. If I had a loved one who was murdered, and then found out that law enforcement had actually captured the suspect beforehand, AND LET HIM GO, you can bet I'd be outraged. But is this proposal the right way to go about it? What is the REAL COST to you and to me. Not just in dollars and cents, but also in our freedoms as citizens.

    My concern is more with the implications and implementations of this concept, and how easily it can be abused.

    Data Quality: People have been known to not give their correct name to the police. Some people have used multiple names (aliases, AKA, etc.) Further, given that even touch-typists will occasionally make typographical errors (and not everyone is a touch-typist, either), I can forsee a not-insignificant amount of "bad" data finding its way into the system. Someone with a name similar to mine commits an offense, but gets recorded UNDER MY NAME. See: false-positives (Type I error) and flase-negatives (Type II error) here: Type I and type II errors.

    • They may not find this person when they go looking for his info - because it's NOT under his name.
    • They might find this person's offense(s) should they go looking under my name - say, for a minor traffic offense.

    Feed the Database: If it's so benign, I want to see a requirement that they seed the database with information on EVERY SINGLE FEDERAL AND STATE OFFICIAL. President of the USA, every senator, representative, judge, police officer, sheriff, District Attorney, etc. If your wage is paid by our taxes, then your info gets loaded into their system automatically. If there is an uproar about doing this for THEM, then maybe they should not be doing it to US. Got to stamp out any possible corruption, yanno? Besides, if you have done nothing wrong, then you have nothing to hide. Right?

    Log EVERY access: CRUD - Create, Read, Update, Delete. Storage is cheap. Log EVERY SINGLE time the data is accessed complete with the date, time, source IP, accessor's name (See the Feed the Database, above, what was requested, etc. If what you are doing with the database is on the up-and-up, then you have nothing to hide. Log it.

    Prosecute Abuse of the System: Run analyses every single day to seek out abuse of the system. And Prosecute Them. Publicize The Prosecutions. Enter the prosecutions into the system. What's good for the goose is good for the gander.

    Data Validation and Correction: It's going to happen. Some data is going to be inaccurate. (Consider the problems that exist with the accuracy of people's credit reports. And the difficulties, effort, and cost involved in getting those mistakes rectified.) How can I:

    1. Get access to the information they have on me?
    2. Contest its accuracy?
    3. Ensure corrections are applied?

    Looking ahead: Data storage costs are coming down. Some localities have ever-present video cameras recording all activity in their purview. I can imagine a time when advanced techniques exist to go searching through these archives looking for, extracting, and logging the identities and activities of all within their field of view (face recognition, scene analyses, cell phone GPS, etc.) Combine all these streams and extracts into a central DB and one can easily go trolling for perps.

    So, in short, I can see some good intentions behind this. Quite laudable in fact. But, I am NOT convinced this is a good idea, never mind whether or not they can come up with a good implementation.