Skip to content
Novus Examples
csv308 B

Cobalt Operations Team: Leave request register

Leave request register for Cobalt Operations Team. 4 requests of 8 hours each, all for dates after the pay period. 2 are approved and count against the balance; 2 are pending and do not. counts_against_balance is derived from status and never disagrees with it.

csv

text/csv

308 B
Document Set
payroll
Industry
people-operations
Source Kit
people-operations
Synthetic
true
As Of
2026-09-08
Rows
4

Binary csv: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
payroll
Industry
people-operations
Source Kit
people-operations
Synthetic
true
As Of
2026-09-08
Rows
4
Approved
2
Pending
2
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Join the requests to the leave balances and check which ones moved a balance.
Expected result
The 2 approved requests total 16 hours and appear in the approved_future_hours column of leave-balances.csv; the 2 pending requests total 16 hours and appear only in pending_request_hours. No request falls inside the pay period, so none of them affects the payroll register.

What is a .csv file?

CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.

How to use this file

Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.

How to use this file for testing

“Cobalt Operations Team: Leave request register” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 4 rows · UTF-8. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import pandas as pd

df = pd.read_csv("leave-requests.csv")
print(df.head())
print(df.dtypes)

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.