In order to support testing changes to the local KB data loading / title matching / PTI and PCI management a testing environment should be set up. This will need:
- mod-agreements built from a branch which is dedicated to change
- set to harvest from GOKb test instance
- Ideally frontend apps ui-agreements and ui-local-kb-admin, although it may be possible to test with only backend apps in place
The UI (or mod-agreements API if no UI provided) will need to be accessible to key testers (Owen, Felix, Benjamin)
The setup should be completely wiped and re-established every night.
A second environment running the current mod-agreements code (either from master, or from the most recent release) will be required in order compare any changes to the process between the current setup and the new setup. However, folio-snapshot or folio-testing could be used for this purpose, so a dedicated environment may not be needed (unless preferred by the developers)