...
ClientDetailDatabase- contains information about clients involved in vessel registration. We expect the schema of this database to change in the future, once Stakeholder Management Service takes over client management concerns.VesselDetailDatabase- contains detailed information about vessels.VesselRegistryDatabase- contains information about registration of vessels. In essence, it "links" vessel detail records with client detail records.
...
The only change made here was adding OFFICIAL_NUMBER field to the Y001_VESSEL table, since official number is an attribute of a vessel, and never changes once assigned to one.
...
VesselRegistryDatabase
The following changes were made to the database:
Dropped table Y015_REGISTRY_WORKITEM_XREF. Reason: Vessel registration records should not “have knowledge” of work items or requests that have lead to its their creation or modification. This decouples the request management process from vessel registry and allows for applying security, data loss prevention and other polices to these two databases independently.
Added new table Y010_VESSEL_OWNERSHIP, in accordance with the diagrams developed by vincentjoseph.chazhoor (Unlicensed). A couple of deviations here:
Instead of using FK relationship to Y001_VESSEL, which is in another database, we use FK relationship to the Y010_REGISTRY table.
CLIENT_ID column is no longer marked as a FK, as it points to records in a separate database.
Added OFFICIAL_NUMBER field to the Y010_REGISTRY table, as this is how vessel records will be linked to the vessel registry records.
...