Event Tags: Flow of Tags into Registration, Impacts and User

In addition to generic tags, there is also a concept of creating a tag for an event, and allow that tag to follow the registration, the impact (outputs), and the user who attended the event. 

For example: 

• Registration Tags: is for a specific registration record, i.e., what types of tags (inherited from an event) do they have.
• Impact Tags: is for a specific impact, i.e., what types of tags (inherited from an event or registration record) do they have. 
• User Tags: is for an individual, i.e., what types of tags (aggregated) do they have.--

--- 
To understand the above better, the following is a scenario:

If I'm John Doe, and I registered to an event with one tag called "Path1", the registration record would have the "Path1" tag associated with it and also the Impact record. Another scenario would be if I'm still John Doe and I registered to another event with one tag called "Path2", for the registration record would have the "Path2" tag associated with it and also the Impact record. 

Given the above John Doe being registered to two events tagged differently, John's User record will have the "User Tags" = "Path1, Path2". 
---