portaljs-migrate

# PortalJS — Migrate ## Overview Harvest datasets from an external open-data platform into a PortalJS portal, or push them into a CKAN instance. Every source reads into one canonical shape — `{ slug, namespace, name, description, resources[] }` — then writes to the target from that shape, so adding a source covers every target automatically. Supported sources: CKAN, a DCAT-US `/data.json` catalog (DKAN, ArcGIS Hub, data.gov), a DCAT / DCAT-AP RDF feed, Socrata, OpenDataSoft, or an ArcGIS FeatureServer/MapServer. Supported targets: a static PortalJS catalog (`datasets.json`, resources linked by URL or downloaded into Cloudflare R2) or a CKAN instance over its write API. This is the copy-into-the-portal path, the inverse of `/portaljs-connect-ckan` (which reads the source live at build time): a one-time, re-runnable snapshot so the portal stands alone and needs no backend. ## Prerequisites - An existing PortalJS portal for the static target: `datasets.json`, `package.json`, and `pages/[owner]/[slug].tsx` must exist (the `portaljs-catalog` template). - Node 18+ and npm, with portal dependencies installed (`npm install`). - Network access to the source platform's API or feed URL. - For a CKAN target: a write API key in `CKAN_API_KEY` — never hardcoded. - For `download` copy mode: `git-lfs` and a PortalJS Arc account (or a self-hosted Giftless endpoint) to push resource files to R2. - For `dcat-rdf` sources: `lib/metadata/dcat-harvest.ts` and `dcat-profiles.ts` (copy...