Merge pull request #1259 from PhilanthropyDataCommons/756-create-work…

…er-to-sync-basefields

Create worker to sync basefields

README.md

@@ -180,7 +180,11 @@ Migrations should be named according to the following pattern: `####-{action}-{t
 
 For example: `0001-create-users` or `0001-modify-users`
 
-In `/src/databases/seeds` there is seed or starter data. The contents can be run manually to help developers get data in their databases. The scripts are not referenced by the software and are included for convenience. The migrations must run prior to using seed scripts.
+The `CopyBaseFieldsTask` worker is designed to copy basefields from a remote to a local instance of the pdc service. An administrative user looking to seed their database can make a POST request to the `/tasks/baseFieldsCopy` route, specifying the remote url in the body of the form:
+
+```json
+{ "synchronizationUrl": "https://remote.pdc.instance" }
+```
 
 #### Linting
 

package.json

@@ -53,6 +53,7 @@
 		"@types/jest": "^28.1.2",
 		"@types/language-tags": "^1.0.4",
 		"@types/node": "^22.10.5",
+		"@types/node-fetch": "^2.6.12",
 		"@types/pg": "^8.11.10",
 		"@types/supertest": "^6.0.2",
 		"@types/swagger-ui-express": "^4.1.7",
@@ -95,6 +96,7 @@
 		"language-tags": "^1.0.9",
 		"monocle-ts": "^2.3.13",
 		"newtype-ts": "^0.3.5",
+		"node-fetch": "^2.7.0",
 		"phone": "^3.1.57",
 		"pino": "^9.6.0",
 		"pino-http": "^10.3.0",