You say you did but i cannot find any suggestion from you. 
Can you say how many satellites/links/hubs you need in a Data Vault model to import the data from my example dataset?
the example data:
dataset day1:
partitcipant, totalnumberofsteps
Jenny, 2000
Olof, 4000
Still havenât found that driver key have you?
Good luck
Hello Patrick!
Nice that you wish me good luck!
If you are referring to my example the driver key is the participant.â
Now, how would you model my example?
the example data:
dataset day1:
partitcipant, totalnumberofsteps
Jenny, 2000
Olof, 4000
right⌠yup you need to read up on what a driver key is and how to properly construct effectivity satellites â which was my point all along.
There is plenty of literature to help you ,
If you want modelling scenarios, load code, query code, look no further than
Hello again Patrick!
With all do respect, you are referring to links that you wrote yourself. 
I joined this forum to discuss Data Vault issues and my goal here is to help others, gain insight from other users and hopefully be a part of evolving the Data vault community. I have lots of ideas on how Data vault can be more powerful/effective when it comes to practical implementations and easier for beginners to grasp. I wish I could be discussing issues with you around Data Vault. I am ready to be right, to be wrong and to be respectful to others that has different opinion then what I have.
I have based my knowledge on Data vault from Dan Linstedts various articles online and his book âBuilding a scalableâŚâ. Did my practitioners training with Michael Olschimke (great guy btw).
Below is a link to Dan Linstedt Modeling specification v 2.0.2.
Page 6:
"1.3.2 Effectivity Satellite
An Effectivity Satellite is a standard Satellite housing temporal views of a Link or Hub record. In
other words, one or more sets of begin and end dates that may dictate the effectivity of the
relationship (Link record), or of the business key (Hub Record).
Effectivity Satellites may also house deleted dates, or other metadata markers that describe the
parent records within or across timelines. NOTE: Physical updates are never allowed on this
data. See the Data Vault Implementation Standards for more information.
"
So, I have based my knowledge of Dans paper. When I am refering to an Effectivity satellite, the EFS can be connected to a link or a hub.
I have deployed Effective satellites into Data Vault Data warehouses for a long time. Without the use of effective satellites (or NHL, RTS), your Data Vault system wonât be able to track if keys or key combinations gets altered or deleted over time. Without the knowledge of when a key or a key combination is effective, your data vault will not be able to represent historic data as it was when data got delivered from the source. Your are losing the bitemporality in your Data vault and audit of the data over time wonât be possible.
Now, how would you model my example?
the example data:
dataset day1:
partitcipant, totalnumberofsteps
Jenny, 2000
Olof, 4000
I think if you followed EFS carefully, the training, standards in the PDF and Dans book do not align on the definition of EFS. Only the pdf states an EFS is over a hub and link when the other two state it is only about the relationship
Youâre not helping anyone by not knowing what a driver key is.
Of course I wrote those, because theyâre correct.
As I said before, the preference in order of key manipulation is
I am following Dans definition from the specification, it is a great specification!
You are saying that I am not helping anyone by not knowing what a driver key is, what do mean by that?
I did not ask you for the preference in order of key manipulation. I stated that in my scenario the source could not provide the changes (which I think is the most common scenario).
I give you my definition of the driver key if you model my example, what about that? 
the example data:
dataset day1:
partitcipant, totalnumberofsteps
Jenny, 2000
Olof, 4000
All three are from Dan???
Good luck buddy
I used the specification that i provided, the pdf document. Why wont you provide us with an example of how you would model my example?
Oh! I thought you would have noticed that everyone (including me) have moved on from this topic!
And itâs not âusâ itâs âyouâ, I recommend that for you to learn about Driver Keys and how to properly Define and Build Effectivity Satellites you start with the resources I provided above. Or try âluckâ the other resource you might be interested in.
Regards,
Why wont you provide us with an example of how you would model my example? If you are a Data vault guru, please enlighten us.
The book is the Data Vault Guru, I have never proclaimed myself as a DV Guru.
You can get one and put it on your shelf.
Is having Satellite primary key as hash-key+load_date+applied_date as a general rule which can be applied to all satellite tables?
If done so, any drawback to it?
@saqib do you use the below composite keys for all satellites?
BKs + Load Date + Applied Date (modifyts from source)
I am facing a dilemma whether to add applied date as part of primary key of satellite table.
Adding it looks logical to resolve multisnapshot loads, but would like to check if this approach is an accepted approach among the Data vault practitioners?
Appreciate your comment on this. Thank you
Makes your DV bi-temporal;
I originally called it âRecord Tracking Timestampâ â Dan Linstedt said I should call it âApplied Timestampâ instead
Thanks @patrickcuba for a quick reply.
I understand the usage of applied date column via your blogs (thank you for that )
Apologies to push it again for clarification. just want to make sure i understand it clearly.
In the case where we do use applied time for satellite tables.
primary key for a satellite changes to this :
BKs + Load Date + Applied Date
correct?
Correct! (my response must be at least 20 characters)
shall applied date need to be part of hash key of the satellite too
uuhhhhh⌠think about what you are saying⌠if you add applied date to the hash hash-key whatâs going to happen?