Java Database Design Pattern Suggestion

We are working on a Java application which will store user profiles. We have multiple trusted sources (all of them are tables from same oracle database) to create, update user profiles.

We do not have a direct mapping of user profile fields from sources. The field values are derived based on some logic.

Here is a sample of user profile fields in our application

**Application User Profile**

 1. User Login
 2. First Name
 3. Email
 4. Location
 5. Start Date
 6. End Date

Source 1: Database table

 1. User Login
 2. First Name
 3. Last Name
 4. Action Type
 6. Action Date

Source 2: Database table

 1. User Login
 2. Email

Which Java design pattern would you suggest for our scenario? (Assuming we will always read data from the same database, so is DAO not suggestible?)

As explained above, we have multiple sources and the logic to derive user profile fields values from source is different from each source and we don't have all fields in all sources.

Thank you,
Sash