Design Pattern for Data Consolidation

I have to design a software using asp .net core which collects data from various datasources (s. picture below). E.g. DataSource1 and DataSource2 are including product data like attributes. DataSource 3 is including the assets of those products. I thought first of all I will collect the data from each datasource and persists them in own datasource with the defined entity below. I have the advantage later at translating or tranforming the data to use one abstract entity.

My question which pattern should be good for this system? Repository, Pipeline,...?? And what about DI if I use interfaces but should have multiplied instances of datasources?