If you didn't want to waste bandwidth, you shouldn't have launched senseless personal attacks and false allegations. You obviously wouldn't cease your personal attacks unless I rehashed the entire sequence of posts leading up to your so-called "PROOF" of a lie that was never uttered. You had posted snipets of posts and claimed that those snippits PROVED THAT I WAS A LIAR. If you hadn't embarked on this voyage, you wouldn't have had to deal with the rocky seas. Get over the fact that you were wrong and drop it..
I like the FAQ part, it proves I'm right, there are problems with the database, and they're hoping to fix them, but they don't consider the problems terminal. They can admit it, why can't you?
I HAD already POSTED the damn database error part of the FAQ. The errors in the database DO NOT include duplicate records. In case you're going to try to weasel your way around this and say that I'm LYING, I'll provide that post again just to prove that you are simply being flippant and that your position is intellectually bankrupt.
Here's post #208
From LCA Database FAQs
Are Database Errors Corrected?
The data in the database is an exact replication of the DOL data that was obtained using the Freedom of Information Act. This data is not modified or corrected for errors because a lot can be learned from the errors the data contains. It is not the mission of ZaZona.com to correct errors in our government databases.
So I was wrong, the data is from the Department of Labor instead of INS. HOWEVER, the data IS an exact duplicate of that provided by the DOL. SO, if there's a problem with the data, it is the DOL that either collected the data incorrectly or the data is in fact valid.
208 posted on 11/05/2002 10:09 AM PST by FormerLurker
So there you go, I supplied you with the link to the FAQ in post 208 so that you could read it. Have you ever heard of the expression, RTFFAQ? If you HAD read the FAQ you would have seen the following info...
What Types of Errors Exist in the Database?
There are many errors contained in this database. Most of them occur when employers enter something incorrectly or forget to fill out a field. Another major source of errors are caused when the Dept. of Labor scans the LCAs into digital format.
A major source of errors occurs when employers categorize the jobs. When employers fill out the Labor Condition Application they are required to categorize the job by using a three digit code defined in the Dictionary of Occupational Codes (DOT). These codes range from 000 to 999. The codes appear on the database results page as OCC followed by a three digit code.
It is the employer's responsibility to assign the DOT codes and job titles. These are not reviewed by the Department of Labor (DOL) for errors or inconsistencies. Gross errors can occur because the employer assigns wrong codes and/or vague job titles. Here are some of the major reasons those errors could occur:
Human resource people or clerical staff are not properly trained to assign codes. They might not understand the job title enough to categorize it.
The employer want to be intentionally vague so that they have more flexibility in hiring a variety of different H-1Bs
Intentional errors could be entered to change how prevailing salaries are calculated. If, for instance, a software engineer is considered for a position, he could be classified as a Programmer/Analyst since they typically are on a lower pay scale.
Negligence or mistakes can never be ruled out as a source of error.
The DOT system is outdated and doesn't define categories correctly in many cases
Errors can happen at the DOL when LCAs are scanned into the digital format. They use an OCR that can misinterpret data items.
There are many types of errors observed in the database including:
Missing fields
shifted fields
misspelled words
numbers that are too large or too small
numbers that have an extra digit
numbers that are missing digits
unknown or vague job classifications
incorrect job codes
Year 2000 date errors
Here is an example of some of the types of errors encountered in the database. Table A is an example of the raw data entries as received by the DOL. The job code, or DOT, column was all "030" but that isn't the correct code for the job titles given. Table B shows how the data would appear if the errors in the job code were corrected.
|
|
|
You kept on insisting that you were seeing duplicates, and are again trying to claim that there is a problem with duplicates where in fact that isn't one of the listed problems with the data. You may want to refresh your memory with post #250. Here I'll just post the relevant segment in an ATTEMPT to reduce bandwidth..
Finally, we have ARCSIGHT INC Sure enough, it IS a US corporation. And sure enough there ARE records with the same start date. HOWEVER, if you look at the applications they filed for the TEMPE office, they have one application for 1 SOFTWARE ENGINEER each on the same date and TWO applications for 5 SOFTWARE ENGINEERS with the same date as the other applications. It becomes readily apparent that if they filed even ONE application with only ONE worker and ONE application with FIVE workers all with the same start date, that it is IS common practice to file separate applications with the same start date for the same location, salary, and job title. You've just proven that your "bad data" theory is a "bad" assumption.
Don't use up any more bandwidth. Drop it, you were wrong. And DON'T ever call me a liar again. |