THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Figure 2: Collecting information about people and teams | UserIdentity provides a structure for storing the security authentication information about a person. Initially we have a simple string for the userId - but this could be extended to include more sophisticated identification information. An ActorProfile describes the actual person, or possibly team if group userIds are being used, that is working either with the data assets or with the metadata directly. The profile is a record to add additional information about the person or engine that is making the requests. They may have more than one UserIdentity. Actors are associated with the new metadata that they create and comment on during crowd-sourcing processes. Teams define groups of actors working together. via their user identities. More information about the person behind the user identity is available through the ActorProfile. This separation is maintained because the user identity is the only information available on calls to the metadata repository. The ActorProfile is used to aggregate the activity of the individual or team (or engine - see Area 2 model). This includes crowdsourcing and project participation. Open metadata supports KarmaPoints. These are awarded for participation in the collaboration around open metadataA person is an individual. |
Collections
Collections provide a general mechanism for grouping resources together. They are typically associated with Actors, Projects (see 0130 below) or Communities (0140 below).
Figure 3: Collections of resources | The classifications associated with Collection allows it to be specialized for particular uses. |
Projects
Projects are used to organize a specific activity. The project is used to control the use of resources and associated costs so they are used appropriately in order to successful achieve the project's goals. The project definition is shown in figure 4.
...