On updating an existing package in Agreements local KB, update/overwrite existing package metadata

Purpose:

Once a package has been ingested for the first time the package metadata is not then updated by subsequent ingests

User story statement(s):

As a ERM administrator
I want package updates to complete update package metadata
so that the package metadata stored in the local KB is always up to date

Scenarios:

1. Scenario:
   • Given a GOKb harvest
   • When a package in the harvest matches an existing package
   • Then the package metadata should be overwritten by the harvested package metadata
2. Scenario:
   • Given a package upload via JSON
   • When the package uploaded matches an existing package
   • Then  the package metadata should be overwritten by the uploaded package metadata
3. Scenario:
   • Given a package upload via KBART
   • When the package uploaded matches an existing package
   • Then  the package metadata should be overwritten by the uploaded package metadata (based on the form filled out for KBART package upload)

Additional information

In all of the above scenarios, the packages are matched using a combination of the package reference and package source. The package metadata should be overwritten with the information available at the time of the harvest/import as follows

• source -> by definition stays the same, do not overwrite
• reference -> by definition stays the same, do not overwrite
• sourceDataCreated -> never updated after first creation, do not overwrite
• PackageContentItem -> updated by title/PCI updates separately - do not change how this is done
• sourceDataUpdated -> updated
• lifecycleStatus -> updated
• availabilityScope -> updated
• contentTypes -> remove all existing contentTypes and replace with ones in new package metadata
• alternateResourcenames -> remove all existing alternative names and replace with ones in new package metadata
• vendor -> updated