HR sample database — MongoDB, embedded (1,963 rows)

Tables that belong to another are folded into it as arrays, so the documents read the way the application uses them. The rest are collections of their own, joined by key as in the flat version.

Load it:
  sh import.sh                    (into mongodb://localhost:27017)
  sh import.sh "<connection string>"

Or one collection at a time: mongoimport --db hr --collection <name> --file <name>.ndjson

Collections:
  addresses — 10 documents
  applications — 10 documents
  attendance — 1,000 documents
  benefits — 8 documents
  candidates — 10 documents
  companies — 1 documents
  contacts — 10 documents
  contracts — 10 documents
  departments — 12 documents
  dependents — 10 documents
  educations — 10 documents
  employees — 10 documents, each with its employee_benefits, its employee_salaries, its employee_skills
  employment_statuses — 4 documents
  equipment — 400 documents, each with its equipment_assignments
  grades — 8 documents
  interviews — 10 documents
  job_openings — 120 documents
  jobs — 30 documents
  leave_allocations — 10 documents
  leave_requests — 10 documents
  leave_types — 6 documents
  locations — 6 documents
  onboarding_tasks — 10 documents
  payrolls — 60 documents
  payslips — 60 documents
  performance_reviews — 10 documents
  review_goals — 12 documents
  salary_components — 6 documents
  skills — 30 documents
  training_enrollments — 10 documents
  trainings — 20 documents

Folded in (no collection of their own):
  employee_benefits — 10 rows, as the "employee_benefits" array on employees (its employee_id is the parent's _id)
  employee_salaries — 10 rows, as the "employee_salaries" array on employees (its employee_id is the parent's _id)
  employee_skills — 10 rows, as the "employee_skills" array on employees (its employee_id is the parent's _id)
  equipment_assignments — 10 rows, as the "equipment_assignments" array on equipment (its equipment_id is the parent's _id)

Types: numeric columns are Decimal128, so totals stay exact; dates and timestamps are
Date values read as UTC (the data has no time zone); times and UUIDs are strings;
JSON columns are embedded objects.

Synthetic data, CC0-1.0, from databasesample.com. The same rows as the SQL and CSV files.
