Skip to content
Novus Examples
csv193 B

Pine Assembly Workshop — Generic primary records CSV

Generic primary records CSV for Pine Assembly Workshop. 6 generic records with stable primary keys. Map the documented fields before importing into another platform.

Preview, first 8 linescsv
part_id,description,unit_cost,opening,reorder_point
DESK,Desktop kit,40,20,8
BASE,Base assembly,15,30,10
TOP,Top assembly,20,25,10
LEG,Leg,3,100,24
PANEL,Panel,12,50,12
SCREW,Screw,0.1,500,100

Specifications

Kit
inventory-manufacturing
Industry
manufacturing
Schema Version
1
Synthetic
true
As Of
2026-09-08
Rows
6
Columns
5
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Use generic primary records csv in the Pine Assembly Workshop bill-of-materials, stock-movements, reorder-planning, procurement, production-planning, shipments, delivery-exceptions workflow.
Expected result
6 generic records with stable primary keys. Map the documented fields before importing into another platform.

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

“Pine Assembly Workshop — Generic primary records CSV” 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: 6 rows · 5 columns · 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("primary-records.csv")
print(df.head())
print(df.dtypes)

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