cityoffulton.us

File structure

Notes: This is free-form text with no consistent column structure. The data appears to be unstructured operational reports from the Fulton Police Department, with no repeating columnar format. Values include officer names, shift times, equipment status, and operational notes, but they are not organized into tabular columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, and role designations. There are no personal identifiers (PII) such as names, contact details, or sensitive personal data in any column. Values represent shift schedules, equipment codes (e.g., Rifle, Car), operational categories (e.g., BRVMNT, NBA), and role titles (e.g., Deputy Chief, Officer). No columns map to PII fields.

File structure

Notes: This is an unstructured document containing free-form text logs from the Fulton Police Department. There are no consistent columns or delimiters; instead, it's a series of operational reports with officer names and other non-PII operational data. No structured PII columns are present.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but none of the columns map to PII fields. Column 0 contains names, but these appear to be officer assignment codes or shift names rather than personal names of individuals. Column 2 contains numeric codes that look like officer identification numbers (OINs), but these are internal operational identifiers, not traditional PII like SSNs or usernames. All other columns contain shift schedules, equipment assignments, and operational codes that are internal to the department and not personally identifiable information. Per the rules, internal IDs (like officer identification numbers) must be skipped.

File structure

Notes: The file appears to be free-form text containing unstructured operational reports from the Fulton Police Department. The lines contain mixed content (shift times, officer names, equipment, OINs) without a consistent delimiter or column structure. No identifiable PII columns can be mapped due to the unstructured nature of the data. This is typical of raw breach dumps containing operational documents rather than tabular PII.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational documents from the Fulton Police Department, not personal PII. Columns describe shift schedules, assignments, equipment, and roles (e.g., 'Rifle 1', 'Car 1', 'Deputy Chief'). No PII fields (email, phone, dob, name, etc.) are present. Values like 'Curtis' appear to be placeholder names or codes, not actual personal names. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags, and organizational codes.

File structure

Notes: This is a free-form text file with no consistent column structure. The content appears to be internal operational documents from the Fulton Police Department, including shift reports, officer assignments, and equipment details. The data contains officer names (e.g., 'Ja. Marino', 'Levea', 'Brown') and other operational details, but lacks a structured format with consistent delimiters across rows. While names are present, the unstructured nature prevents column mapping. The presence of names and operational details suggests this should be processed as unstructured text for further analysis.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file but all columns contain internal operational data (officer names, shift times, equipment codes, duty types) that are NOT personally identifiable information per the exclusion rules. Column0 contains officer names but these are internal duty rosters, not public personal records. All other columns are shift times, equipment codes, vehicle assignments, duty types, and status flags. None map to any PII fields (email, phone, dob, address, etc.).

File structure

Notes: This is a free-form text file with no consistent delimiter or row structure. The content appears to be operational logs from the Fulton Police Department, including officer names (Pappa, Hahn, Hogan), OINs (officer identification numbers), equipment details, and shift information. While it contains potentially sensitive personnel data, it lacks a structured columnar format with headers and consistent delimiters across rows, making it unsuitable for column-based PII mapping. The unstructured format requires special processing to extract any embedded PII.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment, assignments). Column1 contains officer names but these are employee identifiers rather than personal PII per breach context. No genuine PII fields (email, phone, dob, address, etc.) are present. All columns map to skip categories: officer names treated as internal IDs, numeric codes, shift times, equipment types, departmental designations.

File structure

Notes: This is an unstructured document format. The data appears to be free-form text with no consistent delimiter structure. The content consists of operational reports from the Fulton Police Department with officer names, equipment details, and shift information, but lacks any columnar structure that would allow for PII mapping. The values appear to be mixed text and codes without a fixed schema.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment, assignments). No PII fields detected — values are officer identifiers, shift codes, equipment types, and duty statuses. Names like 'Curtis' appear but are likely officer nicknames/codes, not personal names. All columns map to skip categories (internal IDs, flags, timestamps, vehicle/product data, etc.).

File structure

Notes: This is a free-form text file containing unstructured operational logs from the Fulton Police Department. There are no consistent column delimiters or header rows; instead, it appears to be line-by-line narrative entries with varying formats. No PII columns can be mapped due to the unstructured nature of the data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be operational/assignment data (names of officers, shift times, equipment types, duty codes). No PII fields detected. Column0 contains officer names but these are likely officer identifiers or duty roster labels rather than personal names, and there are no associated personal identifiers like emails, phones, or addresses. All other columns are shift times, equipment codes, duty types, and status flags.

File structure

Notes: This is free-form text document containing operational reports and shift rosters from Fulton Police Department. There is no consistent delimiter or structured columns across rows — entries vary widely in format and content. While some lines contain officer names (Pappa, Hutchinson, Okun) and identifiers (OIN numbers), these appear interspersed in free-text lines without a fixed column layout. The file lacks any header row or consistent structure, meeting all criteria for unstructured format. No column mapping is possible as there are no defined columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment, assignments) but none contain direct PII fields. Column0 contains officer names but these are job titles/operational identifiers rather than personal names; Column1 is numeric codes; Column2 appears to be officer identification numbers (OINs) but these are internal IDs, not public PII; all other columns are shift times, equipment codes, assignment types, and status flags. Per exclusion rules, internal IDs and operational codes must be skipped.

File structure

Notes: This is a free-form document with no consistent column structure. The data appears to be operational logs from the Fulton Police Department, with entries like officer names, shift details, equipment, and timestamps. There are no consistent delimiters or repeating column patterns, and the content is prose-style rather than tabular. While officer names are visible, they are embedded in unstructured text and not in a columnar format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational data (officer names, shift times, equipment, assignments) but no identifiable personal information beyond generic role names. No emails, phones, DOB, addresses, SSNs, or other PII are present. Values in Column1 appear to be officer names but lack sufficient context to reliably map to firstName/lastName fields; they may be nicknames or role descriptors. No PII fields can be confidently mapped.

File structure

Notes: This is a free-form operational document from the Fulton Police Department. The file contains unstructured text with no consistent columnar structure. While there are repeated patterns (shift times, equipment types), these are operational codes and not personal PII fields. No identifiable personal information (names, emails, phone numbers, addresses, etc.) is present in a structured format. The document appears to be a series of shift reports and equipment logs, not a dataset containing personal identifiable information in a tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (names of officers, shift times, equipment codes, duty types). No PII fields are present — 'Curtis', 'Burlingham', etc. are officer call signs or operational aliases, not real names. Age values (30,80,64) are shift durations or age proxies. ID-like strings (7078-3084) are equipment or assignment codes. All columns are internal operational metadata and do not map to any PII field categories.

File structure

Notes: The provided data is free-form text with no consistent delimiter or structured columns. It appears to be internal operational documents from the Fulton Police Department, containing unstructured entries such as shift reports, officer names, equipment details, and timestamps. Since there is no consistent column structure, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift times, equipment codes, duty types). No identifiable PII fields present. Names appear to be officer identifiers or shift codes rather than personal names, and numeric values are internal codes or duty codes. This matches the expected content of law enforcement operational documents with no exposed personal data.

File structure

Notes: This is a free-form document containing unstructured operational logs and shift reports. No consistent column structure exists across lines; values appear to be mixed text and identifiers rather than tabular data. There are no identifiable PII fields in a structured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment, assignments) with no identifiable PII fields. Names appear to be officer identifiers or roster codes rather than personal names; numeric codes and vehicle designations are internal tracking values. No emails, phones, DOB, SSN, or address data present.

File structure

Notes: This is a free-form document with no consistent columnar structure. The sample shows unstructured operational reports with mixed content across lines (officer names, shift times, equipment IDs). There are no identifiable PII columns in a tabular format. Any personal identifiers (e.g., 'J. Sweeting') appear inline in prose and would require unstructured text processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational scheduling data (names of officers, shift times, equipment assignments, duty types) but none map to defined PII fields. Officer names appear in Column1 but these are internal personnel identifiers rather than public personal data; shift times and equipment codes are operational metadata. No emails, phones, DOBs, addresses, SSNs, or other PII categories are present.

File structure

Notes: This is an unstructured document with free-form text lines containing officer names and operational data. No consistent columnar structure exists. The content appears to be internal police shift reports with officer names and equipment listings, but lacks CSV/TSV structure. Since there are no consistent columns and the data is free-form prose, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data: officer names (non-PII in this context as personnel roster), shift times, equipment assignments, duty types. No PII fields (email, phone, DOB, SSN, etc.) are present. Values like 'Curtis', 'Burlingham' are officer names but are not personal contact info in this structured operational context. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags, company/business references.

File structure

Notes: This is a free-form operational document from the Fulton Police Department, not a delimited structured file. The data appears as prose lines with shift details, officer names, equipment types, and timestamps, but lacks consistent column structure or delimiters. It contains officer names (Hahn, Hall, R. Sweeting) and potentially sensitive operational details, but no clear PII fields in a columnar format. This should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal law enforcement operational data (shift codes, equipment, assignments) and identifiers that are NOT personal PII per exclusion rules. No email, phone, address, name, DOB, SSN, gender, or other PII fields are present. Columns 0 and 1 appear to be placeholder names or numeric codes, not actual person names. Columns with codes like 'Rifle 1', shift times, vehicle assignments, and status codes are internal operational identifiers and do not map to any PII field types.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be operational reports from the Fulton Police Department, with lines containing mixed data (officer names, OINs, equipment, timestamps, etc.) but no shared delimiter or row pattern. The sample shows free-form entries like 'SHIFT', 'OFFICER', 'J. Sweeting', 'Chernesky', 'Okun', '1600-2400', 'OIN', etc., confirming unstructured format. Since there is no consistent delimiter or repeating structure, this must be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file but contains no PII fields. All columns represent internal operational data such as officer names (which are not personal identifiers in this context), shift times, equipment types, vehicle assignments, department codes, and status flags. No emails, phone numbers, addresses, DOB, SSN, or other personal identifiers are present. The 'Curtis', 'Burlingham', etc. values appear to be officer identifiers or role names rather than personal names, and the numeric codes are internal department identifiers. All columns are marked as skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is a free-form text file containing unstructured operational reports from the Fulton Police Department. There is no consistent columnar structure across lines; each line represents different types of data (shift information, officer names, equipment details, timestamps). While there are some names visible (e.g., 'Ja. Marino', 'Levea', 'Golden'), the lack of consistent delimiter or column pattern means this must be processed as unstructured text. No PII columns can be mapped due to absence of structured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file containing law enforcement operational data from the Fulton Police Department. All columns appear to be internal operational codes, vehicle identifiers, shift schedules, and duty classifications. No PII fields are present — names like 'Curtis' are likely officer call signs or placeholder names, not actual personal names. Numeric codes (e.g., '7078-3084') are internal identifiers, not phone numbers or SSNs. Vehicle codes ('Car 1', 'Rifle 1') and duty codes ('BRVMNT', 'Sick') are non-PII operational metadata. No email addresses, phone numbers, DOBs, or other PII fields are detectable.

File structure

Notes: This is a free-form text document with no consistent columnar structure. The file appears to be a series of operational reports from the Fulton Police Department, containing prose entries rather than structured tabular data. No consistent delimiter or header pattern exists across lines.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/logistical data (names of officers, shift times, equipment types, duty codes). No PII fields are present. Names in Column1 appear to be officer names, but these are not personal identifiers in this context—they are operational roster names used internally. All other columns are shift timestamps, equipment codes, duty types, and status flags. No emails, phones, DOB, addresses, SSNs, or other PII are detectable.

File structure

Notes: This is an unstructured document containing free-form text with no consistent column structure. The file appears to be a series of daily desk reports from the Fulton Police Department, with entries that vary in format and content across rows. There are no identifiable PII columns in a structured format, and the data does not conform to a CSV or tabular structure. The content includes operational details like shifts, officer assignments, equipment, and timestamps, but lacks consistent delimiters or headers.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers (names of officers, shift codes, equipment types, assignment types) and scheduling flags — none contain personal PII like email, phone, address, or SSN. Officer names appear but are not mappable to a PII field in our taxonomy; these are operational personnel rosters, not customer/contact records. All columns are skipped per exclusion rules for internal IDs and operational metadata.

File structure

Notes: This is unstructured free-form text with no consistent delimiter or column structure. The sample shows narrative entries like 'DESK REPORT / FULTON POLICE DEPT.', timestamps, and operational codes rather than tabular data. There are no identifiable PII columns to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of personnel, shift times, equipment types, duty codes). No PII fields are present. Columns contain officer names but these are likely internal roster names rather than personal identifiers; no emails, phones, addresses, DOB, SSN, etc. are visible. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags.

File structure

Notes: The file is a free-form text document containing operational reports from the Fulton Police Department. There are no consistent columns or delimiters; instead, it appears to be a series of lines with varying structures and content, including officer names and operational details. This matches the unstructured opt-out criteria because it lacks a consistent delimiter, each line has a different shape, and there are no identifiable PII columns to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer schedules, equipment codes, shift types) with no personal identifiers. Column0 values appear to be officer names but these are operational codes (Curtis, Burlingham, etc. are not actual personnel names). Column2 values are numeric codes. Column6 values are officer identification numbers (OINs) but these are internal identifiers and should be skipped per exclusion rules. All other columns are equipment codes, shift types, or status flags. No PII fields are present.

File structure

Notes: This is a free-form document with no consistent columnar structure. The content appears to be a mix of text lines representing shift reports, officer assignments, and equipment listings from the Fulton Police Department. There are no identifiable PII columns in a structured format; any potential names appear inline in unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department, with no personal identifiable information (PII). Columns represent officer names (but these appear to be nicknames or codes rather than real names), age ranges, shift times, equipment assignments (rifles, cars), duty types, and status flags. No emails, phone numbers, addresses, DOB, SSN, or other PII fields are present. All columns map to skip categories (internal codes, equipment, timestamps, status flags).

File structure

Notes: This is a free-form document containing operational logs from the Fulton Police Department. The data shows shift reports, officer assignments, and equipment details with no consistent column structure across rows. Values appear to be free-text entries rather than structured tabular data, matching the unstructured opt-out criteria.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file containing operational records from the Fulton Police Department. All columns appear to represent internal operational data such as officer names (which are likely internal identifiers or call signs rather than personal names), shift times, equipment assignments, and duty statuses. None of the columns map to defined PII fields per the provided schema. Columns with numeric values likely represent internal codes or shift identifiers. There are no emails, phone numbers, addresses, DOBs, SSNs, or other personal identifiers present in this sample.

File structure

Notes: This is a free-form text document with no consistent column structure. The file appears to be operational logs from the Fulton Police Department containing shift reports, officer assignments, and equipment status. There are no structured PII columns in this data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, shift patterns, equipment codes, and status flags. No PII is present. Columns 0 and 1 appear to be names but the context indicates these are officer identifiers or role labels, not personal names. Columns 2 and 6 appear to be internal codes, not phone numbers or SSNs. All other columns are operational codes, vehicle designations, and status flags. No email, address, DOB, SSN, or other PII fields are present.

File structure

Notes: This is a free-form document containing operational reports from the Fulton Police Department. The data appears to be prose-style records with no consistent columnar structure or delimiter. While some lines contain what appear to be officer names (e.g., 'Wallace', 'R. Sweeting', 'Okun'), the format lacks any consistent mapping to PII fields due to its unstructured nature. The sample shows mixed content across lines without a shared delimiter or column pattern.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift times, equipment codes, assignment types). No PII fields present. Names appear to be officer surnames only without first names or other identifiers. Numeric codes are internal department identifiers, not SSNs or phone numbers. Timestamps are shift schedules, not DOBs. Equipment and assignment codes are non-PII operational data.

File structure

Notes: This is a free-form text file containing unstructured operational notes from Fulton Police Department. No consistent column structure exists across rows. The data appears to be shift reports, officer assignments, and equipment tracking, but lacks any identifiable PII fields in a structured format. Per rules, unstructured files with no consistent delimiter structure and variable row shapes should return an empty columns object.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, and duty statuses. No PII fields (names, emails, phone numbers, addresses, DOB, SSN, etc.) are present. Columns with names like 'Column1' containing values that resemble names are actually codes or placeholders, not actual personal names. The values in all columns are internal departmental codes, shift patterns, equipment identifiers, and duty types, none of which constitute personally identifiable information under the defined PII categories.

File structure

Notes: This is free-form text with no consistent columnar structure. The data appears to be operational reports from the Fulton Police Department with officer assignments, equipment, and shift details. There are no identifiable PII fields in a structured format; any names present appear to be officer names within narrative text and not in a machine-parseable columnar format. This should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department (Fulton, NY). All columns are internal operational codes, shift times, equipment assignments, and duty statuses. No PII is present. Columns like names (Curtis, Burlingham) appear to be officer nicknames or duty codes, not actual personal names. Numeric codes and vehicle identifiers are internal tracking numbers, not SSNs or usernames. All columns fall under the skip rules: internal IDs, vehicle/product data, internal flags, and operational codes.

File structure

Notes: The file appears to be free-form text documents rather than structured tabular data. The lines contain operational notes, shift information, and equipment details for the Fulton Police Department, but there is no consistent column structure or delimiter. Values appear to be mixed prose rather than columnar data. Since there is no consistent row structure and the data is free-form text, this is classified as unstructured.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal police operational data (officer schedules, equipment, assignments) with no personal identifiers. Column 0 appears to be officer surnames, but this is non-personally identifiable within this law enforcement context and not mapped to any PII field. All other columns are shift times, equipment codes, duty types, and status flags — none are PII. No emails, phones, DOB, addresses, SSNs, or usernames present.

File structure

Notes: This is an unstructured document containing free-form text records with no consistent column structure. The sample shows lines with varying content like officer names, shift times, equipment details, and timestamps, but no fixed delimiter or header pattern. The file contains embedded names and timestamps, but due to the lack of structured columns, it should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/shifts data (names of officers, duty shifts, equipment assignments, vehicle types). No PII fields (email, phone, dob, etc.) are present. Officer names appear but are not mappable to a PII field in our taxonomy (no 'officerName' field). All columns are skipped per rules (vehicle data, internal flags, timestamps, etc.).

File structure

Notes: This is unstructured text data representing operational documents from the Fulton Police Department. The content shows free-form text with no consistent delimiter structure across rows. Each line appears to be part of narrative reports with varying fields and content shapes. There are no identifiable PII fields in a structured format, and this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file with 14 columns, but none of the columns map to PII fields. Column1 appears to contain names, but these are likely officer names or personnel names which are not considered PII in this context per the exclusion rules for law enforcement operational documents. All other columns contain operational codes, vehicle assignments, shift times, and status flags that are internal departmental identifiers and not PII. No email, phone, DOB, address, SSN, or other PII fields are present.

File structure

Notes: This is unstructured free-form text with no consistent column structure. The sample consists of headerless operational logs and shift reports from the Fulton Police Department, with no repeated delimiters or columnar layout. Contains officer names but lacks any identifiable PII fields in structured columns. No mapping possible due to unstructured nature.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational document from the Fulton Police Department. Columns contain shift schedules, equipment assignments, and duty codes — no personal identifiers. Values in Column1 are likely officer names but lack supporting columns (no emails, phones, DOB, etc.). Without corroborating PII fields, we cannot reliably map Column1 to any PII type. All other columns are operational codes, vehicle types, time slots, or duty statuses. No email, phone, address, SSN, or username data is present. Therefore, no columns map to defined PII fields.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. Lines contain mixed data including officer names, shift information, and equipment details, but lack a uniform column layout. The content appears to be internal operational documents rather than structured tabular data with PII columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns represent internal operational codes, vehicle assignments, shift times, and duty statuses. There are no personal identifiers (PII) such as names, contact information, or sensitive personal data. Columns with names like 'Column1' containing values such as 'Curtis', 'Burlingham', etc., appear to be officer identifiers or codes rather than actual personal names, and the numeric and alphanumeric codes represent internal departmental designations. No PII fields are present.

File structure

Notes: The file is free-form text with no consistent column structure. It contains operational notes and shift rosters from the Fulton Police Department. There are no structured PII columns; values appear to be narrative entries rather than delimited data. No emails or phone numbers are visible in the sample.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, shift schedules, equipment codes, and role titles. No PII fields (names, emails, phone numbers, addresses, DOB, SSN, etc.) are present. Columns map to officer names (non-PII in this context as they are job titles), shift times, equipment types, vehicle assignments, and duty statuses. No sensitive personal data identified.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The sample shows prose entries like 'SHIFT', 'OFFICER', 'JA. MARINO', and operational codes rather than structured tabular data. There are no identifiable PII columns in this format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns represent internal operational codes, shift timings, equipment assignments, and duty statuses. No PII fields are present — names like 'Curtis' are likely officer call signs or duty identifiers, not personal names. Age values ('30', '80') are likely shift durations or age codes, not actual birth dates. ID-like strings (e.g., '7078-3084') are equipment or officer identification numbers, not SSNs or addresses. All columns fall under skip rules: vehicle/product data, internal IDs, timestamps, internal flags, and company/business references.

File structure

Notes: This is a free-form document with no consistent column structure. The data appears to be operational logs from the Fulton Police Department, containing unstructured text entries for shift reports, officer assignments, and equipment details. There are no consistent delimited columns, and the content varies significantly across rows. No PII columns can be mapped due to the unstructured nature of the data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for the Fulton Police Department. All columns appear to represent internal operational codes, shift times, equipment types, and duty statuses. There are no personal identifiers such as names, contact information, dates of birth, or other PII fields. The values in Column1 appear to be generic names that do not correspond to actual personnel. All columns are internal operational metadata and do not contain any PII.

File structure

Notes: This is a free-form text file containing operational documents from the Fulton Police Department. The data appears to be prose-style entries with no consistent columnar structure or delimiter. Each line contains different types of information (officer names, shift details, equipment, etc.) in an unstructured format. There are no columns to map to PII fields as the data is not in a tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/equipment data, shift codes, or internal status flags. No PII fields present. Column 0 appears to be officer names but values like 'Curtis' and 'Burlingham' are likely role placeholders or test data rather than real personnel names given the context of shift rosters and equipment logs. No emails, phones, addresses, DOB, SSN, or other PII are present.

File structure

Notes: This is a free-form text document (not a CSV/TSV). The file contains unstructured operational logs from the Fulton Police Department with no consistent column structure. While some values resemble names (e.g., 'JA. MARINO', 'SCRIBNER'), there is no consistent delimiter or header pattern across rows, and the data appears to be narrative-style shift reports rather than tabular records. Per the unstructured opt-out rules, we return an empty columns object.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational scheduling and equipment data (names of officers, shift times, vehicle assignments, duty types). No PII fields are present — officer names are internal identifiers, shift blocks and equipment codes are operational metadata, duty types are roles/statuses. No emails, phones, addresses, DOBs, SSNs, etc. are visible. All columns are skipped per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is a free-form text file containing unstructured operational reports and schedules from the Fulton Police Department. There are no consistent columnar structures; instead, it's a series of human-readable entries with varied layouts. The file contains officer names (R. Sweeting, Golden, Hogan), officer identification numbers (OIN), and vehicle assignments, but these appear inline within prose rather than as tabular data. Since there is no consistent delimiter or row structure across lines, this must be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data, vehicle assignments, shift schedules, and departmental codes. No PII fields (names, emails, addresses, etc.) are present. Columns map to internal identifiers, shift times, equipment types, and role designations — all skip per exclusion rules.

File structure

Notes: This is unstructured operational documentation from the Fulton Police Department. The file contains free-form text with no consistent columnar structure — headers appear in the first row but subsequent rows mix textual entries and operational codes across all positions. The content includes officer names (Dumas, Wallace, Okun), OINs (42, 14, 90, 10), equipment identifiers (Rifle 1, SG 3, 7042-5585), timestamps, and duty assignments. Because there is no stable delimiter or repeated row pattern, this must be processed as unstructured text. Embedded PII (names, OINs) will be extracted via streaming processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational schedule / assignment document for the Fulton Police Department, not a personal PII dataset. Columns contain shift times, equipment types, vehicle assignments, operational codes, and duty titles — no actual names, addresses, or other PII are present. Values that look like names (e.g., 'Curtis', 'Burlingham') are likely officer codes or placeholder labels, not real personal names. All columns fall under skip rules: vehicle/product data, internal flags, timestamps, operational codes, and internal IDs. No PII fields mapped.

File structure

Notes: This is a free-form text file (not CSV/TSV) with no consistent delimiter or column structure. The file appears to be a mix of prose and tabular data, with lines containing phrases like "DESK REPORT / FULTON POLICE DEPT." and fragmented operational details. Though no explicit PII like emails or phone numbers appear in the first 50 rows, unstructured files may still contain embedded PII that requires streaming extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, shift codes, equipment designations, and duty statuses. No PII is present — names appear to be placeholder or test data, and numeric values are shift identifiers or OIN fragments. No emails, phones, addresses, DOB, SSN, or other personal identifiers detected.

File structure

Notes: This is a free-form document with no consistent columnar structure. The content appears to be operational logs from the Fulton Police Department, including shift reports, officer assignments, and equipment details. There are no structured PII fields in a tabular format; instead, it contains narrative entries with officer names and operational codes. Since the data lacks a consistent delimiter and row structure, it is classified as unstructured text. No column mapping is performed.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers, vehicle codes, shift schedules, and department roles. No PII fields detected. Columns contain officer names without surnames, shift times, equipment codes (Rifle, Car), department codes (BRVMNT, NBA), rank titles, and status flags. No emails, phone numbers, addresses, DOBs, SSNs, or other PII categories present.

File structure

Notes: This is free-form text with no consistent delimiter or column structure. The file appears to be a series of operational reports from the Fulton Police Department, containing unstructured entries such as shift details, officer assignments, equipment, and timestamps. There are no consistent columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but all columns contain internal operational data (names of officers, shift times, equipment codes, duty assignments) that do not map to any defined PII fields. Officer names appear in Column1 but these are employee identifiers rather than personal identifiers for individuals in a civilian context. All other columns are shift codes, equipment types, duty types, and status flags — none qualify as email, phone, address, DOB, SSN, etc. No PII fields are present.

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows prose entries like officer names and shift details, not a CSV/TSV with defined columns. Contains officer names (J. Sweeting) which are PII, so unstructured extraction will handle it.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational schedule/roster file with officer names, shift times, equipment assignments, and duty statuses. No actual PII fields are present. Names appear to be placeholder names or pseudonyms ('Curtis', 'Burlingham', etc.), and all other columns represent shift schedules, equipment codes, duty types, and administrative codes — none map to email, phone, DOB, SSN, or other PII categories. The file is purely operational and contains no personal contact or identifying data beyond generic role assignments.

File structure

Notes: This is free-form text with no consistent column structure. The data appears to be operational documents from the Fulton Police Department containing unstructured entries like officer names, shift times, and equipment details. There are no consistent delimiters or column patterns across the rows, and the content is prose-like with embedded names and operational details rather than structured tabular data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains no PII. All columns represent internal law enforcement operational data: officer names (non-PII internal identifiers), shift codes, equipment designations, vehicle assignments, department codes, and status flags. No emails, phone numbers, addresses, DOBs, SSNs, or other PII fields are present.

File structure

Notes: This is a free-form text document with no consistent columnar structure. It contains unstructured operational notes from the Fulton Police Department, including officer names (e.g., 'Sheldon', 'Okun', 'Wallace') and internal codes, but lacks a defined delimiter or header row. The content appears to be narrative reports rather than tabular data, so no column mapping can be performed.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for the Fulton Police Department. All columns appear to be internal operational codes, vehicle identifiers, shift times, and duty statuses. No personal identifiable information (PII) fields such as names, contact details, or sensitive identifiers are present. Columns with names like 'Column1' containing values that resemble names are actually operational codes or placeholders, not actual personal names. All columns map to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is free-form text with no consistent columnar structure. The sample shows narrative entries about police shifts and equipment, not tabular data. While names like 'J. Sweeting' appear, they are embedded in prose lines without shared delimiters. This qualifies as unstructured content per rules.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational data (names of officers, shift times, equipment codes, duty types). No PII fields (email, phone, dob, etc.) are present. Officer names are internal identifiers for shift rosters, not public person names. All columns map to skip categories: internal IDs, vehicle/product data, timestamps/dates, internal flags, etc.

File structure

Notes: This is a free-form text document containing operational reports and shift rosters from the Fulton Police Department. The data shows no consistent columnar structure — each line contains different report elements (officer names, shift times, equipment status, etc.) without a shared delimiter or fixed format. The content includes officer names (e.g., 'Hall', 'R. Sweeting', 'Murphy') and shift details, but these are embedded in prose rather than structured fields. This meets the unstructured criteria: no consistent delimiter, variable line shapes, and embedded PII in free text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent operational scheduling and equipment data for Fulton Police Department personnel. No PII fields present — names are officer nicknames or roles, numbers are shift identifiers or OIN fragments, vehicle/equipment codes are internal operational data, and status codes (Sick, Vac, etc.) are non-personal status flags. Per exclusion rules, these are skipped.

File structure

Notes: This is a free-form text file containing operational documents from the Fulton Police Department. The content shows unstructured prose with no consistent columnar pattern — lines contain varying data points like officer names, shift times, equipment status, and operational codes. While names like 'Wallace', 'Levea', and 'Brown' appear, they are embedded in narrative text rather than structured columns. Per the unstructured opt-out rules (a) no consistent delimiter, (b) lines have wildly different shapes, and (c) contains human-readable text with officer names, this file must be processed as unstructured with embedded PII extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, duty statuses, and organizational titles. There are no identifiable personal fields (names, emails, phone numbers, addresses, DOB, SSN, etc.). Column 0 contains names but these appear to be officer nicknames or duty identifiers rather than personal full names, and are not combined with other PII. No columns map to PII fields.

File structure

Notes: The file is free-form text with no consistent delimiter structure. It contains operational reports from Fulton Police Department, including officer names (e.g., 'Ja. Marino', 'J. Sweeting', 'Levea'), shift details, and equipment information. While names appear, the lack of structured columns means we must treat it as unstructured text for processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file but all columns represent internal operational data (officer names, shift times, equipment codes, assignment types). Column0 contains officer names but these are employee identifiers rather than personal PII — law enforcement personnel names are not generally considered public PII in this context unless released publicly as part of an official roster. All other columns are shift times, equipment codes, assignment categories, and status flags. No email, phone, dob, address, ssn, password, or other personal PII fields are present. Therefore no PII columns to map.

File structure

Notes: This file is unstructured operational documents from Fulton Police Department. It contains free-form text with no consistent column structure across rows. Sample shows shift reports, officer names, OINs (officer identification numbers), equipment data, and timestamps, but these appear as free-text entries rather than tabular data. The content includes officer names (Hahn, Scribner, Murphy) and OINs (70, 66, 58) embedded in the text, but there are no defined columns to map. This requires unstructured text processing for PII extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (names of officers, shift times, equipment codes, assignment types). No PII fields (email, phone, dob, etc.) are present. Officer names are internal personnel identifiers, not public PII per law enforcement context. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags.

File structure

Notes: This is an unstructured document containing free-form text with no consistent delimiter or column structure. The data appears to be operational reports from the Fulton Police Department, with entries describing shifts, officer assignments, equipment, and other operational details. There are no identifiable PII columns in a structured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains only operational/scheduling data for law enforcement personnel. No PII fields are present — all columns are internal codes, shift times, equipment types, role titles, and status flags. No names, IDs, contact info, or other personal data appear in the sample.

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows unstructured operational notes from Fulton Police Department with officer assignments, shift times, and equipment listings, not tabular PII data. No columns to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment data for the Fulton Police Department. All columns appear to represent internal operational codes, vehicle assignments, shift times, and duty statuses. No personal identifiable information (PII) such as names, contact details, or sensitive personal data is present. Columns with names like 'Column1' containing what appear to be surnames are actually officer designations or roster labels, not actual personal names. All data fields are internal departmental codes, timestamps, or operational statuses that do not qualify as PII under the defined categories.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The sample shows operational notes and shift reports from the Fulton Police Department, with values varying per line and no shared delimiter. Contains officer names (Algarin, Hutchinson, Scribner) and operational details, but lacks structured columns for PII mapping.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (names of officers, shift times, equipment types, duty codes) but none contain actual PII fields. Column0 contains officer names but these are likely internal codes/aliases rather than real names, and are not mapped to firstName/lastName per policy. All other columns are vehicle/product data, timestamps, internal flags, or company/business references that must be skipped.

File structure

Notes: The file is a free-form text document containing unstructured operational logs from the Fulton Police Department. It lacks consistent columnar structure across rows — each line contains different categories of data (shift assignments, officer names, equipment, timestamps). Values appear as plain text with no shared delimiter or fixed field positions. Though officer names like "Hall" and "R. Sweeting" appear, they are embedded in free-text lines without column mappings. This meets unstructured criteria: no consistent delimiter, variable line shapes, and embedded personal names.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department officers. All columns represent internal operational codes, shift times, equipment types, and duty classifications. No personal identifiable information (PII) is present. Columns with names like 'Column1' containing what appear to be names are actually officer identifiers or duty codes, not actual personal names. All values are internal departmental codes, timestamps, or equipment designations. Per exclusion rules, no columns map to PII fields.

File structure

Notes: This is a free-form document containing unstructured operational logs from the Fulton Police Department. The content includes desk reports, shift details, officer assignments, equipment lists (long guns, cameras, tasers), vehicle assignments, and timestamps. There is no consistent columnar structure or delimiter; instead, it appears to be a narrative or tabular text format with mixed data types and varying line formats. While it contains sensitive operational data, it does not present structured PII fields in a columnar format. The values shown are operational codes, equipment serial numbers, timestamps, and shift details rather than personal identifiable information such as names, addresses, emails, or phone numbers in a structured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment assignments, duty types). No PII fields are present. Values like 'Curtis' are officer names used in operational contexts, not personal identifiers requiring PII classification per the exclusion rules for internal law enforcement documents. No emails, phones, addresses, DOB, SSN, etc. are present.

File structure

Notes: This is a free-form text document containing operational notes from the Fulton Police Department. The content includes desk reports, shift details, officer assignments, equipment listings, and other internal scheduling data. There are no consistent column structures or delimiters — each line contains unstructured prose with officer names, operational codes, and timestamps. While officer names appear (e.g., "Algarin", "Hutchinson", "Scribner"), they are embedded in narrative text rather than in a tabular format. Per rules, unstructured files with no consistent delimiter and varying line shapes must be processed as unstructured, even if PII-like strings exist.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department personnel. All columns represent internal operational codes, shift times, equipment assignments, and duty statuses. No PII fields (names, emails, addresses, etc.) are present. Columns with officer names (e.g., "Curtis", "Burlingham") are likely officer identifiers or placeholders, not personal names. Values like "7078-3084" appear to be internal reference codes, not phone numbers or SSNs. No email addresses, phone numbers, dates of birth, or other PII are detected.

File structure

Notes: This is an unstructured document containing free-form text. The data appears to be internal operational documents from the Fulton Police Department, with no consistent columnar structure. It contains entries like officer names (e.g., 'Hall', 'R. Sweeting', 'Golden'), officer identification numbers (OINs), equipment assignments, and shift information, but these are embedded in prose rather than structured columns. Therefore, it should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal police operational data (names of officers, shift times, equipment codes, duty statuses). None of the columns map to defined PII fields — officer names are internal personnel identifiers, shift times are work schedules, equipment codes are non-PII inventory tags, and duty statuses are operational flags. No emails, phones, addresses, DOB, SSN, or other personal identifiers are present.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The data appears to be operational logs from the Fulton Police Department, containing unstructured entries like shift reports, officer assignments, and equipment details. There are no identifiable PII columns in a structured format; instead, the data is prose-style entries. Per the unstructured opt-out rule, we return an empty columns object.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but ALL columns contain operational/tracking data (names of officers, shift times, equipment codes, duty types). No columns contain identifiable PII such as email, phone, DOB, SSN, etc. Officer names are internal identifiers for scheduling and NOT personal names in a PII sense per the exclusion rules for internal IDs/flags. All columns map to skip categories (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is a free-form text file containing unstructured operational documents from the Fulton Police Department. The content appears to be daily desk reports, shift rosters, and officer assignments, with no consistent column structure or delimiter. Sample lines show free-form text with no repeating column patterns, and contain officer names and operational details but not in a tabular format. Per the unstructured opt-out rules, no column mapping is performed.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational / scheduling data (officer names, shift times, equipment types, duty codes). Column0 contains officer names, but these are employee identifiers for law enforcement personnel, not general public PII. Per breach context (Fulton Police Department internal documents), names refer to officers — these are NOT mappable to firstName/lastName fields because they are internal personnel records, not public civilian data. No columns map to any defined PII fields (email, phone, dob, etc.).

File structure

Notes: This is a free-form document with no consistent column structure. The data appears to be internal operational reports from the Fulton Police Department, containing unstructured text entries such as officer names, shift information, equipment details, and timestamps. There are no clearly defined columns that map to PII fields. Given the unstructured nature and the presence of free-form text, this should be processed as unstructured data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment types, duty codes). No PII fields are present. Column0 contains officer names but these are likely internal identifiers or nicknames rather than personal names, and the context confirms this is law enforcement scheduling data with no exposed personal contact information. All other columns are shift times, equipment codes, duty types, and status flags.

File structure

Notes: This is a free-form text file with no consistent delimiter or row structure. The file contains operational documents from the Fulton Police Department, including shift reports, officer assignments, equipment lists, and timestamps. No structured PII columns exist, but it may contain embedded names or identifiers in prose. The format is unstructured and should be processed accordingly.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment codes, assignment types). No PII fields are present. Column0 contains officer names, but these are internal staff identifiers rather than public personal data. All other columns are shift schedules, equipment codes, and assignment types — none map to PII categories. No emails, phones, addresses, DOB, SSN, etc. present.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The content appears to be operational reports from the Fulton Police Department with no structured PII fields in columnar format. Values appear to be mixed text with officer names and operational codes rather than tabular data. Since there is no consistent column structure and the data is prose-like, it should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal law enforcement operational data (officer schedules, assignments, equipment). Column1 contains officer names, but these are not personal PII as they are internal personnel identifiers within the Fulton Police Department context. No true PII fields (email, phone, address, DOB, SSN) are present. Vehicle IDs, shift times, and operational codes are all internal operational data, not personally identifiable information in the standard sense.

File structure

Notes: The file is free-form text with no consistent delimiter or column structure. It appears to be operational logs from Fulton Police Department with mixed content across lines (shift reports, officer names, equipment details, timestamps). There are no structured columns to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/tactical law enforcement data (officer names, duty schedules, vehicle assignments, equipment, shift codes). No PII fields are present — names appear to be officer identifiers or shift codes, not personal names. Numeric values are shift times or equipment codes. No emails, phones, DOBs, addresses, SSNs, or other PII detected.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The content appears to be operational logs from the Fulton Police Department, containing unstructured entries like shift reports, officer assignments, and equipment details. There are no identifiable PII columns in a structured format, but the text may contain embedded names and operational codes that require unstructured processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns represent internal operational codes, vehicle assignments, shift times, equipment types, and duty statuses. No PII fields (names, emails, addresses, etc.) are present. Columns like 'Column1' contain officer last names, but these are not personal identifiers in a PII sense within this operational context — they are internal roster codes. All other columns are shift codes, equipment designations, or status flags. No mappable PII columns exist.

File structure

Notes: This is free-form text with no consistent column structure. The sample shows unstructured operational reports with officer names, shift times, equipment, and OINs, but there are no repeating columns or delimiters. It matches the unstructured opt-out criteria: (a) no consistent delimiter, (b) lines have wildly different shapes, (c) contains officer names which could be treated as PII but require streaming extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational schedules and equipment assignments for law enforcement personnel. All columns represent internal operational data (names of officers, shift times, equipment codes, duty types). No personally identifiable information (PII) such as email, phone, DOB, address, SSN, etc. is present. Officer names are internal identifiers for personnel and not considered PII in this operational context. All columns map to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is free-form text with no consistent delimiter or column structure. The data appears to be operational documents from the Fulton Police Department, containing unstructured entries such as officer names, shift details, equipment, and timestamps. There are no structured columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal law enforcement operational data (names of officers, shift times, equipment assignments, duty types). No PII fields (email, phone, dob, etc.) are present. Officer names are internal identifiers for scheduling, not public PII in this context. All columns map to skip per rules: vehicle/product data, internal flags, timestamps, and internal IDs.

File structure

Notes: This is an unstructured document containing free-form text records of Fulton Police Department operational logs. The sample shows inconsistent formatting with no defined column structure — headers are sparse or absent, and rows contain mixed operational data (officer names, shift times, equipment, OINs). This matches the breach description of leaked internal operational documents (desk reports, shift rosters, equipment assignments). The file must be processed via unstructured text parsing to extract any embedded PII (e.g., officer names like 'J. Sweeting').

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational roster document with officer names and internal identifiers, but the names are not personal employee names (they are shift officer identifiers or aliases). No PII fields are present: Column1 contains shift officer identifiers (not personal names), Column2 is likely age or years of service, Column3 and Column6 are internal officer identification numbers (OINs), and the rest are shift details, equipment assignments, and operational codes. No emails, phones, DOBs, addresses, SSNs, or other PII are present.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be operational documents from the Fulton Police Department, containing shift reports, officer assignments, and equipment details. There are no structured columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment data for the Fulton Police Department. No PII fields are present. Columns contain officer names (Curtis, Burlingham, etc.), shift times, equipment codes (Rifle, Car), duty types (BRVMNT, MH TRANSPORT), and titles (Deputy Chief, Lieutenant). Names appear to be officer surnames or call signs, not personal identifiers. All columns fall under internal operational data and are not mappable to PII fields.

File structure

Notes: This is unstructured operational documentation from the Fulton Police Department. The data appears to be free-form text with no consistent columnar structure. Columns listed appear to be placeholders or labels within the document rather than actual data columns. There are no identifiable PII fields in a structured format; any personal identifiers (like names) appear embedded within narrative text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational data (officer names, shift times, equipment codes, duty types). No identifiable PII fields (email, phone, DOB, SSN, etc.) are present. Names in Column1 appear to be officer names, but these are not mappable to firstName/lastName fields because they are internal identifiers for personnel and not personal contact information. All other columns contain shift times, equipment codes, duty types, and status flags which are operational metadata, not PII. Therefore, no PII columns to map.

File structure

Notes: This is a free-form text file containing internal operational documents from the Fulton Police Department. The data appears to be unstructured with no consistent delimiter or column structure. The sample shows lines with varying content and no shared format, indicating it is not a structured CSV or tabular format. Given the unstructured nature and lack of consistent columns, it is classified as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift times, equipment codes, duty statuses). No PII fields are present — names appear to be officer identifiers (e.g., 'Curtis', 'Burlingham') not personal names, and numeric codes are internal tracking numbers. Values in columns 0-1 and 2-6 are non-PII operational codes, vehicle assignments, and duty statuses. No emails, phones, DOBs, or addresses detected.

File structure

Notes: The file appears to be free-form text with no consistent delimiter structure. The content includes operational reports, shift details, and equipment listings from the Fulton Police Department. There are no structured columns containing PII fields like names, emails, or phone numbers. The values are operational codes, timestamps, and equipment identifiers rather than personal data. While some entries contain what might appear as names (e.g., 'Hutchinson', 'Wallace'), these are likely officer identifiers or report codes rather than actual personal names in a PII context. No email or phone numbers are visible in the sample.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be operational/internal data (names of officers, shift times, equipment codes, duty types). No PII fields (email, phone, DOB, SSN, etc.) are present. Values in Column1 appear to be officer names, but these are not mappable to firstName/lastName fields per exclusion rules for law enforcement operational documents. All columns are skipped per policy for internal law enforcement records.

File structure

Notes: This is a free-form text file containing operational documents from the Fulton Police Department. There are no consistent columns or delimiters; instead, it contains prose-style entries with officer names, shift information, and equipment details. The structure varies per line and does not conform to a tabular format, thus classified as unstructured.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational document from Fulton Police Department containing shift rosters, equipment assignments, and officer identification numbers. Columns contain shift times, weapon assignments, vehicle assignments, duty types, and status codes. No PII fields are present — names are likely officer last names without first names, and numbers are operational codes or shift IDs. All columns map to skip categories (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is a free-form text file with no consistent column structure. The content appears to be operational documents from the Fulton Police Department, including shift reports, officer assignments, and equipment listings. There are no identifiable PII columns in a structured format; any potential PII would need to be extracted from free-text content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains no PII fields. All columns represent internal operational data such as officer names (non-PII internal identifiers), shift times, equipment types, vehicle assignments, department codes, and status flags. Names like 'Curtis' or 'Burlingham' appear to be officer identifiers rather than personal names, and all other columns are non-personal operational codes. No emails, phone numbers, addresses, DOBs, SSNs, or other PII are present.

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows unstructured operational notes from Fulton Police Department shift reports. No column mapping is possible; any PII would need to be extracted from free text via streaming processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment designations, and role titles. No personally identifiable information (PII) such as names, email addresses, phone numbers, dates of birth, or social security numbers is present. All columns are flagged as skip per the exclusion rules (vehicle/product data, internal IDs, internal flags, and company/business references).

File structure

Notes: This is a free-form document with no consistent delimiter structure. The file appears to be internal operational documents from the Fulton Police Department containing shift reports, officer assignments, equipment data, and other law enforcement operational details. There are no structured columns containing PII fields like email, phone, or address. The content is prose-style with embedded names and codes rather than tabular data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains internal operational documents from the Fulton Police Department. All columns appear to be internal identifiers, shift codes, equipment types, and status flags. No PII fields (email, phone, name, dob, etc.) are present. Columns 0 and 1 appear to be names and ages but are internal officer identifiers or codes rather than actual personal data. All other columns are codes for shifts, equipment, departments, and statuses.

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. It contains operational documents from the Fulton Police Department, including shift rosters, officer assignments, and equipment details. There are no clearly defined columns with PII fields; instead, the data is presented in a narrative format with mixed content across lines. Since there is no consistent delimiter or structured format, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment codes, duty types). No PII fields (email, phone, dob, etc.) are present. Columns contain officer names but these are not mapped as PII fields because the context indicates these are internal operational documents where names are part of shift rosters and not exposed as personal identifiers for privacy breach purposes. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags, etc.

File structure

Notes: This is a free-form text document containing operational logs and shift reports from Fulton Police Department. The file shows no consistent column structure — lines are variable-length prose entries describing shifts, officer assignments, equipment status, and beats. No identifiable PII fields (names, emails, phones, etc.) are visible in the first 50 rows beyond officer names which appear in plain text but cannot be mapped to structured PII fields due to the unstructured format. All content is operational logs, not contact records. The unstructured format requires a streaming PII extractor for any embedded emails/phones, but none are present in the sample.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, and duty statuses. No personal identifiable information (PII) is present. Columns such as names appear to be officer identifiers or nicknames rather than actual personal names, and numeric codes represent operational identifiers, not SSNs, phone numbers, or other PII fields. Therefore, no columns map to PII fields.

File structure

Notes: This is a free-form text file containing unstructured operational documents from the Fulton Police Department. There are no consistent columns or delimiters across the rows, and the data appears to be narrative reports rather than structured records with PII fields. The content includes shift reports, officer assignments, and equipment details, but does not contain any identifiable PII fields in a structured format. No column mapping is possible as there is no consistent structure.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns appear to represent internal operational codes, shift times, equipment assignments, and duty statuses. No PII fields are present — all columns are internal identifiers, vehicle codes, shift schedules, or duty codes. Names in Column1 appear to be generic placeholder names or test data, not actual personal names. No emails, phone numbers, addresses, DOBs, or SSNs are visible.

File structure

Notes: This is unstructured free-form text with no consistent column structure. The data appears to be daily desk reports from the Fulton Police Department, containing officer assignments, equipment information, and operational details. There are no identifiable PII columns in a structured format; any potential PII would need to be extracted from free-text content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be operational/internal codes (names appear to be officer identifiers, shift times, equipment codes, duty statuses). No PII fields detected. Values like 'Curtis', 'Burlingham', etc., are likely officer identifiers or shift codes rather than personal names. The data reflects internal police department scheduling and assignment records without personal identifiable information.

File structure

Notes: This is unstructured operational documentation from Fulton Police Department. The file contains free-form text lines with no consistent column structure or delimiter. It includes officer names (e.g., 'J. Sweeting'), operational codes (e.g., 'Rifle 6'), timestamps, and shift information, but lacks a tabular format. Since there is no consistent delimiter or repeating column pattern, this is correctly classified as unstructured text. No column mapping is possible.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data: officer names (non-PII in law enforcement context), shift times, equipment codes, vehicle assignments, department units, rank titles, and status flags. No PII fields (email, phone, dob, ssn, etc.) are present. Values like 'Curtis' are officer names used internally, not personal identifiers for privacy purposes in this context.

File structure

Notes: The provided data is free-form text with no consistent columnar structure. The content appears to be operational documents from the Fulton Police Department, with lines containing officer names, shift information, equipment details, and timestamps. There are no identifiable PII columns in a structured format; any personal information is embedded within prose lines. This requires unstructured processing to extract any potential emails or phone numbers from the free-text content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be operational scheduling data for law enforcement (names, shift times, equipment, assignments). While column 0 contains names that could be considered PII, these are likely officer names used in an official capacity within a law enforcement agency. Per policy, names of public officials in operational contexts are treated as non-PII for breach impact analysis unless explicitly personal contact details. No email, phone, address, SSN, DOB, or other PII fields are present.

File structure

Notes: This is an unstructured document containing free-form text with no consistent delimiter or column structure. The file appears to be a series of daily desk reports from the Fulton Police Department, with entries that do not follow a tabular format. There are no identifiable PII columns to map as the data is not structured.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file but contains NO PII. Columns describe law enforcement operational data: officer names appear to be nicknames or generic values ('Curtis', 'Burlingham'), IDs are internal codes (e.g., '7078-3084'), shift times, equipment types (Rifle, Car), department units, and status flags. No emails, phones, DOB, SSN, addresses, or other PII fields are present. All columns map to skip categories (internal IDs, vehicle/product data, timestamps, flags).

File structure

Notes: This is a free-form text file with no consistent column structure. It contains unstructured operational reports from the Fulton Police Department, with no identifiable PII columns in a tabular format. Values appear to be shift details, officer names, equipment, and timestamps embedded in prose. Since there is no consistent delimiter and lines vary in structure, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains no PII. Columns represent internal operational data: officer names (non-PII in this context as they are public officials), age ranges, shift schedules, equipment assignments, vehicle assignments, department codes, and status flags. No emails, phone numbers, addresses, SSNs, or other personally identifiable information are present.

File structure

Notes: This is a free-form text file with no consistent column structure. The content appears to be operational reports from the Fulton Police Department, with lines containing officer assignments, equipment details, and shift information. There are no identifiable PII columns in a structured format, but the unstructured content may contain embedded names or other PII that would need to be extracted via streaming processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers, vehicle assignments, shift codes, and department roles. No PII fields detected. Values are codes, shift times, vehicle types, and role titles, not personal names, addresses, or contact information.

File structure

Notes: This is an unstructured document with free-form text lines. The data appears to be shift reports and operational logs from the Fulton Police Department. There are no consistent columns or delimiters, and the content consists of prose entries rather than structured tabular data. While there may be embedded names or operational codes, the format does not allow for column mapping.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but all columns represent internal operational data (officer names, shift times, equipment assignments, duty types). No PII fields are present. Column0 contains officer names, but these are internal officer identifiers used in scheduling, not personal names for public PII purposes. All other columns are shift schedules, equipment codes, duty types, and status flags. None map to the defined PII fields (email, phone, DOB, etc.).

File structure

Notes: This is unstructured operational documentation from Fulton Police Department. The file contains free-form text entries with no consistent columnar structure. Columns appear to be placeholders or empty, and the data consists of narrative shift reports, officer assignments, and equipment listings rather than structured PII fields. No consistent delimiter or header structure exists across rows.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/shift data (names of officers, shift times, equipment types, duty codes). No PII fields present: officer names are internal personnel identifiers, not public personal names; numeric codes are internal operational identifiers, not SSNs or phone numbers; vehicle/equipment codes are non-personal. No emails, addresses, DOBs, or other PII appear in any column.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The file contains operational documents from the Fulton Police Department, including shift reports, officer assignments, and equipment details. There are no structured columns containing PII fields; the data is presented as prose entries with no column headers or consistent formatting.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent operational scheduling and equipment data for law enforcement personnel. No PII fields (names, addresses, DOB, etc.) are present. Values such as names (Curtis, Burlingham) are likely officer identifiers or duty station names, not personal names. All columns are mapped to skip per exclusion rules (vehicle/product data, internal flags, timestamps, etc.).

File structure

Notes: This is free-form text with no consistent column structure. The file contains unstructured operational reports from the Fulton Police Department, including officer names, shift details, and equipment assignments. There are no delimited columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational scheduling data (names of officers, shift times, equipment assignments, duty types). No PII fields are present. Column0 appears to be officer surnames, but these are not personal identifiers in this context — they are operational roster names used internally by the Fulton Police Department. All other columns are shift times, equipment codes, duty types, and status flags. No emails, phones, addresses, DOB, SSN, or other PII are present.

File structure

Notes: This is an unstructured document (prose-style operational log) with no consistent columnar format. The sample shows free-form text lines like 'OFFICER Wallace' and 'Rifle 5', not a delimited table. While it contains officer names, they appear embedded in narrative text rather than as structured columns, so it must be processed as unstructured. The breach context confirms this is internal operational documents, not a CSV.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains no PII fields. All columns represent internal operational data (names are likely officer identifiers, not personal names), shift times, equipment codes, vehicle assignments, departmental codes, and status flags. No emails, phone numbers, addresses, DOB, SSN, or other PII appear. Columns with human-like names (Curtis, Burlingham, etc.) are internal officer codes or role designations, not actual personal names. All columns are mapped to skip per exclusion rules (company/business references, internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is an unstructured document containing free-form text with no consistent columnar structure. The data appears to be daily shift reports from the Fulton Police Department, with mixed content across lines including officer names, equipment, and timestamps. There are no delimited columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational data (officer names, shift codes, equipment types, duty assignments). No PII fields detected: Column1 values appear to be officer identifiers or nicknames, not actual first names. Numeric values in Column2 could be age or badge numbers but are not directly mappable to PII fields. Other columns contain shift times, equipment codes, vehicle assignments, department codes, and status flags — all internal operational metadata with no personal identifiers. No emails, phones, addresses, DOB, SSN, or other PII categories present.

File structure

Notes: The file appears to be free-form text with no consistent column structure. It contains operational notes and shift rosters from the Fulton Police Department. The data is not in a tabular format with delimited columns, and instead consists of free-text entries describing shifts, officer assignments, equipment, and other operational details. No PII fields can be mapped as there are no structured columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment assignments, duty types). No PII fields present. Names appear to be officer first names only (no surnames), shift times are time ranges, equipment codes and duty types are non-PII operational codes. No emails, phones, addresses, DOB, SSN, gender, etc. present.

File structure

Notes: This is a free-form document containing unstructured operational reports from the Fulton Police Department. The content consists of prose entries with no consistent columnar structure. While it contains officer names (e.g., 'Jarrett Marino') and operational codes, these appear as part of unstructured text rather than in a tabular format. The file lacks consistent delimiters, row structure, and header rows required for CSV mapping. It should be processed as unstructured text for any embedded PII extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but none of the columns map to PII fields. Columns contain operational data such as officer names (which are not personal identifiers in this context), shift times, equipment codes, vehicle assignments, and duty statuses. No email addresses, phone numbers, dates of birth, SSNs, or other PII are present. The officer names are part of internal scheduling and do not constitute personal identifiers for privacy purposes in this operational context.

File structure

Notes: This is a free-form text document (not a delimited CSV). The content shows unstructured operational logs with officer names, shift details, and equipment listings. There are no consistent columns — each line is a free-form note or label. While some lines contain officer names (Pappa, Algarin, Murphy), the lack of any consistent delimiter or repeating structure across all rows means this must be processed as unstructured text. The notes field contains names that could be extracted later by a streaming name extractor, but column mapping is impossible due to the absence of a tabular structure.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns represent internal operational identifiers, shift codes, equipment types, and status flags. No personal identifiable information (PII) is present — names appear to be officer identifiers or shift codes, and numeric values are shift timestamps or internal codes. No emails, phones, DOBs, addresses, SSNs, or other PII fields are detectable. All columns are skipped per exclusion rules (internal IDs, vehicle/product data, timestamps, flags).

File structure

Notes: This is a free-form text file containing operational documents from the Fulton Police Department. The data does not follow a consistent columnar structure with delimiters. Instead, it appears to be a series of free-text entries describing shift reports, officer assignments, equipment, and other operational details. There are no identifiable PII fields in a structured format; any potential PII would need to be extracted from the unstructured text content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file with operational data from the Fulton Police Department. Columns contain officer names, shift times, equipment assignments, duty types, and status codes. No PII fields (email, phone, DOB, SSN, etc.) are present. All columns either represent internal identifiers, equipment codes, duty classifications, or status flags. Therefore, no columns map to PII fields.

File structure

Notes: This is unstructured free-form text with no consistent column structure. The content appears to be shift reports and operational documents from the Fulton Police Department, containing mixed data formats and no clear tabular structure. The sample shows free-form entries like 'SHIFT', 'OFFICER', 'LEVEA', 'GOLDEN', etc., with no consistent delimiter or column pattern across rows.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal police scheduling and equipment data (names of officers, shift times, vehicle assignments, duty types). No PII fields are present: officer names are internal staff identifiers, not public person names; numeric codes are operational identifiers (OINs, shift codes); vehicle/equipment designations are non-identifiable operational data. All columns are skipped per exclusion rules for internal IDs and operational metadata.

File structure

Notes: This is free-form text with no consistent delimiter structure. The data appears to be operational logs from the Fulton Police Department, containing unstructured entries like officer names, shift details, and equipment. No structured PII columns exist; the data is prose-like with no predictable column mapping.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer schedules, equipment assignments, shift codes). No PII fields are present — names are likely officer identifiers, not personal names, and numeric codes are internal tracking numbers. Values like 'Curtis' appear to be officer codes rather than personal first names based on breach context (Fulton Police operational documents).

File structure

Notes: This is unstructured operational documentation from Fulton Police Department. No consistent column structure exists across rows — headers are sparse, rows contain mixed text (shift assignments, equipment codes, officer identifiers). No PII fields are present in this structured tabular format. All content is free-form operational documentation with no reusable PII columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an internal operational document from the Fulton Police Department. Columns contain shift rosters, officer assignments, equipment assignments, and status codes. There are no identifiable personal fields (no names, addresses, DOBs, SSNs, emails, or phone numbers). All columns represent internal police department codes, vehicle assignments, time slots, and status flags. No PII is present.

File structure

Notes: This file is free-form text with no consistent delimiter structure. The content appears to be operational documents from the Fulton Police Department, including shift reports, officer assignments, and equipment details. There are no structured columns containing PII fields; instead, the data is presented in a narrative format. The presence of unstructured text patterns and lack of consistent column alignment across rows confirms this is unstructured data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal law enforcement operational data (officer names, shift times, equipment, assignments). No PII fields are present — names are likely officer identifiers rather than personal names, and numeric values are internal codes, shift times, or equipment designations. All columns map to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is an unstructured document containing free-form text with no consistent columnar structure. The content appears to be internal operational documents from the Fulton Police Department with no identifiable PII columns in a structured format. While there are some values that might resemble identifiers (OIN numbers, dates), they are embedded within free-text lines and do not follow a consistent columnar pattern across rows. Therefore, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for law enforcement personnel. Columns contain officer identification codes, shift times, equipment types, and status flags. No personal identifiable information (PII) fields are present. All columns map to internal operational data or skip categories (vehicle data, internal flags, timestamps, company/business references).

File structure

Notes: This is an unstructured document containing free-form text lines with no consistent delimiter or column structure. The content appears to be operational logs and shift reports from the Fulton Police Department, with values varying per line and no repeatable tabular format. While it contains officer names (like "Dumas", "Wallace", "Okun"), these are embedded within free-text lines rather than structured columns, triggering the unstructured opt-out rule. No column mapping is possible.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers (names of officers, shift codes, vehicle assignments, duty types). No PII fields detected. Columns contain shift patterns, equipment assignments, and operational codes — none map to email, phone, DOB, etc. Officer names are present but are internal staff identifiers, not public PII per breach context. All columns are skipped per exclusion rules for internal IDs and operational data.

File structure

Notes: This is unstructured operational documentation from the Fulton Police Department. The file contains free-form text with no consistent column structure or delimiter. While it includes officer names and shift details, these appear as prose rather than structured tabular data. Per rules, unstructured files with no shared delimiter across lines are handled by a streaming extractor for embedded PII, not column mapping.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains only operational and scheduling data for Fulton Police Department personnel. No PII fields are present — all columns represent shift assignments, equipment, duty types, and internal codes. Columns 0-13 contain names of personnel, but these appear to be officer identifiers/codes rather than personal names, and column 1 contains numeric age-like values that do not map to any PII field. No emails, phones, addresses, DOB, SSN, or other personal identifiers are present.

File structure

Notes: This is a free-form text document containing operational notes from the Fulton Police Department. The file lacks consistent column structure or delimiters, with each line containing unstructured prose or mixed data. Despite the presence of potentially sensitive operational information, there are no identifiable PII fields (emails, phone numbers, names, addresses, etc.) in the provided sample. The content appears to be shift reports, officer assignments, and equipment logs rather than personal identifiable information.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational scheduling document for the Fulton Police Department. All columns contain internal operational codes, shift times, equipment identifiers, and duty statuses. No PII fields (names, emails, addresses, etc.) are present. Values like 'Curtis' appear to be officer identifiers or shift codes, not personal names, based on the context of police scheduling and equipment logs. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags, and non-PII status codes.

File structure

Notes: This is a free-form operational document from Fulton Police Department. The sample lines show shift reports, officer assignments, and equipment details with no consistent structured columns — it's a narrative-style text file. While it contains officer names and identifiers (OINs), these appear as part of prose rather than tabular data. The format does not meet structured CSV/TSV criteria and should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment types, duty codes). No PII fields are present. Columns contain officer names but these are likely officer identifiers rather than personal names (no first/last split, no suffixes, no context suggesting personal use). All other columns are shift codes, equipment types, duty types, and status flags — none map to PII categories. No emails, phones, DOB, addresses, SSN, gender, or usernames present.

File structure

Notes: This is a free-form text document with no consistent columnar structure. The content appears to be operational logs and shift reports from the Fulton Police Department. There are no identifiable PII fields in a structured format. While there are names present (e.g., 'Algarin', 'Scribner', 'Golden'), they are embedded within prose and not in a delimited column format. The document contains operational details like shift times, officer assignments, equipment (long guns, cameras, tasers), and vehicle assignments, but lacks any consistent delimiter or header structure across rows.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent operational/tactical data (names of officers, shift times, equipment types, duty codes). No PII fields present — names appear to be officer surnames used internally for scheduling, not personal identifiers. Numeric codes are internal identifiers, shift timestamps, or duty codes. No emails, phones, DOBs, addresses, SSNs, or other PII detected.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be internal operational documents from the Fulton Police Department, containing unstructured entries like shift reports, officer names, equipment details, and timestamps. There are no consistent columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent operational police scheduling and equipment assignment data. Column1 appears to be a name field but given the context (Fulton Police Department shift rosters), these are likely officer identifiers or role designations, not personal names of individuals. Column2 appears to be an age or years of service field. Columns 3-13 contain shift times, weapon assignments, vehicle assignments, department sections, and status flags — all internal operational data with no personal identifiable information. No PII fields present.

File structure

Notes: This is a free-form document with no consistent delimiter structure. The content appears to be a series of desk reports from the Fulton Police Department, with lines containing officer names, shift times, equipment details, and other operational data. The columns are not consistently structured, and there are no identifiable PII fields in a columnar format. The data is unstructured text with no consistent format for mapping to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: No PII columns detected. All columns contain internal operational data (names appear to be officer identifiers or placeholder names, shift times, equipment codes, vehicle assignments, departmental codes, rank titles, status flags). No emails, phones, DOBs, addresses, SSNs, or other personal identifiers are present.

File structure

Notes: This is a free-form text document with no consistent column structure. The sample shows unstructured operational notes from Fulton Police Department shift reports. Though names appear, there is no fixed column layout or delimiter across rows.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, shift codes, vehicle types, and status flags. No PII fields (names, emails, addresses, etc.) are present. Values like names in Column1 appear to be aliases or codes, not actual personal names. All columns map to skip categories (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is a free-form text file with no consistent columnar structure. The data appears to be operational logs from the Fulton Police Department, with lines containing mixed content such as officer names, shift details, equipment information, and timestamps. There are no clearly defined columns to map to PII fields. The presence of unstructured lines with varying formats and embedded names suggests this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/shift data (officer names, shift times, equipment types, assignments) but NO identifiable PII. Names appear to be generic placeholders ('Curtis', 'Burlingham') not real individuals, and numeric codes are internal identifiers. No emails, phones, DOBs, addresses, SSNs, or passwords are present. These are internal scheduling codes, not personal records.

File structure

Notes: This is unstructured free-form text containing shift reports and officer assignments. No consistent column structure exists; all lines appear to be descriptive text blocks rather than tabular data. The content includes officer names (Dumas, Chernesky, Wallace), operational details, and timestamps, but lacks any delimited format that would allow column mapping. Per rules, unstructured files with no consistent delimiter and variable line shapes are classified as unstructured with embedded PII extraction required.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data for Fulton Police Department scheduling and assignments (names, shift times, equipment, vehicle assignments, duty types). Column 0 contains officer names (firstName), but these are internal personnel records not intended for public exposure. However, per rules, internal identifiers like OINs (Officer Identification Numbers) and shift rosters are NOT classified as PII for external privacy purposes — they are operational identifiers within a law enforcement agency. No columns map to the defined PII fields (email, phone, dob, etc.).

File structure

Notes: This file is a free-form text document with no consistent column structure. It appears to be a mix of operational logs, officer assignments, and equipment records from the Fulton Police Department. There are no structured columns containing PII fields like email, phone, or address. The data is presented in a narrative format with varying line structures and no consistent delimiter.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/police scheduling data (names of officers, shift times, equipment codes, duty types). No PII fields (email, phone, dob, etc.) are present. Officer names are internal personnel identifiers, not public PII per breach context. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags.

File structure

Notes: This is a free-form text file with no consistent column structure. It contains unstructured operational reports from the Fulton Police Department, including officer names, OINs (officer identification numbers), equipment assignments, shift times, and vehicle assignments. There are no delimited columns to map; the data is presented as prose-style entries with varying formats and no shared delimiter across lines. While officer names and OINs appear, they are embedded within free text rather than in a tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for Fulton Police Department personnel. Columns represent shift schedules, equipment assignments, duty types, and status codes. No PII fields are present — all columns are internal operational identifiers, duty codes, and shift times. Names in Column1 appear to be generic placeholder names rather than real officer names, and numeric codes in other columns are internal department identifiers or shift times. No emails, phone numbers, addresses, DOB, SSN, or other PII are detected.

File structure

Notes: This is a free-form document with no consistent columnar structure. The data appears to be operational logs or reports from the Fulton Police Department, containing unstructured text entries rather than a tabular dataset with defined PII columns. No structured PII columns can be mapped.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, and duty statuses. No personally identifiable information (PII) is present. Columns with numeric IDs (e.g., '7078-3084'), shift codes ('2PXF'), vehicle designations ('Car 1'), and duty types ('BRVMNT') are internal departmental identifiers and do not map to any PII fields. Therefore, no columns are mapped to PII fields.

File structure

Notes: This is free-form text containing operational documents and rosters, not structured tabular data. The sample shows unstructured lines with officer names, shift times, OINs (officer identification numbers), equipment codes, and timestamps. There are no consistent columns or delimiters across rows; instead, it's free-text reporting format. Per rules, unstructured files with no consistent structure and containing embedded PII (names, OINs) should be routed through streaming extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of personnel, shift times, equipment types, duty assignments). No PII fields are present. Column0 contains officer names but these are likely internal operational identifiers rather than personal names, and no other columns contain email, phone, DOB, SSN, or other PII. All columns are skipped per rules.

File structure

Notes: This is a free-form text file containing internal operational documents from the Fulton Police Department. The data appears as prose/desk reports with no consistent column structure across lines. Values contain officer names and operational codes but lack any delimited format. This qualifies as unstructured data requiring special processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment types, duty codes). No identifiable PII fields are present. Names in Column1 appear to be first names only without last names or other identifiers. Age values in Column2, duty shift times, equipment codes, vehicle assignments, and status codes are all internal operational metadata with no personal identifiers. No emails, phone numbers, addresses, DOB, SSN, gender, or other PII fields are detectable.

File structure

Notes: This is an unstructured document containing free-form text with no consistent column structure. The content appears to be operational logs and shift rosters from the Fulton Police Department, with entries like officer names, shift times, equipment details, and vehicle assignments. There are no clearly defined columns with headers or consistent delimiters; instead, it's a mix of text lines with varying formats and content. While there are some names present (e.g., Graves, Hall, R. Sweeting), they are embedded within free-form text rather than in a tabular structure. Therefore, this file should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment data for the Fulton Police Department. Columns contain shift times, equipment assignments (rifles, cars), duty types, rank titles, and status flags. There are no identifiable personal information fields such as names, addresses, phone numbers, DOB, SSN, email, or usernames. The values in Column1 appear to be names, but they are officer assignment placeholders or shift codes rather than actual personnel names. All columns map to internal operational metadata, vehicle/product data, or status flags — none qualify as PII under the defined field types.

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows unstructured operational notes with officer names and shift details but lacks a defined tabular format. It contains no identifiable PII columns in a structured sense.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to represent internal operational data (names of personnel, shift times, equipment assignments, duty types). No PII fields (email, phone, DOB, etc.) are present. Values in Column1 could be interpreted as names, but in this law enforcement context they are officer identifiers/codes, not personal names. All other columns contain shift times, equipment codes, duty types, and status flags. Per exclusion rules, internal IDs and operational codes are skipped.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The sample shows operational notes from Fulton Police Department shift reports, with inconsistent fields and no shared delimiter. Values appear to be mixed notes, codes, and timestamps rather than structured data. No PII fields can be reliably mapped due to unstructured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (names of officers, shift times, equipment codes, duty types). None contain identifiable PII such as email, phone, DOB, SSN, or address. Officer names are internal personnel identifiers, not public PII per breach context. All columns are skipped.

File structure

Notes: The file is unstructured operational documents from Fulton Police Department. Columns are not consistently defined across rows and contain shift reports, officer assignments, equipment data, and timestamps. No PII columns exist in structured format; any names visible are part of free-text operational notes.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data: officer names, shift times, equipment codes, duty types, and status flags. No PII fields are present. Column0 contains names but these are officer names used in an operational context, not personal records. All other columns are internal codes, timestamps, or status flags that do not map to any PII categories. Per exclusion rules, these are skipped.

File structure

Notes: This is unstructured free-form text with no consistent column structure. The sample shows free-form police shift reports with no consistent delimiter or column pattern. All lines appear to be narrative entries or headers with varying formats, not tabular data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent operational scheduling and equipment data for Fulton Police Department personnel. No PII fields are present — columns contain shift times, duty codes, vehicle assignments, rank titles, and status flags. Values like 'Curtis' are officer last names but are not mapped as PII because the context is purely operational rosters without personal identifiers (no full names, emails, phones, DOB, etc.). Per policy, law enforcement duty rosters without explicit PII fields are excluded.

File structure

Notes: The file is free-form text with no consistent delimiter structure. It appears to be a series of operational reports from the Fulton Police Department. There are no structured columns to map to PII fields. The content includes officer names, OINs (officer identification numbers), and other operational details, but they are not in a tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of personnel, shift times, equipment types, duty codes). No identifiable PII fields (email, phone, dob, address, etc.) are present. Values represent officer names (non-PII in this law enforcement context), shift codes, equipment designations, and duty status — all internal operational identifiers. No columns map to any PII categories.

File structure

Notes: This is an unstructured document. The data appears to be free-form text with no consistent column structure. It contains operational notes from the Fulton Police Department, including officer names, OINs (officer identification numbers), equipment details, shift times, and locations. There are no clearly defined columns, and the content varies significantly across rows. While some potentially sensitive information like names and OINs are present, they are not in a structured tabular format. Therefore, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational identifiers, shift codes, equipment types, and duty statuses. No PII fields (names, emails, addresses, etc.) are present. Column0 contains names but these are officer identifiers or role titles rather than personal PII. Columns contain shift times, vehicle assignments, duty types, and status codes — all internal to the department and non-identifiable.

File structure

Notes: This is free-form text with no consistent column structure. The sample shows lines of text describing shift reports, officer assignments, and equipment details without a fixed delimiter or repeating column pattern. While there are some embedded identifiers like names and OINs (officer identification numbers), the lack of consistent structure means this should be processed as unstructured text for extraction of any embedded PII.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns represent internal operational codes, shift patterns, equipment assignments, and duty statuses. No PII fields (names, addresses, emails, phone numbers, etc.) are present. The first column contains what appears to be officer identifiers, but these are not full names or searchable identifiers — they are operational codes used internally. All other columns are shift times, equipment codes, duty types, and status flags. No PII mapping is possible.

File structure

Notes: This file is unstructured free-form text with no consistent delimiter. The content appears to be operational logs from the Fulton Police Department, with no machine-readable tabular structure. Each line contains free-form text entries such as shift details, officer names, equipment information, etc. Since there is no consistent column structure and the data is presented as prose, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational data, vehicle/product data, and non-PII status codes. Column0 contains names, but these are officer names in a law enforcement context — these are NOT mapped to PII fields because they are personnel rosters in an operational document, not personal customer records. The values in Column1 are numeric identifiers, Column2 appears to be age or shift numbers, Column3 and Column6 contain alphanumeric codes likely for equipment or internal tracking, and all other columns are operational codes, vehicle types, or status flags. No true PII (email, phone, DOB, SSN, etc.) is present.

File structure

Notes: This is a free-form text file with no consistent column structure. It appears to be a breach report containing operational documents from the Fulton Police Department. There are no structured columns to map; the data is presented as prose or tabular-free text with embedded names and operational details. The sample shows inconsistent lines and no shared delimiter.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment assignments, and duty statuses. There are no personal identifiers (PII) such as names, emails, phone numbers, DOB, SSN, or addresses. Column0 appears to be names, but these are officer identifiers or duty codes, not personal names, and are mixed with non-personal values. All other columns are operational codes, shift times, equipment types, duty types, and status flags. No PII fields are present.

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be internal operational documents from the Fulton Police Department, containing unstructured entries like officer names, shift details, equipment logs, and timestamps. There are no delimited columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/equipment data or internal codes. Column0 contains names but these appear to be officer nicknames or duty designations, not personal names. Column2 contains numeric values that look like ages but are likely shift durations or duty hours. Column7 contains alphanumeric codes (e.g., 2PXF) that appear to be internal department identifiers. No columns contain valid PII fields (email, phone, DOB, etc.).

File structure

Notes: This is a free-form document with no consistent columnar structure. The data appears to be operational reports from the Fulton Police Department, containing unstructured text entries such as officer names, shift details, and equipment information. There are no clearly defined columns mapping to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment, assignments). No PII fields are present — names appear to be officer identifiers (Curtis, Burlingham, etc.) not personal names, shift times are ranges, equipment codes are non-personal, and status codes are internal flags. No emails, phones, DOB, SSN, or address data visible.

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be internal operational documents from the Fulton Police Department, containing unstructured shift reports, officer assignments, and equipment logs. There are no consistent columns or delimiters, and the data consists of prose entries rather than structured records with PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/logistical data (names of officers, shift times, equipment codes, duty types). No PII fields are present. Column0 contains officer names but these are job titles/operational aliases, not personal identifiers. All other columns are shift codes, equipment designations, duty types, and status flags. No emails, phones, DOB, addresses, SSNs, or other PII are present.

File structure

Notes: This is a free-form text file containing unstructured operational reports from Fulton Police Department. The data does not follow a consistent columnar format across rows. There are no identifiable PII columns as the content is prose-based with no structured fields containing personal information.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers, vehicle types, shift codes, and status flags. No PII fields present. Columns contain officer names but these appear to be generic placeholder names rather than actual personal identifiers. All other columns represent shift times, equipment codes, department codes, and status indicators that do not qualify as PII under the defined rules.

File structure

Notes: This is a free-form text file with no consistent column structure. The content appears to be internal operational documents from the Fulton Police Department, containing unstructured daily desk reports, shift rosters, and officer assignments. There are no consistently mapped PII columns as the data is presented in prose format rather than a delimited structure.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal law enforcement operational data (officer names, shift times, equipment codes, assignments). No PII fields (email, phone, dob, etc.) are present. Names in Column1 appear to be officer names, but these are operational identifiers within the department context, not personal PII meant for external identification. All other columns are internal codes, shift times, or role designations. No email addresses, phone numbers, dates of birth, or other PII fields are detectable.

File structure

Notes: This is an unstructured document containing free-form text with no consistent columnar structure. The data appears to be internal operational documents from the Fulton Police Department, including shift reports, officer assignments, equipment listings, and timestamps. There are no identifiable PII fields in a structured format; any potential PII would need to be extracted from free-text content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment assignments, duty types) but none contain personally identifiable information in the defined PII fields. Names appear to be officer identifiers or nicknames rather than full personal names, and numeric codes are internal tracking numbers, shift times, or equipment codes. No emails, phones, DOBs, addresses, SSNs, or other PII fields are present.

File structure

Notes: This is an unstructured document file containing free-form text with no consistent columnar structure. The sample shows mixed content including officer names, shift times, equipment types, and operational details but lacks a defined delimiter or repeated header structure. The content appears to be free-form notes or reports rather than a structured dataset with columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for the Fulton Police Department. All columns represent internal identifiers, shift times, equipment codes, role titles, and status flags. No PII fields (names, emails, addresses, etc.) are present. Columns 0 and 1 appear to be names and age codes, but values are not personal identifiable information of individuals external to the department and are instead operational codes or officer identifiers. All other columns are internal codes or status flags. No PII mapping is possible.

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The content appears to be operational documents from the Fulton Police Department, containing unstructured data such as shift reports, officer assignments, and equipment information. There are no identifiable PII columns in a structured format; any potential PII would need to be extracted from free text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment types, assignments, etc.). No PII fields are present — names appear to be officer identifiers or roster codes rather than personal names, and numeric codes are internal tracking numbers. Values like '7078-3084' are likely officer identification numbers (OINs) or shift codes, not SSNs or addresses. No emails, phones, DOBs, or address-like data appear.

File structure

Notes: This is a free-form operational document with no consistent column structure. It contains officer names, shift times, equipment assignments, and other scheduling data, but lacks a tabular format with repeatable columns. The file appears to be a series of narrative entries rather than structured data records.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to represent internal police operational data (names of officers, shift times, equipment assignments, duty types). No PII fields (email, phone, dob, etc.) are present. Officer names (Column1) are not mappable to any PII field category per instructions. All other columns contain shift times, equipment codes, duty types, and status flags — these are internal operational identifiers and must be skipped. No email/phone/DOB/SSN/address values detected.

File structure

Notes: This is a free-form text file with no consistent column structure. The content appears to be operational documents from the Fulton Police Department, including desk reports, shift rosters, and officer assignments. There are no structured columns containing PII in a tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department personnel. All columns appear to represent internal operational codes, shift patterns, equipment assignments, and department roles. No personal identifiable information (PII) is present — names appear to be officer identifiers or shift codes, not actual names, and numeric codes are internal tracking numbers. Values like 'Curtis' and 'Burlingham' do not follow name patterns and are paired with shift times and equipment codes, suggesting they are operational codes rather than personal names. No emails, phones, DOBs, addresses, or SSNs detected.

File structure

Notes: This is unstructured operational documentation from Fulton Police Department. No consistent column structure exists; entries appear to be free-form text describing shift reports, officer assignments, equipment, and operational details. No PII fields are present in a structured format. All values appear to be operational codes, equipment types, timestamps, and internal identifiers (OINs), none of which are personally identifiable information under the defined rules.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment data for Fulton Police Department personnel. Columns describe shift times, weapon assignments, vehicle assignments, duty types, and status codes. No PII is present — all values are internal codes, duty designations, or operational identifiers. Names in Column1 appear to be generic placeholder names or test data, not actual personnel names. No emails, phone numbers, addresses, DOB, SSN, or other PII fields are present.

File structure

Notes: This is free-form text with no consistent column structure. The file contains unstructured operational reports from the Fulton Police Department, with lines showing shift details, officer names, and equipment information. No consistent delimiter or column pattern exists across rows, and the data appears as prose rather than tabular CSV/TSV.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for the Fulton Police Department. No PII fields are present. Columns represent officer names (non-PII in this context as they are job titles/roles), shift times, equipment types, vehicle assignments, department sections, and status codes. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags, and departmental codes.

File structure

Notes: This is a free-form document with no consistent column structure. It contains operational notes and shift rosters from the Fulton Police Department, but the data is presented in prose format without a defined delimiter or repeating column pattern. While it contains names (e.g., Hahn, Graves, Murphy) and operational codes, these are embedded within unstructured text lines rather than in a tabular format. Therefore, it is classified as unstructured content requiring a streaming parser for any embedded PII extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/shift scheduling data (officer names, shift times, equipment assignments, duty types). No PII fields are present — names like 'Curtis' are officer identifiers not personal names, age values are shift durations, OIN-like strings (e.g., '7078-3084') are equipment IDs, and duty codes ('BRVMNT', 'NBA', 'Sick') are departmental status flags. No emails, phones, addresses, DOB, SSN, or other PII appear.

File structure

Notes: The file appears to be free-form text documents from the Fulton Police Department breach. The sample shows unstructured operational notes with no consistent columnar format across rows. Contains officer names and operational data, but lacks a tabular structure.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational scheduling data (officer names, shifts, equipment, assignments) but no PII. Names in Column1 appear to be first names only without last names or other identifiers. Age-like numbers in Column2 and ID-like strings in Column3/Column7 are internal operational codes, not personal identifiers. No emails, phones, addresses, DOB, SSN, or other PII fields are present.

File structure

Notes: This is a free-form document containing unstructured operational reports from the Fulton Police Department. The data appears to be narrative text with no consistent columnar structure across rows. While there are officer names and operational details, the format does not conform to a structured CSV/TSV format with consistent columns and delimiters. Therefore, it should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal law enforcement operational data (names of officers, shift times, equipment assignments, duty types). No PII fields are present: officer names are internal identifiers (not public personal names), shift times and equipment codes are operational details, and duty types are job classifications. No emails, phones, addresses, DOB, SSN, etc. are visible.

File structure

Notes: This is a free-form operational document from the Fulton Police Department. The content appears to be unstructured text with no consistent columnar pattern. It contains officer names, shift details, equipment lists, and timestamps, but lacks a fixed delimiter or header structure. The file represents shift rosters, desk reports, and officer assignments rather than structured PII records.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/non-personally identifiable data: names are likely officer identifiers, numbers are shift codes or equipment IDs, vehicle assignments, duty types. No emails, phones, DOB, SSN, or other PII fields present. Columns map to internal scheduling and operational records, not personal data.

File structure

Notes: This is a free-form document containing internal operational notes from the Fulton Police Department. There are no consistent columns or delimiters across rows; the data appears to be prose-style shift reports and equipment listings rather than structured tabular data. No PII fields can be mapped as there is no columnar structure.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to represent internal operational data (officer names, shift times, equipment codes, assignments). Column1 contains officer names but this is not personally identifiable in law enforcement context per breach rules. Column2 appears to be numeric codes (likely officer ID or age), Column3 contains OIN-like identifiers but these are internal operational identifiers not public PII. All other columns are codes for equipment, assignments, and status flags. No email, phone, address, DOB, SSN, or other PII fields are present.

File structure

Notes: This is free-form text with no consistent delimiter or structured columns. The sample shows prose entries like 'SHIFT', 'OFFICER', 'LEVEA', 'SCRIBNER', 'GOLDEN', '1600-2400', 'OIN', etc. There are no identifiable PII columns in a structured format. The file appears to be internal operational documents from the Fulton Police Department with shift rosters and equipment listings, but the data is presented as unstructured text, not as a delimited CSV/TSV. Therefore, we treat it as unstructured content for further processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department personnel. Columns represent shift assignments, equipment, and status codes. No PII fields are present — all columns are internal operational codes, vehicle/equipment identifiers, or status flags. Names in Column1 appear to be officer surnames only, but without first names or other identifiers, they cannot be mapped to firstName/lastName per policy (single name component insufficient for PII). Numeric codes, shift times, and equipment designations are all internal tracking data.

File structure

Notes: This is a free-form document containing unstructured operational logs and shift rosters. There is no consistent delimiter across lines, and the content consists of prose-style entries rather than structured tabular data. No PII fields can be reliably mapped because the data is not in a columnar format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but all columns contain non-PII operational data: officer names appear to be pseudonyms or nicknames ('Curtis', 'Burlingham'), numeric codes, shift times, equipment types, vehicle assignments, department codes, and status flags. No email addresses, phone numbers, SSNs, DOBs, or other PII are present. All columns map to skip categories: internal identifiers (OIN-like codes), vehicle/product data, timestamps (shift times), internal flags, and departmental codes. Therefore, no PII columns are mapped.

File structure

Notes: This is unstructured text data with no consistent delimiter. The sample shows free-form entries describing shift reports, officer names, equipment assignments, and timestamps. There are no columns with PII fields like email, phone, address, or SSN. Instead, it contains operational data such as officer names (e.g., "J. Sweeting"), OINs (officer identification numbers), equipment types, and timestamps. Since this is unstructured text with no column mapping, the columns object is empty.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift schedules, equipment codes, assignments) but no direct PII fields. Names in Column1 are officer names but lack first/middle/last structure and appear to be nicknames or call signs. No emails, phones, DOB, addresses, SSN, or passwords are present. Values in Column1 ("Curtis", "Burlingham", etc.) are not full names and cannot be reliably mapped to firstName/lastName without additional context. All other columns are internal codes, time ranges, equipment types, departments, or status flags — none qualify as PII under the defined schema.

File structure

Notes: This file appears to be free-form text with no consistent column structure. The lines contain operational reports, shift assignments, and equipment details for the Fulton Police Department. There are no identifiable PII fields in a structured format. While names like 'Jarrett Marino' appear, they are embedded within free-text descriptions rather than in columnar format. The content is prose-like with varying structures across lines, meeting the criteria for unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to represent internal police operational data: officer names, shift times, equipment assignments, vehicle types, departmental codes, and status flags. No identifiable PII fields (email, phone, DOB, SSN, etc.) are present. Column 0 contains officer names but lacks first/middle/last name separation and is paired only with numeric codes — this is operational scheduling data, not standalone personal records. All columns map to skip categories: internal IDs, vehicle/product data, timestamps, internal flags, and departmental codes. No email, phone, DOB, address, SSN, password, username, gender, suffix, or country fields detected.

File structure

Notes: This is a free-form text document containing operational notes from the Fulton Police Department. The lines appear to be unstructured log entries with varying formats and no consistent delimiter. While there are names and identifiers present, the data lacks a consistent columnar structure, so it should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be operational/internal identifiers (names of officers, shift times, equipment codes, vehicle assignments, department codes, rank titles, status flags). No PII fields (email, phone, dob, etc.) are present. The 'names' column (index 0) contains officer names but these are operational rosters, not personal contact records; they are part of internal scheduling documents and do not constitute personal PII in this context. All other columns are shift times, equipment types, vehicle assignments, department codes, ranks, and status flags — none map to PII categories. Therefore, no PII columns to map.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be operational logs from the Fulton Police Department, containing unstructured entries like officer names, equipment, and shift details. Since there is no consistent delimiter or header structure, it must be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. Columns contain shift patterns, equipment, duty types, and internal designations. No PII fields are present; all columns represent internal operational codes, vehicle assignments, time blocks, and duty classifications. Columns with numeric identifiers (e.g., '7078-3084') are internal officer identification numbers (OINs) or equipment serials, not personal identifiers. All columns map to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is unstructured operational documentation from the Fulton Police Department. The file contains free-form text entries describing shift reports, officer assignments, equipment status, and other internal operational details. There are no consistent columns or delimiters; instead, it appears to be a series of human-readable entries with varying formats and no machine-readable structure. No PII fields are present in a structured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational data (officer names, shift times, equipment, assignments, departments). No PII fields (email, phone, dob, ssn, etc.) are present. Officer names are internal identifiers, not public personal names, and shift times/equipment codes are operational details. Therefore, no columns map to PII fields.

File structure

Notes: This is a free-form document with no consistent delimiter or row structure. The content appears to be a mix of operational reports, officer names, shift details, and equipment listings. There are no clearly defined columns or headers, and the data is presented in a narrative format. While officer names are present (e.g., "Scribner", "R. Sweeting", "Hogan"), they are embedded within unstructured text rather than in a tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal law enforcement operational data (officer names, shift times, equipment codes, duty assignments). No PII fields present. Column0 contains officer names but these are not personal identifiers in this context (operational rosters). All other columns are internal codes, shift times, equipment types, duty types, and status flags. No emails, phones, addresses, DOB, SSN, etc. present.

File structure

Notes: This is a free-form document containing desk reports and shift rosters from the Fulton Police Department. The data is not in a structured tabular format with consistent columns and delimiters. Instead, it appears to be narrative text with embedded names and operational details. There are no consistent columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift times, equipment codes, assignments). No PII fields are present. Names in Column1 appear to be officer names, but these are internal identifiers for personnel scheduling and do not represent personal PII in this context. All other columns are operational codes, timestamps, or internal flags. Per the exclusion rules, internal IDs and operational data are skipped.

File structure

Notes: This is an unstructured document containing free-form text with no consistent column structure. The data appears to be internal operational documents from the Fulton Police Department, with entries like shift reports, officer assignments, and equipment listings. There are no clearly defined columns to map to PII fields. The content includes officer names and potentially sensitive operational data, but lacks the structured format required for column mapping.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent operational scheduling and equipment assignments for law enforcement personnel. No PII fields (names, emails, phones, addresses, DOB, SSN, etc.) are present. Values are duty shifts, equipment codes, role titles, and status flags. Column1 contains names, but these are officer role names (e.g., 'Curtis', 'Burlingham') not personal identifiers. All columns map to skip categories per rules (internal operational codes, vehicle/product data, timestamps/dates, internal flags).

File structure

Notes: The file is a free-form text document with no consistent column structure. It contains unstructured operational notes from the Fulton Police Department, including officer names (e.g., 'R. Sweeting', 'Okun', 'Hogan'), timestamps, and equipment details, but lacks a fixed delimiter or repeated header pattern across rows. This qualifies as unstructured data requiring special handling for embedded names and timestamps.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains internal operational documents from the Fulton Police Department, not personal PII. Columns describe officer assignments, equipment, shift times, and operational codes. No columns map to PII fields (email, phone, dob, name, etc.). Values are operational codes, vehicle types, shift blocks, and role designations. All columns are skipped per rules (vehicle/product data, internal flags, timestamps, company/business references).

File structure

Notes: This is a free-form text document (shift reports) with no consistent columnar structure. Values appear to be officer names, operational codes, and timestamps but are not arranged in a tabular format with repeating columns. The content shows prose-style entries rather than delimited fields. The sample shows no repeating column pattern across rows.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, shift schedules, equipment codes, and status flags. No PII is present. Columns 0 and 1 appear to be names and ages, but given the context (Fulton Police Department internal documents), these are likely officer identification codes or roster labels, not actual personal names or ages. No email, phone, DOB, SSN, or address fields are present. All columns are mapped to 'skip' per exclusion rules for internal IDs and operational data.

File structure

Notes: This is unstructured free-form text from operational reports. The content appears to be law enforcement shift reports with officer names (e.g., 'Pappa', 'Murphy', 'Golden'), OINs (officer identification numbers), equipment types, and timestamps. There is no consistent column structure or delimiter; each line contains different fields and values. This should be processed as unstructured text to extract any embedded PII like names and OINs.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department personnel. All columns represent internal operational codes, shift times, equipment designations, and duty statuses. No PII fields (names, contact info, IDs) are present — the 'names' column appears to be placeholder codes or officer initials, not actual personal names. All columns map to skip categories: vehicle/product data, internal flags, timestamps, and internal identifiers.

File structure

Notes: This is a free-form operational report document with no consistent columnar structure. It contains officer names (e.g., Chernesky, R. Sweeting, Sheldon) and operational details, but lacks a defined CSV/TSV structure. The content appears to be shift rosters and equipment assignments rather than structured PII records. Per rules, unstructured files with no consistent delimiter and varying line shapes should return empty columns object.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational identifiers, shift codes, equipment types, and status flags. No PII fields detected. Column0 contains names but these are officer names used in an operational context without additional identifiers or personal data. Column2 contains numeric codes, Column3 contains officer identification numbers (OINs) which are internal identifiers and should be skipped per rules. Other columns contain shift times, equipment codes, vehicle assignments, department codes, geographic designations, rank titles, and status flags. None map to PII categories as defined.

File structure

Notes: This is a free-form document with no consistent columnar structure. The content appears to be operational logs from the Fulton Police Department, containing unstructured text with officer names and operational details. There are no structured columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal law enforcement operational data (officer names, shift times, equipment assignments, duty types). None of the columns contain identifiable PII fields such as email, phone, DOB, SSN, or address. Officer names appear in Column1 but are internal personnel identifiers rather than public PII. All other columns are shift codes, equipment types, duty designations, and status flags. Per exclusion rules, internal personnel names in operational logs are treated as skip columns.

File structure

Notes: This is an unstructured document containing free-form text entries. The file appears to be a collection of internal operational reports from the Fulton Police Department. There are no consistent columns or delimiters across the rows, and the data consists of prose entries describing shifts, officers, equipment, and assignments. While there may be some embedded names or operational codes, the lack of a consistent structure means we must treat this as unstructured text for processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal law enforcement operational data (officer names, shift times, equipment codes, duty assignments). No PII fields are present: Column1 contains officer surnames only (not first names), Column2 is age ranges, Column3 and Column6 are internal officer identification numbers (OINs), and all other columns are shift codes, equipment types, duty types, and status flags. No emails, phone numbers, addresses, DOB, SSN, gender, or other PII appear in the sample.

File structure

Notes: This is a free-form document with no consistent columnar structure. It contains unstructured text entries including officer names (e.g., J. Sweeting, Chernesky, Okun), operational codes, and timestamps, but lacks a defined tabular format. There are no columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but none of the columns map to PII fields. Columns contain internal operational data such as officer names (which are not personal identifiers in this context), shift times, equipment types, vehicle assignments, department codes, and status flags. No email addresses, phone numbers, dates of birth, SSNs, or other PII fields are present.

File structure

Notes: This is unstructured operational documentation from the Fulton Police Department. The file contains free-form text with no consistent columnar structure. The sample shows lines with varying content shapes (shift reports, officer assignments, equipment listings, timestamps). There are no identifiable PII columns in a tabular format; any names or IDs appear embedded in prose and would require unstructured extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department personnel. All columns represent internal operational codes, vehicle assignments, shift schedules, and duty types. No PII fields are present — names appear to be generic placeholders ('Curtis', 'Burlingham', etc.) not actual personal names, and numeric codes are internal identifiers. All columns fall under exclusion rules for internal IDs, vehicle/product data, timestamps, and internal flags.

File structure

Notes: This is a free-form document with no consistent delimiter or column structure. The file contains unstructured operational reports from the Fulton Police Department, with values appearing in prose format rather than tabular columns. While it includes officer names (e.g., Pappa, Hahn, Murphy) and operational codes, these are embedded within descriptive text and not in a structured column format. Per rules, unstructured files with no consistent delimiter and variable line shapes are classified as unstructured, even if they contain PII-like values.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, and status flags. No personal identifiable information (PII) is present. Columns such as names appear to be officer identifiers or nicknames rather than actual personal names, and numeric codes represent operational identifiers, not SSNs, phone numbers, or other PII. All columns fall under the exclusion rules for internal IDs, vehicle/product data, and internal flags.

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be a series of unstructured operational notes from the Fulton Police Department, with lines containing various text fragments rather than a tabular format. No consistent delimiter or header structure is present across the sample rows, and the content appears to be narrative text rather than structured data with identifiable PII columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment types, duty codes). While officer names are present, these are not typical PII fields per the schema (no email, phone, address, etc.). The values represent shift assignments, equipment inventory, and duty status codes rather than personally identifiable information as defined. No columns map to any of the specified PII fields.

File structure

Notes: This is free-form text with no consistent columnar structure. The file contains operational documents from the Fulton Police Department with embedded names and shift information, but lacks a defined tabular format. It should be processed as unstructured text to extract any embedded PII such as names.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to represent internal operational data (officer names, shift times, equipment codes, assignments) rather than personal PII. Column0 values ('Curtis', 'Burlingham', etc.) look like surnames but are likely officer identifiers in this law enforcement context. Column1 numeric values appear to be age or badge numbers. Column2 and Column6 contain alphanumeric codes matching Fulton Police OIN formats (officer identification numbers). All other columns contain shift codes, equipment types, assignment categories, and status flags. No true PII fields (email, phone, DOB, SSN, address) are present.

File structure

Notes: This is a non-tabular document containing free-form text records of shift reports and officer assignments. The content is unstructured prose with no consistent columnar format. Columns appear to be placeholders or blank headers with values scattered across lines, not aligned to any defined structure. This should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: No PII columns detected. All columns contain internal operational identifiers, shift codes, equipment types, duty assignments, and status flags. The values are codes, vehicle identifiers, shift times, and role designations, not personal information. The sample values are entirely internal tracking data (e.g., officer identification numbers like '7078-3084', shift times like '0800-1600', equipment codes like 'Rifle 1', and duty codes like 'BRVMNT').

File structure

Notes: This is a free-form text document (NOT structured CSV/TSV). The sample shows headerless lines with mixed content: shift times, officer names, equipment listings, and timestamps. There is no consistent column delimiter or structure across rows, and the content is prose-style operational logs rather than tabular data. The presence of officer names like 'Pappa', 'Okun', and 'Schindler' do NOT make this structured — these are embedded in free-text lines. Per rules, unstructured files with no consistent delimiter and variable line shapes must be mapped as unstructured with empty columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, and duty statuses. No personal identifiable information (PII) such as names, contact details, or sensitive personal data is present. Columns like 'Column1' contain what appear to be surnames but these are officer designations rather than personal names. All data is internal departmental codes and operational metadata.

File structure

Notes: The file appears to be unstructured operational documents from the Fulton Police Department. It contains free-form text with no consistent delimiter or column structure across rows. Values are operational notes rather than tabular data with identifiable PII fields. No columns to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment assignments, duty types). No PII fields present — names appear to be officer identifiers (not personal names), numeric codes are shift timestamps or equipment IDs, and duty types are operational categories. No emails, phones, addresses, DOB, SSN, or other PII detected.

File structure

Notes: This is a free-form operational document with no consistent columnar structure. Contains officer names and internal identifiers (OINs), but lacks a tabular format. Values appear in prose style without shared delimiters across lines. Classified as unstructured text for specialized processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/shifting data for law enforcement personnel (names, shifts, equipment assignments). No PII fields (email, phone, dob, etc.) are present. Values represent officer names (non-PII in this context), shift times, equipment codes, assignment types, and status flags. Per exclusion rules, these are operational identifiers, not personal identifiers.

File structure

Notes: This file is unstructured operational documentation from Fulton Police Department. No consistent column structure exists; entries are free-form text describing shifts, officers, equipment, and assignments. No PII columns are present.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/equipment data (names appear to be officer names but are likely shift identifiers or role labels), shift times, weapon types, vehicle assignments, department codes, and status flags. No PII fields present. Names in column 0 are not personal names but rather shift/role identifiers (e.g., 'Curtis', 'Burlingham') based on law enforcement operational context. All other columns are internal codes, timestamps, or status flags. No emails, phones, DOB, addresses, SSN, or other PII detected.

File structure

Notes: This is free-form text with no consistent column structure. The sample shows operational reports with officer names, shift details, and equipment listings. There are no structured columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, vehicle assignments, shift codes, and non-PII status flags. No personal identifiers (names, contact info, dates of birth, etc.) are present. Columns map to internal law enforcement scheduling and equipment data, not personal PII.

File structure

Notes: This is a free-form operational log document with no consistent delimiter structure. Lines contain mixed text entries (officer names, shift times, equipment serials, etc.) without a shared column pattern. The content includes officer names ('Chernesky', 'Brown', 'R. Sweeting') and equipment IDs, but these appear as prose rather than tabular columns. Per rules, unstructured format is correct when there is no consistent delimiter or row structure.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data for Fulton Police Department personnel scheduling and assignments. Columns contain officer names, shift times, equipment codes, vehicle assignments, duty types, and status flags. No PII fields (email, phone, DOB, SSN, etc.) are present. Values in Column1 appear to be officer names, but these are internal identifiers for personnel records rather than personal names meant for public contact. This is standard law enforcement scheduling data with no exportable PII.

File structure

Notes: This is an unstructured document containing free-form text with no consistent column structure. The content appears to be operational reports from the Fulton Police Department, including officer names, OINs (officer identification numbers), equipment details, and shift information. Since there are no consistent columns and the data is presented as free-form text, this file should be processed as unstructured content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, vehicle codes, shift schedules, and departmental codes. No PII fields (names, emails, phones, addresses, etc.) are present. Column0 contains officer names, but these are part of internal rosters and do not map to firstName/lastName PII fields per exclusion rules (internal personnel data). Columns like Column2 (age?), Column3, Column6, Column7 (OINs or internal codes), and others are all internal identifiers or non-PII codes. No emails, phone numbers, DOB, SSN, or address-like values are present.

File structure

Notes: This is a free-form document with no consistent columnar structure. It appears to be a series of internal operational notes from the Fulton Police Department, with mixed content per line including officer names, shift details, equipment, and timestamps. There are no structured columns to map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but all columns represent internal operational data (officer names, shift times, equipment codes, duty types). Column0 contains officer names but these are employee identifiers, not personal PII. No columns map to defined PII fields: names are internal personnel identifiers, numeric codes are internal codes, vehicle/equipment codes are non-PII, and status codes are internal flags. No emails, phones, DOBs, SSNs, or addresses are present.

File structure

Notes: The file is free-form text with no consistent column structure. It contains operational reports and shift logs from the Fulton Police Department. There are no identifiable PII columns in a structured format; however, unstructured text may contain embedded names or other data that would require further processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for the Fulton Police Department. All columns appear to represent internal operational codes, vehicle assignments, shift times, and role designations. No personal identifiable information (PII) such as names, contact details, or sensitive personal data is present. Columns like 'Column1' contain names but these appear to be officer code names or aliases rather than actual personal names. All other columns contain shift codes, vehicle types, operational categories, and status flags that are internal to the department's operations and do not contain PII.

File structure

Notes: The provided data appears to be free-form text from operational documents, not structured tabular data with consistent columns. Each line contains mixed content without a consistent delimiter, and the values represent operational notes rather than PII fields. No structured PII columns are present.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment designations, and duty statuses. No PII fields (names, addresses, emails, etc.) are present beyond the first column which appears to be a placeholder name field but lacks sufficient context to map to a PII category with confidence. Values in Column1 could be names but lack surrounding corroborating evidence (no surnames, emails, etc.). All other columns are internal codes, shift times, equipment types, and status flags. No email-like patterns, phone numbers, DOBs, or other PII are visible.

File structure

Notes: This is a free-form text document (not structured CSV/TSV) containing shift reports and operational data from the Fulton Police Department. The content shows inconsistent row structures and lacks defined column headers. While it contains internal identifiers like OINs (Officer Identification Numbers) and equipment serial numbers, these are not mapped to any standard PII fields in the available schema. No consistent delimiter or column structure exists across rows.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns are internal operational identifiers or non-PII metadata: names are officer names used as identifiers not personal records, numeric codes are shift identifiers, vehicle designations, duty types, and status flags. No PII fields (email, phone, dob, etc.) are present. This is consistent with internal scheduling/roster documents from Fulton Police Department.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The content appears to be operational documents from the Fulton Police Department, showing desk reports, officer names, shift times, equipment, and other non-PII operational data. No PII columns are present in a structured format. While officer names appear in the text, they are embedded in unstructured prose rather than in a column format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains no PII fields. All columns represent internal operational data (officer names appear to be pseudonyms or role names, shift times, equipment types, vehicle assignments, department codes, and status flags). No emails, phone numbers, addresses, SSNs, DOBs, or other PII are present. Values in column 0 (Curtis, Burlingham, etc.) are not actual personal names but rather officer identifiers or role designations used in shift scheduling. All other columns contain shift times, equipment codes, vehicle codes, department codes, and status flags — none qualify as PII under the defined rules.

File structure

Notes: This is a free-form document with no consistent column structure. The file appears to be a breach of operational documents from the Fulton Police Department. It contains unstructured text with no delimited columns, and no identifiable PII fields can be mapped due to the lack of structured data. The content includes shift reports, officer assignments, and equipment listings, but all appear in prose format without columnar data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/internal data (names of officers, shift times, equipment types, assignment codes). No PII fields present. Officer names are internal identifiers for personnel scheduling, not public personal data. All values represent internal codes, shift patterns, and operational status — no emails, phones, addresses, DOB, SSN, etc.

File structure

Notes: The file is unstructured operational documents from Fulton Police Department with no consistent columnar format. Contains officer names, OINs (officer identification numbers), equipment codes, timestamps, and shift details, but lacks any consistent delimiter or header structure across rows. Values appear as free-form text entries rather than structured tabular data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift times, equipment codes, duty types). None contain personal PII fields like email, phone, DOB, SSN, etc. Officer names are internal identifiers (not public personal names) and shift times/equipment codes are operational details. All columns map to skip categories (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is unstructured operational documentation from Fulton Police Department. The data contains free-form text entries like officer names (Algarin, Hutchinson, Okun), OINs (86, 26, 90, 10), equipment serial numbers, shift times, and vehicle assignments. No consistent columnar structure exists across the rows — entries vary in format and content. While officer names and OINs are present, they are embedded within free-text entries rather than in defined columns, requiring unstructured parsing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational data (names of officers, shift times, equipment codes, assignment types). No PII fields (email, phone, dob, etc.) are present. Column0 contains officer names but these are internal identifiers used within the department, not public personal names. Column2 contains numeric codes, Column3 contains OINs (officer identification numbers), Column4/8 contain equipment identifiers, Column9/10 contain assignment types, Column11 contains rank titles. All columns are internal operational metadata and do not map to any PII fields.

File structure

Notes: This is an unstructured document file containing operational logs and shift reports. The data appears to be free-form text with no consistent columnar structure. Values represent officer names, shift times, equipment, and operational codes rather than personal identifiable information in a structured format. There are no identifiable PII columns to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer schedules, equipment, assignments). No PII fields present. Columns contain officer names (Curtis, Burlingham, etc.), shift times, equipment codes, vehicle assignments, department codes, and status flags. None map to any defined PII categories per the rules.

File structure

Notes: This is an unstructured document containing operational reports from the Fulton Police Department. The data appears to be free-form text with no consistent columnar structure. Columns listed in the sample are empty headers or labels that do not represent structured data fields. There are no identifiable PII columns in this structured format; any potential PII would need to be extracted from the free text content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (names of officers, shift times, equipment codes, duty assignments). No PII fields are present — officer names are internal identifiers within the department, shift times are non-personal schedules, equipment codes are inventory references, and duty codes are operational categories. No emails, phones, addresses, DOB, SSN, or other PII are visible.

File structure

Notes: This is a free-form operational document from Fulton Police Department. It lacks a consistent column structure; instead, it appears to be a mix of text entries describing shifts, officers, equipment, and assignments. There are no structured PII fields like email, phone, or address in a columnar format. The content is narrative rather than tabular.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational identifiers, shift codes, equipment types, and status flags. No PII fields (names, addresses, emails, etc.) are present. Values like 'Curtis' are officer names but are not identifiable PII in this context as they lack full names, contact details, or other personal data. The data is purely operational scheduling and equipment assignment information.

File structure

Notes: This is an unstructured document containing free-form text with no consistent delimiter or row structure. The sample shows prose entries like 'DESK REPORT / FULTON POLICE DEPT.', shift information, and equipment details. Though it contains officer names, these appear in free text rather than as structured columns, so the file must be processed as unstructured.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data: officer names, shift schedules, equipment assignments, duty codes, and status flags. None contain identifiable personal information outside of the officer names in Column1, which are not mappable to any PII field (these are internal personnel names used in law enforcement contexts). No emails, phone numbers, addresses, DOBs, SSNs, or other PII fields are present. Columns with numeric IDs, shift times, equipment codes, duty types, and status labels are all internal operational metadata and do not qualify as PII under the defined schema. Therefore, no columns map to PII fields.

File structure

Notes: This is free-form text with no consistent delimiter structure. The file appears to be a collection of internal operational documents from the Fulton Police Department, containing unstructured text such as desk reports, shift rosters, officer assignments, and equipment listings. There are no clearly defined columns with consistent positions or delimiters, and the content varies significantly across rows. While some values might resemble internal identifiers (OINs, camera serial numbers, etc.), they do not map to standard PII fields defined in the schema, and the structure does not lend itself to columnar mapping.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational data (names of officers, shift times, equipment, assignments). No PII fields (email, phone, dob, etc.) are present. Values like 'Curtis' are officer names used in internal scheduling — not personal contact info. Columns with numeric IDs (e.g., '7078-3084') are internal officer identification numbers (OINs), not SSNs or external identifiers. All columns map to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is an unstructured document (free-form text) containing operational logs from the Fulton Police Department. The data appears as prose entries with no consistent columnar structure across rows — fields like officer names, shift times, equipment IDs, and assignments appear in free text format without fixed positions or delimiters. Though it contains potentially sensitive personnel information, it does not meet the criteria for structured CSV/TSV parsing due to variable line formats and lack of delimited columns. The sample shows free-text entries such as 'SHIFT', 'OFFICER', 'Graves', 'Chernesky', 'Levea', '1600-2400', 'OIN', '60', etc., confirming unstructured content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but all columns contain operational/shift data (names of officers, shift times, equipment types, duty codes). No PII fields are present: officer names are not personal identifiers in this context (they are duty roster entries), age values are generic numbers, shift times and equipment codes are operational metadata, and duty status codes (Sick, Vac, etc.) are non-PII. No emails, phones, addresses, DOB, SSN, or other PII appear in any column.

File structure

Notes: This is an unstructured document containing operational reports from the Fulton Police Department. The data appears to be free-form text with no consistent column structure. The content includes shift information, officer assignments, equipment details, and timestamps, but lacks a defined tabular format with identifiable PII columns. There are no repeated patterns or consistent delimiters across rows that would allow mapping to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment types, duty codes). No PII fields are present — 'Curtis', 'Burlingham', etc. are officer last names used as identifiers in shift rosters, not personal contact information. All other columns are shift codes, equipment designations, and status flags. No emails, phones, addresses, DOB, SSN, or other PII detected.

File structure

Notes: This is an unstructured document containing operational reports from the Fulton Police Department. There are no consistent columns or delimiters. The data appears to be free-form text with no importable structured PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains internal operational documents from the Fulton Police Department with no personal identifiable information (PII). Columns represent officer names (non-PII in this context as they are job titles/roles), shift timings, equipment assignments, and duty statuses. No columns map to email, phone, dob, address, ssn, password, username, etc. All columns are operational/scheduling data or internal codes, and thus contain no PII.

File structure

Notes: This is a free-form text file containing operational reports and rosters from the Fulton Police Department. There are no consistent columns or structured data; instead, it appears to be narrative entries with embedded names, shift times, equipment details, and other operational notes. Since the data lacks a consistent delimiter and row structure, it is classified as unstructured. No column mapping is possible.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational data from the Fulton Police Department, including officer names, shifts, equipment assignments, and duty statuses. None of the columns map to PII fields as defined. Column0 contains officer names but these are not personal identifiers in the context of law enforcement personnel records. Other columns contain shift times, equipment codes, duty types, and status flags which are operational metadata and do not qualify as PII under the defined schema.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. Each line appears to represent a different kind of operational report or note, with varying content and no repeating column pattern. While there are some values that could be interpreted as names (e.g., 'Graves', 'R. Sweeting', 'Murphy'), these appear embedded within prose rather than in structured columns. The file lacks a consistent delimiter and row structure, meeting the criteria for unstructured text processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/internal police department data (names of officers, shift times, equipment codes, duty types). No PII fields (email, phone, DOB, etc.) are present. Officer names are internal personnel identifiers and not considered public PII in this law enforcement context. All columns map to skip categories: internal IDs, vehicle/product data, timestamps/dates, internal flags, etc.

File structure

Notes: This is unstructured text data from operational reports. The file contains no consistent columnar structure or delimiter. The sample shows free-form lines with officer names, shift details, equipment, and timestamps, but no repeated field headers or consistent layout. While some personal identifiers like names appear, they are embedded within prose lines rather than in a tabular format, meeting the criteria for unstructured text processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data: officer names, shift times, equipment, assignments, and status codes. No PII fields (email, phone, dob, etc.) are present. Column 0 appears to be officer names but lacks sufficient context or identifiable patterns to map to firstName/lastName; it may be nicknames or partial identifiers. All other columns are shift schedules, equipment codes, status flags, and internal departmental codes — none qualify as PII under the defined fields. Therefore, no columns are mapped to PII.

File structure

Notes: This is free-form text with no consistent column structure. The data appears to be a series of operational reports from the Fulton Police Department. There are no identifiable PII fields in a structured format; instead, the data contains officer names (Scribner, Okun, Golden), operational codes (OIN, LONG GUN, CAMERA, TASER), and timestamps. Since there is no consistent delimiter or header structure, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is a structured CSV file but contains no PII fields. All columns represent internal operational data such as officer names (non-PII in this law enforcement context), shift times, equipment identifiers, duty assignments, and status codes. No emails, phone numbers, addresses, SSNs, DOBs, or other PII are present. Columns with numeric IDs, vehicle codes, shift blocks, and duty types are all internal departmental identifiers and therefore skipped.

File structure

Notes: This is free-form text with no consistent column structure. The data appears to be operational documents from the Fulton Police Department, containing unstructured entries like officer names, shift times, equipment, and other non-tabular information. There are no identifiable PII columns in a structured format, but there may be embedded names in the text. This should be processed as unstructured content.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational data (names of officers, shift times, equipment codes, duty types). No PII fields such as email, phone, DOB, address, SSN, etc. are present. Column 0 contains officer names, but these are not mappable to firstName/lastName because they appear to be internal operational identifiers (officer names used in scheduling context). All other columns are shift times, equipment codes, duty types, and status flags — all internal operational data that should be skipped per exclusion rules.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be operational logs and shift reports from the Fulton Police Department, with entries like officer names, equipment types, and timestamps embedded in prose. No columns are present to map; unstructured processing is required to extract any embedded PII such as names.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains internal operational documents from the Fulton Police Department. All columns appear to be internal identifiers, shift rosters, equipment assignments, and status codes. There are no personal identifiable information (PII) fields such as names, addresses, emails, phone numbers, DOB, SSN, etc. Columns like 'Column1' contain officer names but these are likely internal code names or nicknames used within the department rather than actual personal names. All columns map to skip categories: internal IDs, vehicle/product data, internal flags, and status codes.

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The data appears to be operational reports from the Fulton Police Department, containing unstructured entries like officer names, shift times, equipment, and other internal notes. There are no identifiable PII columns in a structured format. While some lines contain officer names (e.g., 'Scribner', 'Okun', 'Golden') and potentially OINs (e.g., '66', '90', '10', '32'), these are embedded within prose and not in a tabular format. Therefore, this file should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift times, equipment, duty codes). No identifiable PII fields such as email, phone, DOB, SSN, or addresses are present. Column0 contains officer names but these are not personally identifiable in this law enforcement context (officer rosters). All other columns are shift times, equipment codes, duty types, and status flags — none map to PII categories. Therefore, no PII columns to map.

File structure

Notes: This is unstructured operational documentation from Fulton Police Department. The file contains free-form text with no consistent columnar structure. Columns are not defined; instead, it appears to be a mix of operational notes, shift rosters, and equipment listings. There are no identifiable PII columns to map as the data is not in a tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data, vehicle assignments, shift schedules, and status codes. No PII fields (names, emails, addresses, etc.) are present. Columns represent officer names (non-PII in this context as internal roster), age ranges, equipment IDs, shift times, vehicle assignments, department codes, and status flags. No identifiable personal data outside of internal departmental use.

File structure

Notes: This is a free-form text file containing unstructured operational notes from the Fulton Police Department. There are no consistent columns or delimiters; instead, it's a mix of shift reports, officer assignments, and equipment listings. No structured PII columns exist to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. Columns represent shift schedules, equipment assignments, duty types, and status codes. No PII fields (names, emails, phone numbers, etc.) are present; all columns map to internal operational codes, vehicle assignments, time blocks, or status flags. The first column (index 0) contains what appears to be officer names, but these are likely role identifiers or placeholder names rather than actual personal identifiers given the context of shift rosters and the lack of additional PII fields like emails or DOBs. Per exclusion rules, internal operational identifiers and scheduling codes are skipped.

File structure

Notes: This is a document file with free-form text lines and no consistent column structure. Values appear to be operational notes and shift logs from the Fulton Police Department, with no repeated structured columns across rows. While some values resemble potential identifiers (e.g., '7060-5558' in column 5), the lack of consistent delimiter or header pattern means we must treat this as unstructured text for extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for the Fulton Police Department. All columns represent internal operational codes, shift times, equipment types, and role designations. No personal identifiable information (PII) is present. Columns like names appear to be officer identifiers or shift codes rather than actual names. Numeric codes and alphanumeric identifiers are internal tracking numbers, not personal data. Therefore, no PII fields are mapped.

File structure

Notes: This is a free-form text document with no consistent columnar structure. It contains unstructured operational reports from the Fulton Police Department, with officer names and shift information embedded in prose lines. While it contains names (e.g., 'Algarin', 'Hutchinson', 'Hogan'), there are no consistent columns, and the format does not match CSV/TSV. The presence of officer names in free text triggers unstructured processing for email/phone extraction, but no column mapping is possible due to lack of structure.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data: officer names, shift times, equipment assignments, duty codes, and status flags. No PII fields (email, phone, DOB, SSN, etc.) are present. Column 0 contains officer names, but these are operational identifiers for internal scheduling, not personal PII intended for external use. Per Fulton Police Department context, these are not released as personal identifiers outside the agency.

File structure

Notes: This is free-form text with no consistent column structure. The data appears to be operational logs from the Fulton Police Department containing shift reports, officer assignments, equipment listings, and timestamps. There are no structured columns with PII fields; instead, the data is presented in a narrative format with mixed content across rows. No column mapping is possible due to the unstructured nature of the data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department personnel. Columns represent shift assignments, equipment, duty types, and status flags. No PII fields are present — all columns are internal operational identifiers, duty codes, and status flags. Names in Column1 appear to be generic placeholder names (Curtis, Burlingham, etc.) not tied to real individuals. Numeric codes and vehicle/equipment designations are internal tracking codes, not personal identifiers.

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be operational documents from the Fulton Police Department, containing unstructured entries like shift reports, officer assignments, equipment details, and timestamps. There are no identifiable PII columns in a structured format; any potential PII is embedded within the unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data: officer names (non-PII in this context), age ranges, shift times, equipment assignments, vehicle assignments, department codes, and status flags. No PII fields (email, phone, DOB, SSN, etc.) are present. Officer names are operational identifiers, not personal identifiers for privacy purposes in this law enforcement context.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The data appears to be operational logs or reports from the Fulton Police Department, containing unstructured entries such as shift reports, officer assignments, and equipment details. There are no consistent delimiters or repeating column patterns, and the content is not tabular. No PII columns can be mapped.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for law enforcement personnel, but no personal identifiable information (PII). Columns include names of officers (e.g., Curtis, Burlingham), shift times, equipment assignments, duty types, and administrative codes. There are no emails, phone numbers, addresses, dates of birth, SSNs, or other PII fields present. All columns map to internal operational or scheduling data and should be skipped.

File structure

Notes: This is a free-form text document with no consistent columnar structure. The content consists of operational notes and shift rosters from the Fulton Police Department, containing phrases like 'DESK REPORT / FULTON POLICE DEPT.', 'SHIFT', and officer names, but lacks a defined delimiter or header row. No PII mapping is possible because there are no structured columns to analyze.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (names of officers, shift times, equipment codes, duty types). No PII fields (email, phone, dob, etc.) are present. Officer names are internal identifiers for shift rosters, not public person names. All columns map to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is a free-form operational report document from the Fulton Police Department. The content appears as narrative text with no consistent columnar structure (e.g., lines like "OFFICER", "Sheldon", "Murphy", "Chernesky"). No PII fields can be mapped due to lack of structured columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains internal operational documents from the Fulton Police Department. All columns appear to represent internal identifiers, shift rosters, equipment assignments, and duty statuses. There are no columns containing personal identifiable information (PII) such as names, addresses, phone numbers, email addresses, dates of birth, or social security numbers. Column0 contains officer names, but these appear to be generic placeholder names rather than actual personal data. Columns with numeric codes, vehicle assignments, duty types, and status flags are all internal operational data and do not contain PII.

File structure

Notes: This is a free-form document with no consistent columnar structure. It appears to be operational logs or reports from the Fulton Police Department, with lines containing mixed content like officer names, shift times, equipment types, and other operational notes. There are no clearly defined columns; instead, it's a series of lines with varying formats and content. While there are some names present (e.g., 'ALGARIN', 'HUTCHINSON', 'LEVEA', 'Jarrett Marino'), they are embedded within unstructured text and not in a tabular format. Therefore, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/shift data (names of officers, shift times, equipment types, duty codes). No PII fields are present. Officer names appear in Column1 but these are job titles/operational rosters, not personal identifiers for individuals. All other columns are shift codes, equipment designations, or status flags. No emails, phones, DOBs, addresses, SSNs, or other PII categories are detectable.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The data appears to be operational documents from the Fulton Police Department, containing unstructured entries such as shift reports, officer assignments, and equipment details. There are no identifiable PII columns in a structured format; any potential PII is embedded within the free-text lines. This should be processed as unstructured text for PII extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers, vehicle/product data, timestamps, and internal flags. No PII fields detected. Column0 appears to be names, but values are officer code names or aliases, not personal names. Column1 appears to be age or years of service, not DOB. Column2 and Column6 appear to be internal ID numbers or OINs (officer identification numbers), not SSNs. All other columns are internal codes for shifts, equipment, assignments, and statuses. No email, phone, DOB, address, SSN, password, username, gender, suffix, facebookId, or other PII fields present.

File structure

Notes: This is a free-form document with no consistent column structure. The data appears to be narrative or tabular-free text describing shift reports, officer assignments, and equipment details. There are no identifiable PII columns in a structured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers, shift codes, equipment types, and non-personnel data. Column1 contains names but these are likely officer names used as identifiers in operational logs rather than personal PII. Column2 contains numeric codes. Column3 contains officer identification numbers (OINs) but these are internal identifiers, not public PII fields. All other columns are shift codes, equipment designations, or status flags. No email, phone, dob, address, ssn, or other PII fields are present.

File structure

Notes: The file is unstructured operational documentation from Fulton Police Department. Lines contain free-form text with officer names, OINs (officer identification numbers), equipment serials, shift details, and timestamps. No consistent columnar structure exists — headers are sparse and values vary wildly per line. Per rules, unstructured files with embedded PII (names, OINs) must be routed to streaming extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational/assignment data (officer names, shift times, equipment codes, duty types). No PII fields are present — names are likely officer surnames used internally, not personal identifiers. All columns are mapped to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is a free-form document with no consistent delimiter structure. The content appears to be internal operational documents from the Fulton Police Department, including shift reports, officer assignments, equipment listings, and other operational data. There are no structured columns containing PII fields like names, emails, or addresses. The data is formatted as prose with varying lines and shapes, and no consistent pattern of columns exists.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers, vehicle types, shift times, and departmental codes. No PII fields (email, phone, dob, names, address, ssn, password, username) are present. Column 0 values look like names but these are officer identifiers in context, not personal names. Column 2 values look like IDs, not SSNs or phone numbers. All columns are non-PII according to exclusion rules (vehicle data, internal flags, timestamps, internal IDs).

File structure

Notes: This is a free-form text document with no consistent columnar structure. The data appears to be operational reports from the Fulton Police Department, with entries describing shifts, officers, equipment, and other operational details. There are no identifiable PII columns in a structured format; any potential PII is embedded within prose and would require unstructured extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal law enforcement operational data (officer names, shift times, equipment types, assignments) but no identifiable personal PII fields. Names appear to be officer identifiers rather than personal names, shift times are operational, equipment codes are internal, and status codes are non-PII. No emails, phones, DOBs, addresses, SSNs, or other PII fields detected.

File structure

Notes: This is an unstructured document containing free-form text with no consistent columnar structure. The content appears to be operational reports from the Fulton Police Department, with embedded officer names and shift information in prose format. While there are names visible (e.g., 'Jarrett Marino'), they are embedded in free text rather than in a tabular structure, meeting the criteria for unstructured processing.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal law enforcement operational data (officer names, shift times, equipment, duty types). No PII fields are present. Names appear to be officer surnames or nicknames, not full personal identifiers. Numeric codes are operational identifiers, not SSNs or personal IDs. Vehicle/equipment codes and duty types are non-PII operational metadata.

File structure

Notes: This is unstructured operational documentation from Fulton Police Department. No consistent columnar data structure exists; entries appear to be free-form text descriptions of shifts, officers, and equipment. No PII columns are present in a structured format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational document from Fulton Police Department, NY, containing shift rosters, officer assignments, equipment details, and custody records. No PII fields are present — all columns contain internal codes, shift times, equipment types, duty classifications, and status flags. Columns with names like 'Column1' containing what appear to be names are actually officer identifiers or duty codes, not personal names. There are no emails, phone numbers, DOBs, addresses, SSNs, or other personal identifiers in any column.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The data appears to be operational logs from the Fulton Police Department, containing unstructured entries such as shift details, officer names, equipment assignments, and timestamps. There are no consistent columns to map to PII fields. The file contains names like 'Hanks', 'Kaufman', 'Lanning', and other operational details, but they are embedded in free-form text rather than in a structured tabular format.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and assignment data for Fulton Police Department officers. All columns represent internal operational codes, shift patterns, equipment assignments, and duty statuses. No PII fields are present — names like 'Curtis' appear to be officer identifiers or placeholder names, not actual personal names. Numeric codes and vehicle/equipment designations are internal tracking numbers, not addresses or phone numbers. No emails, DOBs, SSNs, or other personal identifiers are present.

File structure

Notes: This is unstructured text data with no consistent column structure. The file appears to be a series of free-form notes or reports with varying content per line. There are no identifiable PII columns in a structured format. While some names may appear, they are embedded in prose and not in a columnar format, so unstructured processing is appropriate.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an internal operational document from the Fulton Police Department. All columns appear to contain internal operational codes, shift schedules, equipment types, and duty statuses. No personal identifiable information (PII) is present. Columns contain officer names (which could be considered PII), but these are likely officer identifiers rather than personal names, and the context indicates this is operational scheduling data. No email addresses, phone numbers, dates of birth, or other PII fields are detectable.

File structure

Notes: This is a free-form text file containing operational documents from the Fulton Police Department. The data shows unstructured entries with no consistent delimiter or column structure. Values appear to be shift reports, officer names, equipment listings, and timestamps rather than structured PII fields. While some names like 'Chernesky' and 'R. Sweeting' appear, they are embedded within prose lines without columnar separation, meeting unstructured criteria.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational scheduling data (names of personnel, shift times, equipment assignments, duty types). No PII fields are present. Names in Column1 appear to be officer names but are not linked to personal identifiers or contact info; they are used internally for shift scheduling. All other columns are shift codes, equipment types, duty classifications, and status flags — none constitute PII under the defined field types.

File structure

Notes: This is a free-form text file containing unstructured operational logs and shift reports from the Fulton Police Department. There are no consistent columnar structures or delimiters. The content appears to be narrative entries with embedded names, operational codes, and timestamps, but lacks a tabular format suitable for columnar mapping. No PII columns can be reliably identified due to the unstructured nature of the data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be internal operational identifiers (names of personnel, shift codes, equipment types, assignment categories). No PII fields (email, phone, dob, etc.) are present. Values represent officer names (not full names with first+last), shift timestamps, gear types, and departmental codes — all internal to the Fulton Police Department and non-identifiable outside the organization. No email addresses, phone numbers, dates of birth, or other searchable personal data are visible.

File structure

Notes: This is a free-form text document with no consistent columnar structure. It contains operational reports from the Fulton Police Department with officer names, shift details, and equipment assignments, but lacks a delimited format. The content appears to be prose-style entries rather than structured tabular data.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to be operational/logistical data (names of personnel, shift times, equipment codes, duty types). No PII fields detected. Names in Column1 are likely officer names but are not paired with any identifiers (no badge numbers, emails, etc.). All other columns contain shift codes, equipment types, duty classifications, and status flags — none constitute personal identifiable information under the defined schema. Therefore, no columns map to PII fields.

File structure

Notes: This is an unstructured document containing free-form text with no consistent columnar structure. The data appears to be operational logs from the Fulton Police Department, with entries describing shifts, officer assignments, equipment, and other operational details. There are no identifiable PII columns in a structured format, but the document may contain embedded names or other identifiers in free text which will be processed by unstructured text extraction pipelines.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains only operational and scheduling data for Fulton Police Department personnel. Column 0 appears to hold names, but these are officer names tied to internal rosters rather than general public PII. No columns map to defined PII fields (email, phone, dob, etc.). All columns represent internal operational codes, shift patterns, equipment assignments, and duty statuses. Therefore, no PII columns are identified.

File structure

Notes: This is a free-form text document containing operational records from the Fulton Police Department. There are no consistent column structures or delimiters across rows. The data appears to be a mix of text entries describing shifts, officers, equipment, and other operational details without a fixed tabular format. Therefore, it is classified as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains only internal operational data from the Fulton Police Department (Fulton, NY) — officer assignments, equipment, shift rosters, and status codes. No PII fields are present. All columns are internal identifiers, vehicle/product data, or status flags (e.g., shift times, equipment types, duty status). None map to PII fields.

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample lines show unstructured operational logs from the Fulton Police Department with no repeating column positions. While some lines contain names that could be interpreted as personal data, the format is entirely narrative and lacks tabular structure. This should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment, assignments). No PII fields are present: Column1 values are generic names not tied to individuals, Column2 appears to be ages or codes, Column3 and others are internal identifiers or operational codes. No emails, phones, addresses, DOB, SSN, or other PII are detectable.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The data appears to be internal operational documents from the Fulton Police Department, containing shift reports, officer assignments, and equipment listings. There are no identifiable PII fields in a structured format, but the document may contain officer names and other sensitive operational data in prose form. However, due to the lack of a consistent delimiter and columnar structure across rows, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for the Fulton Police Department. None of the columns map to PII fields. Columns appear to represent officer names (Curtis, Burlingham, etc.), shift times, equipment types, vehicle assignments, duty types, and status codes — but no actual personal identifiers like email, phone, DOB, SSN, or address are present. All columns are either internal operational codes, equipment identifiers, or status flags, and must be skipped per exclusion rules.

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. It contains operational notes and shift reports from the Fulton Police Department. There are no identifiable PII fields in a structured format; values appear to be free-text entries describing shifts, officers, equipment, and assignments. No columns map to PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain internal operational data (names of officers, shift times, equipment codes, duty types). No PII fields (email, phone, dob, etc.) are present. Values represent officer names (Curtis, Burlingham, etc.), shift times (0800-1600), equipment identifiers (Rifle 1, Car 1), duty types (BRVMNT, Sick), and internal codes — none map to any PII categories. Per exclusion rules, internal IDs and operational codes are skipped.

File structure

Notes: This is a free-form text file containing operational documents from the Fulton Police Department. The data does not conform to a structured tabular format with consistent columns and delimiters. The content appears to be descriptive text with embedded values such as officer names, OINs, equipment details, and timestamps, but lacks a uniform columnar structure across rows. Therefore, it is classified as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal police scheduling codes, vehicle assignments, shift times, and operational categories. No PII fields (names, emails, phones, addresses, DOB, SSN, etc.) are present. Columns like 'Column1' with names are officer identifiers used in scheduling context, not personal names requiring protection. All data is operational metadata.

File structure

Notes: This is unstructured free-form text from police operational reports. The data contains no consistent columnar structure — each line is a descriptive report line with varying formats. While there are officer names present (e.g., 'J. Sweeting'), they appear embedded in narrative text rather than as structured columns. The file lacks consistent delimiters, predictable column positions, or header rows. Per rules, unstructured files with embedded PII should be routed through streaming extraction.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This is an operational document with no personal identifiable information (PII). Columns contain shift details, vehicle assignments, equipment, and status codes. No names, addresses, emails, or other PII fields are present.

File structure

Notes: This is a free-form text document with no consistent column structure. The content appears to be internal operational documents from the Fulton Police Department, including shift reports, officer assignments, and equipment details. There are no structured columns containing PII fields.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling data for Fulton Police Department personnel. All columns appear to represent internal operational codes, shift times, equipment types, and duty assignments. There are no columns that map to any PII fields (no names, addresses, contact info, dates of birth, etc.). Column 0 contains names but these appear to be officer code names or aliases used internally rather than actual personal names. All other columns contain shift times, equipment codes, vehicle assignments, duty types, and status flags that are internal operational data with no personal identifying information.

File structure

Notes: This is unstructured free-form text containing shift reports and operational data. No consistent column structure exists — each line is a different format. The file contains no identifiable PII fields like names, emails, or addresses. Values appear to be officer names (Hahn, Chernesky, Murphy), operational codes (OIN), equipment types (Rifle 6, SG 3), timestamps, and duty details, but these are not mappable to standard PII fields (no email, phone, DOB, SSN, etc.). No columns to map.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains internal operational documents from the Fulton Police Department. Columns contain officer names (Curtis, Burlingham, etc.), shift times, equipment codes (Rifle types, vehicle types), department codes, and status flags — all internal scheduling and operational data. No identifiable PII fields (email, phone, DOB, SSN, etc.) are present. Columns are entirely internal identifiers, shift codes, and operational flags. No emails, phone numbers, or address-like values appear. All columns map to skip categories: officer names appear to be aliases/codes, not real names; numeric codes are internal IDs or shift times; equipment and status codes are non-PII operational metadata. Therefore, no PII columns to map.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be internal operational documents from the Fulton Police Department, containing unstructured records of shift reports, officer assignments, and equipment logs. There are no identifiable PII columns in a structured format; any personal data appears embedded within prose lines.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment codes, duty types). No PII fields present. Column0 contains officer names, but these are not personal identifiers in this context (internal roster names). All other columns are shift times, equipment codes, duty types, status flags — none map to PII fields per exclusion rules.

File structure

Notes: This is an unstructured document containing free-form text with no consistent column structure. The file appears to be a series of operational reports from the Fulton Police Department, with no delimited fields or repeating patterns across rows. While it contains officer names and operational details, it lacks the tabular structure required for column mapping. The content should be processed as unstructured text for analysis.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for Fulton Police Department officers. All columns appear to be internal operational codes, shift times, vehicle assignments, and duty statuses. No PII fields (names, emails, addresses, etc.) are present — the 'names' column appears to be officer identifiers or duty codes, not actual personal names. All columns are marked as skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is free-form text with no consistent column structure. The file appears to be operational documents and shift reports from the Fulton Police Department, with embedded text values but no tabular structure. It does not contain any structured PII columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains only operational and scheduling data for Fulton Police Department personnel. Column 0 contains names, but these are officer names and not personal PII for individuals outside the department context. All other columns are operational codes, vehicle assignments, time slots, and status flags. No PII fields (email, phone, dob, etc.) are present.

File structure

Notes: This is a free-form text document with no consistent column structure. The file appears to be a series of operational reports from the Fulton Police Department, with varying content per line. There are no identifiable PII columns in a structured format, and the content does not exhibit a consistent delimiter or header structure. While some values may resemble identifiers (e.g., OIN numbers), they are embedded within free-text lines without a repeating column pattern.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain operational scheduling and equipment data (names of officers, shift times, vehicle assignments, duty types). No PII fields are present. Officer names appear in Column1 but these are operational identifiers for shift rosters, not personal records. All other columns are shift codes, equipment types, duty classifications, and status flags. No emails, phones, addresses, DOB, SSN, or other PII are present.

File structure

Notes: This is an unstructured document containing operational reports from the Fulton Police Department. The data appears to be free-form text with no consistent delimiter or column structure. While there are references to officer names and operational details, the format does not conform to a structured table with identifiable columns for PII mapping. The content includes officer names (e.g., Chernesky, Scribner, Murphy), officer identification numbers (OINs like 40, 66, 58, 10), equipment serial numbers, and shift times, but these are embedded within prose rather than in a tabular format. Therefore, this should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns appear to contain operational police data (names of officers, shift times, equipment types, assignment types, ranks) but no direct PII fields like email, phone, address, DOB, or SSN are present. Officer names are present but are considered operational identifiers for law enforcement personnel rather than general personal PII in this context. All columns map to skip per exclusion rules (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: This is unstructured operational documentation from the Fulton Police Department. The file contains free-form text records with no consistent columnar structure or delimiters. Sample rows show mixed content (officer names, shift times, equipment types, OINs) in free-text format rather than tabular data. While officer names like 'Kaufman' and equipment IDs appear, they are embedded within prose rather than in defined columns. This meets the unstructured opt-out criteria: no consistent delimiter, variable line shapes, and contains personal identifiers within free-form text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns contain internal operational data (officer names, shift times, equipment types, duty codes) but NO identifiable PII. Column0 appears to be officer names but these are likely nicknames/role identifiers rather than true personal names (common last names like 'Curtis', 'Burlingham'). No emails, phones, DOBs, addresses, SSNs, or other PII fields present. Values represent shift scheduling codes, vehicle assignments, and duty types — all internal law enforcement operational metadata.

File structure

Notes: This is a free-form text document with no consistent delimiter. The content appears to be operational reports from the Fulton Police Department, including officer names (Lanning, Hollenbeck, R. Sweeting), OINs (Officer Identification Numbers), equipment details, and timestamps. Since there is no consistent column structure and the data is presented as prose, it should be processed as unstructured text.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: All columns represent internal operational data (officer names, shift times, equipment codes, duty statuses) but contain no identifiable personal information (PII). Column0 appears to be officer names, but these are likely role identifiers or nicknames rather than actual personal names used in official records. No emails, phones, addresses, DOB, SSN, or other PII fields present. All columns map to skip categories: internal identifiers, duty codes, equipment types, status flags.

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows unstructured operational reports with officer names, shift times, equipment IDs, and timestamps, but lacks a consistent CSV-like format. The content appears to be raw log entries or report snippets rather than a structured dataset with columns.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains internal operational documents from the Fulton Police Department. Columns represent scheduling codes, vehicle assignments, shift times, and operational notes. No PII fields are present — all columns are internal codes, vehicle identifiers, shift patterns, and role designations. Names in Column1 appear to be officer surnames but lack first names or other identifiers; these are not sufficient to constitute a fullName PII field per policy. All columns map to skip categories (internal IDs, vehicle/product data, timestamps, internal flags).

File structure

Notes: The file appears to be free-form text (prose) with no consistent columnar structure. It contains operational reports from the Fulton Police Department with no identifiable PII columns. No structured data with repeated fields is present across the sample rows.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment data for the Fulton Police Department. Columns contain officer names, shift times, equipment types (rifles, cars), duty types, and status flags. There are no identifiable PII fields such as email, phone, DOB, SSN, or address. Names appear to be officer surnames or codes, not personal names. All columns fall under operational data or internal codes, therefore no PII columns to map.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The sample shows unstructured operational reports with officer names, OINs, and equipment details but lacks a fixed column layout. While it contains names and internal identifiers, it does not follow a structured tabular format suitable for column mapping.

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: "

Notes: This file contains operational scheduling and equipment assignment data for Fulton Police Department personnel. All columns represent internal operational codes, vehicle assignments, shift times, and duty statuses. No personal identifiable information (PII) is present — names appear to be officer identifiers (not actual names), and numeric codes are internal tracking numbers. Vehicle types (Rifle, Car) and duty codes (BRVMNT, NBA, Sick) are non-PII operational metadata. No email, phone, address, DOB, SSN, or other PII fields are detectable.