Merged rock-loader: the loader library builds for both net10.0 and net472 so Rock can use it, loads can choose their parts, a fresh-database guard refuses a non-new install, the hosted package index and dataset catalog are readable, and the NuGet package is SparkDevNetwork.Rock.SampleData.Loader 0.1.0-alpha.9 (decisions 120 to 126). All three packages pass verify on Rock 21.0.2

Author: jonedmiston

.gitignore

@@ -15,3 +15,6 @@ node_modules/
 
 # The public site build (site/build.js writes it)
 /site/dist/
+
+# The loader NuGet package dotnet pack writes
+/artifacts/

Directory.Build.props

@@ -1,6 +1,6 @@
 <Project>
 
-  <!-- Settings shared by the builder, the loader library, and the loader CLI. -->
+  <!-- Settings shared by every project. The loader library and its compatibility check also build for net472. -->
   <PropertyGroup>
     <TargetFramework>net10.0</TargetFramework>
     <Nullable>disable</Nullable>
@@ -19,6 +19,15 @@
     <NuGetAuditSuppress Include="https://github.com/advisories/GHSA-j9gm-c75j-xc9q" />
     <NuGetAuditSuppress Include="https://github.com/advisories/GHSA-jjfr-hcj7-qf5w" />
     <NuGetAuditSuppress Include="https://github.com/advisories/GHSA-wmxv-xphr-5c9g" />
+
+    <!--
+      On .NET Framework, the loader uses Rock's Microsoft.Data.SqlClient 6.1.4, which brings
+      System.Security.Cryptography.Pkcs 8.0.1, the version Rock ships. A newer one would put a
+      second version into RockWeb/bin. The loader never reads certificates or signed data itself.
+      The .NET 10 build pins a fixed version. Remove these once Rock moves to a fixed version.
+    -->
+    <NuGetAuditSuppress Include="https://github.com/advisories/GHSA-2fmv-rv2c-59x7" />
+    <NuGetAuditSuppress Include="https://github.com/advisories/GHSA-846f-f764-76mx" />
   </ItemGroup>
 
 </Project>

README.md

@@ -139,7 +139,7 @@ and push. Ask me before anything that removes or rewrites history.
 | [photos/](photos/README.md) | The photo rules, the manifest, and the delivered Cast and pool photos. |
 | [graphics/](graphics/README.md) | Reusable church initiative and campaign artwork, beginning with Starting Point. |
 | [builder/](builder/README.md) | The .NET tool that turns this repository into one dataset package per dataset. |
-| [loader/](loader/README.md), `loader-cli/` | The loader library that installs a package into a Rock database, and its command line for developers and test harnesses. |
+| [loader/](loader/README.md), `loader-cli/`, `loader-compat-check/` | The loader library that installs a package into a Rock database (for .NET 10 and for Rock's .NET Framework, as the `SparkDevNetwork.Rock.SampleData.Loader` NuGet package), its command line for developers and test harnesses, and the check that both builds compute the same keys. |
 | [validation/](validation/README.md) | Tolerances and the script that grades generated data, plus the invariants, contract, and standards check the verify tool uses. |
 | [verify/](verify/README.md) | The tool that proves each package works on one exact Rock and writes its receipt. Publishing needs a passing receipt. |
 | [datasets/](datasets/README.md) | One manifest per dataset, with its settings. |

builder/PackageWriter.cs

@@ -52,6 +52,15 @@ public static (string Path, PackageManifest Manifest) Write( string root, string
             var source = new SampleDataSource( repository );
             var datasetManifest = source.ReadDataset( dataset )
                 ?? throw new InvalidOperationException( $"There is no datasets/{dataset}.json." );
+
+            // Rock's installer shows this card, so a package is never built from a manifest without one.
+            var card = SampleDataDatasets.FromManifest( datasetManifest, $"datasets/{dataset}.json" );
+            var campusCount = source.Campuses.Campuses.Count( c => c.Datasets.Contains( dataset ) );
+            if ( card.Key != dataset || card.Campuses != campusCount )
+            {
+                throw new InvalidDataException( $"datasets/{dataset}.json says key {card.Key} and {card.Campuses} campuses, but it is {dataset}, which configuration/campuses.json gives {campusCount} campuses." );
+            }
+
             var files = new SortedDictionary<string, byte[]>( StringComparer.Ordinal );
 
             void AddFile( string path ) => files[path] = Normalize( path, repository.ReadBytes( path ) );

builder/README.md

@@ -31,7 +31,7 @@ A package is a zip of data, never SQL (decision 41). Files keep their paths from
 | `package.json` | The format version, the dataset, the source commit, the one Rock it is for (decision 52), and the SHA-256 of every other file. |
 | `configuration/*.json` | The church setup, unchanged. |
 | `cast/households/*.json`, `cast/groups/*.json` | The Cast and its small group plans, unchanged. |
-| `datasets/{key}.json` | The dataset's settings. |
+| `datasets/{key}.json` | The dataset's settings and its [card](../datasets/README.md#the-dataset-card). |
 | `profile.json` | The calibration profile, already resolved from its sources, so a load never blends sources itself. |
 | `addresses/pool.json` | The address pool for the dataset's campuses only. Each campus's list is unchanged, so generated households get the same addresses. |
 | `photos/manifest.json`, `photos/cast/`, `photos/pool/` | The Cast photos, plus the pool when the dataset gives generated households faces (Core 3). |
@@ -40,7 +40,7 @@ A package is a zip of data, never SQL (decision 41). Files keep their paths from
 
 No timeline is stored: the loader generates every gift, attendance, and alert for the install day. Text files use LF line endings, and every zip entry has the same fixed time, so packing the same commit twice gives byte-identical packages.
 
-Before writing a package, the builder opens it the way the loader does and reads every file a load reads, so a package that would fail to load is never written.
+Before writing a package, the builder opens it the way the loader does and reads every file a load reads, so a package that would fail to load is never written. It also refuses a manifest without its full dataset card.
 
 ## Other commands
 

builder/package-readme.md

@@ -52,7 +52,7 @@ The loader library (`RockSampleData.Loader`) and its command line both install p
 rock-sample-data-load --package {{dataset}}.zip --connection "<connection string>" [--anchor yyyy-MM-dd] [--seed text]
 ```
 
-Before it writes anything, the loader checks the format version, every file's SHA-256, and that the database is Rock {{rockVersion}}. The load runs in one transaction, so a failure leaves nothing behind. Every row it writes carries `ForeignKey = SampleData:{{dataset}}`.
+Before it writes anything, the loader checks the format version, every file's SHA-256, that the database has no people beyond a new Rock install, and that it is Rock {{rockVersion}}. The load runs in one transaction, so a failure leaves nothing behind. Every row it writes carries `ForeignKey = SampleData:{{dataset}}`.
 
 ## More
 

datasets/README.md

@@ -6,7 +6,7 @@ One manifest per dataset: [core-1.json](core-1.json), [core-3.json](core-3.json)
 |---|---|---|---|---|
 | Core 1 | Cast | 1 | Every Cast person | Every check |
 | Core 3 | Cast plus 75 companion households each at Peoria and Gilbert | 3 | Cast, plus about half of companions | Every check |
-| Full 7 | Cast plus Crowd (about 25,000) | 7 | Cast only | Last 12 months |
+| Full 7 | Cast. The manifest lists no generated households yet, so the Crowd loads only with the CLI's `--crowd` | 7 | Cast only | Last 12 months |
 
 ## Manifest settings
 
@@ -19,3 +19,18 @@ One manifest per dataset: [core-1.json](core-1.json), [core-3.json](core-3.json)
 | `checkImages.months` | Months of check gifts, counting back from the anchor date, that get scanned check images. 0 means every check. Used only when the builder runs with `--check-images`; `--check-image-months` overrides it. |
 
 The manifest grows as the builder reads more settings from it. Campuses are listed per dataset in `../configuration/campuses.json`.
+
+## The dataset card
+
+Rock's installer shows a card for each dataset, so a church admin can choose one (decision 124). The loader embeds these fields and serves them as `SampleDataDatasets` (see the [loader README](../loader/README.md#the-dataset-catalog)). Every field is required, and the builder refuses a manifest that is missing one.
+
+| Field | Meaning |
+|---|---|
+| `summary` | One or two plain sentences: who is in the dataset. |
+| `bestFor` | One plain sentence: what the dataset is best for. |
+| `highlights` | Two to four short phrases. |
+| `people`, `households` | People and family households (businesses included) a load adds, measured from a real load at the default seed and 3 years of history. Verify fails a load more than 2% away from either. |
+| `campuses` | The dataset's campuses. Must match `../configuration/campuses.json`. |
+| `typicalInstallSeconds` | The median of three measured loads of every part, check images included, in whole seconds. |
+
+Write the text for a church admin choosing what to install. Follow the [content standards](../docs/content-standards.md) and the writing rules in [AGENTS.md](../AGENTS.md): plain, short sentences and no em dashes. Leave out numbers the number fields already give, so the text never goes stale.

datasets/core-1.json

@@ -2,6 +2,18 @@
   "$comment": "Dataset manifest. Grows as the builder reads more settings from it. Command-line options override these values.",
   "key": "core-1",
   "name": "Core 1",
+  "summary": "The Cast: hand-designed households at one campus, each with its own story. The same families are in every dataset.",
+  "bestFor": "Automated tests, training, and everyday development.",
+  "highlights": [
+    "Families you can name in tests and help articles",
+    "Profile photos for nearly everyone",
+    "Three years of attendance, giving, groups, and serving",
+    "Scanned images of every check gift"
+  ],
+  "people": 185,
+  "households": 87,
+  "campuses": 1,
+  "typicalInstallSeconds": 10,
   "checkImages": {
     "$comment": "Every check in the Cast gets images.",
     "months": 0

datasets/core-3.json

@@ -2,6 +2,17 @@
   "$comment": "Dataset manifest. Grows as the builder reads more settings from it. Command-line options override these values.",
   "key": "core-3",
   "name": "Core 3",
+  "summary": "The Cast at the main campus, plus generated households at two more campuses. About half of the new households have photos.",
+  "bestFor": "Building and trying campus features, such as campus filters, reports, and check-in.",
+  "highlights": [
+    "Three campuses, each with its own people",
+    "The full Cast at the main campus",
+    "Scanned images of every check gift"
+  ],
+  "people": 405,
+  "households": 241,
+  "campuses": 3,
+  "typicalInstallSeconds": 12,
   "checkImages": {
     "$comment": "Every check gets images; Core 3 is still small.",
     "months": 0

datasets/full-7.json

@@ -2,6 +2,17 @@
   "$comment": "Dataset manifest. Grows as the builder reads more settings from it. Command-line options override these values.",
   "key": "full-7",
   "name": "Full 7",
+  "summary": "The Cast at the main campus, with all seven campuses set up. For now, the other six campuses have no people.",
+  "bestFor": "Exploring a seven-campus setup, such as campus pickers and service times.",
+  "highlights": [
+    "Seven campuses with their own service times",
+    "The same Cast as Core 1",
+    "Scanned images of the last 12 months of check gifts"
+  ],
+  "people": 185,
+  "households": 87,
+  "campuses": 7,
+  "typicalInstallSeconds": 9,
   "checkImages": {
     "$comment": "Only the last 12 months of checks get images, to keep the database a reasonable size.",
     "months": 12