Skip to content

Adagio / SUMARiS model correspondence

The SUMARiS data model is derived from the Adagio core model (SIH-Adagio :: Core Server). The concepts are mostly the same, but some foreign keys changed direction, entities were merged, and id/label attributes were added.

In case of conflict, the entities of the pod (branch develop) are authoritative.

This page lists, in a synthetic way:

  • the differences between the two models (renames, merges, association changes);
  • the concepts that are new in SUMARiS (absent from Adagio);
  • the Adagio concepts still absent from SUMARiS (see the dedicated diagrams).

The detailed mapping of the Adagio tables used by IMAGINE is described in the IMAGINE / SUMARiS mapping page (in French).

Differences between the models

Renamed entities

Adagio SUMARiS
FishingTrip Trip
FishingOperation Operation
CatchBatch Batch
DenormalisedBatchSortingValue DenormalizedBatchSortingValue (with a "z")
UserProfil UserProfile
VesselPhysicalFeatures VesselFeatures
Program2Person ProgramPerson
Program2Department ProgramDepartment
TaxonGroup2TaxonHierarchy TaxonGroupHierarchy
Produce Product
Photo ImageAttachment

Merged or restructured entities

  • SortingBatch no longer exists as a distinct entity: the sorting levels are part of the Batch tree itself;
  • the abstract Adagio Measurement has been split into concrete measurement entities (SurveyMeasurement, LandingMeasurement, GearUseMeasurement, VesselUseMeasurement, BatchSortingMeasurement, BatchQuantificationMeasurement, ...), one per host entity;
  • ObservedFishingTrip, ObservedLanding and ObservedSale are replaced, in SUMARiS, by an observation flag (or an *Origin entity) on Trip, Landing and Sale;
  • Batch attaches directly to an Operation or a Sale as a root batch, instead of being nested under CatchBatch/FishingOperation as in Adagio;
  • GearUseFeatures keeps its link to the operation, and gains an origin (GearUseFeaturesOrigin, qualified by program and acquisition level).

Association changes

  • some foreign keys changed direction (e.g. the program/person and program/department links are carried by ProgramPerson/ProgramDepartment in SUMARiS, by Program2Person/Program2Department in Adagio);
  • referential join tables (Fishery2Gear, Fishery2Metier, SamplingStrata2*, FishingArea2*) were removed or replaced by direct foreign keys.

Concepts new in SUMARiS (absent from Adagio)

  • AI models: AIModel, AIModelType;
  • Extractions: ExtractionProduct, ExtractionProductTable, ExtractionProductColumn, ExtractionProductStrata, ExtractionProductValue, and the RDB output tables (ProductRdbTrip, ProductRdbStation, ProductRdbSpeciesList, ProductRdbSpeciesLength, ProductRdbLanding);
  • Technical platform: Software, SoftwareProperty, File, FileLine, FileStatus, NamedFilter, ProcessingFrequency, ProcessingType, ProcessingStatus, DevicePosition, ImageAttachment;
  • Social: UserEvent, UserInteraction, UserSettings, UserToken;
  • Programs and strategies: ExpertiseArea, Program2Location, AppliedSamplingStrata, SamplingStrataAppliedPeriod, TaxonGroupStrategy, TaxonGroupSamplingStrata;
  • Collected data: PhysicalGear (+ PhysicalGearMeasurement), GearUseFeaturesOrigin, ProductSortingMeasurement, ProductQuantificationMeasurement, ScientificCruise, DenormalizedSpatialItem, VirtualTaxonComponent.

Adagio concepts still absent from SUMARiS

The following Adagio entities have no equivalent in SUMARiS (yet). They are shown in the dedicated diagrams:

  • Crew, sessions and vessel tracking (vessel-crew-sessions.svg): VesselPerson, VesselPersonFeatures, VesselPersonRole, PersonSession, PersonSessionItem, PersonSessionVessel, TempPersonSessionVessel, VesselPositionVMS, VesselCommissioningPeriod, VesselManagePeriod, VesselFleetEvent, PhysicalGearSurvey, AgeReaderQualification;
  • Marketing and auctions (marketing.svg): TakeOver (+ TakeOverMeasurement), Buyer, BuyerType, Seller, SellerType, Transshipment, the sale quality views (QvDressing, QvFreshnessCategory, QvPreservation, QvSizeCategory), AppliedSizeCategory, RightToProduce;
  • Playground and managed data (playground-data.svg): PlaygroundVesselMaster, PlaygroundVesselOwner, PlaygroundFishingTripVesselMaster, PlaygroundFishingEffortZone, PlaygroundRicTaxonGroup, PlaygroundTaxonGroupSampling, ManagedData, ManagedDataType, ManagedDataTransfer, EconomicalSurvey, FishingEffortCalendar, DeclaredDocumentReference.

Other minor Adagio classes without SUMARiS equivalent (e.g. ObservedLocationFeatures, LocationHierarchyException/LocationHierarchyOverride, GearFeaturesControl, MeasurementFile, LinkedItem) are not diagrammed: they are either internal helper tables or candidate concepts for a future SUMARiS version.