REC_SRC attribute in hub , link or satelites

We have business entities where sourcename is the part of composite keys , since we get data from 3 or 4 different sources for same entity . So can we map sourcename to REC_SRC ? Or have 2 different columns sourcename & REC_SRC in hub,link & sat but these columns will have same information .

Is this a source system decision of the source system you are loading? Or is it a decision made in your Data Vault solution? If the latter, then this could be an implementation of a BKCC or Collsion Key and therefore this should generally not be changed. If the former, then you should load as-is and map that key to the Record source of the raw vault tables as you have described.

Very skeptical here — source name should never be a part of the business key else you are building an anti-pattern to a true data vault