THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
<== Back to Area 0 - Extensions to the base model | Forward to Area 2 - Assets and Connectors ==> | Models for referenced objects: Referenceable
Area 1 covers the people and teams using the data resource along with the organization structure that organize their work. The packages are show in figure 1.
Figure 1: Packages for area 1 |
Actors
Most metadata repositories are run in a secure mode requiring incoming requests to include the requestor’s security credentials. Therefore we have an identifier for each unique logged on security identity (aka userId). This identity is recorded with specific entities and relationships when they are created or updated. The userId for a server is also captured in the metadata model (see 0040 Servers in Area 0) so it is possible to correlate the actions of a data processing server with changes to the metadata.
Figure 2 captures how people and teams are represented.
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. A 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 |
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.
Figure 4: Projects and the people and resources they manage | Projects organize resources to build new capability or improve existing capability. Related projects can be organized into campaigns Notice that the project acts as an anchor for collections of resources that the project is using. Since it is a Referenceable, it can have links to external URLs, such as the project home page, project plan or APIs as well as images (see 0015 Linked Media Types in Area 0). |
Communities
Communities are groups of people related by a common interest or skill. People tend to stay in communities for the long term, whilst they are are associated with projects just for the lifetime of the project and then they move on to another. Figure 5 shows the community model linked to the people who are members and the resources that they use.
Figure 5: Communities Model |
Feedback
An important principle of good metadata it to be continually capturing the experience of subject matter experts. Figure 6 shows the feedback model that captures comments and ratings from subject matter experts.
Figure 6: Feedback through comments and ratings | Comments and ratings are a key mechanism for providing feedback on the metadata definitions by any user.
Note that comments can be tagged, rated and commented on. |
Notes
Notes provide additional information about a referenceable object. They are used by resource owners and stewards to document the current status of their resources. Engines that are performing processing on the resources may also write notes to the note log. Figure 7 shows the notes in a note log. The note log can be attached to any referenceable metadata object.
Figure 7: Notes and note logs | A referenceable object can have many notes linked off of it. Notes are used by the people with edit access to the referenceable object to provide information about its content, proposed changes and other useful information. Notes are also used by engines that are working on the related assets to add an informal audit trail of activity around the object. |
