Skip to content
Novus Examples
json1.9 KB

Willow Community Fund: Restricted fund report JSON

Restricted fund report JSON for Willow Community Fund. The same 4 funds as restricted-funds-report.csv with the balancing rule stated and the closing balance split by restriction: 1904.75 with donor restrictions and 1200.00 without.

json

application/json

1.9 KB
Document Set
nonprofit
Industry
nonprofit
Source Kit
nonprofit-fundraising
Synthetic
true
As Of
2026-09-08
Funds
4

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

Specifications

Document Set
nonprofit
Industry
nonprofit
Source Kit
nonprofit-fundraising
Synthetic
true
As Of
2026-09-08
Funds
4
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Apply the stated rule to every fund and check the restriction split in the totals.
Expected result
Every fund satisfies the rule and the array sums to the totals object: 6300.00 received, 4395.25 spent and 3104.75 closing. Summing only the funds marked with donor restrictions gives 1904.75, exactly the closingWithDonorRestrictions figure.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“Willow Community Fund: Restricted fund report JSON” 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: 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 json

with open("restricted-funds-report.json") as f:
    data = json.load(f)
print(type(data), len(data))

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