Use the breadcrumb to navigate backward in the current branch of the
directory path, by clicking on a directory name in the breadcrumb. Note
that you can access the root of the directory path by clicking the Home
icon in the breadcrumb.
Figure 2: The Breadcrumb
If the currently selected entity is a collection, the Content Panel
shows the child entries under that collection. It provides details of each
entry. An entry can be either another collection or a resource.
Name - Click to access the content of this entry
Created Date
Author
Ratings
The link to the Atom feed
Figure 4 : View of Directory Entries
Adding a new Resource
Adding a resource could be done for a collection of resources or for an
individual resource. To add a collection or directory, click on the "Add resource"/"Add collection" link
provided and a page will be presented to fill in the required information.
Optionally, a description can be included for the resource in question.
Note : Adding and and deleting resources within the registry are considered version operations. Therefore, provision is made to rollback or restore a resource to any previous version. Refer Versions for additional information on this topic.
Deleting a Resource
To delete a resource , click on the cylindric icon provided. However, upon
doing so a resource will not be removed from the database but instead marked
as deleted. This provides the opportunity to restore a previously deleted
resource.
If the currently selected entity is a resource, the Content panel
provides a user interface through which you can display, edit and
download the content.
Figure 5 : View of the Content
Using the following screen, WSO2 Governance Registry permissions can be assigned to different roles and individual users. The top half of the permission's screen is used to define user roles and the bottom half for defining role permissions.
Figure 6 : Permissions
To assign permissions to users or roles follow the steps given below:
select user/role from User/Role drop down
choose an action from the 'Action' drop down menu
select permission type. users are able to choose 'Allow' or 'Deny' by selecting appropriate option button.
Click 'Add Permission' to apply selection
Existing permissions can be changed by selecting and clearing the check boxes for required permissions and clicking the "Apply All Permissions" button.
Note: 'User permissions' have higher priority over 'role permissions'. 'Deny' permissions have higher priority over 'allow' priorities. Essentially, this means that permissions assigned to users overrides permissions assigned for a role and that a deny permission always overrides an 'allow' permission assigned to a user.
The right side of the resources page houses 3 additional blocks, namely: Tags, Comments and Versions.
Provides space to enter tags for a given resource. These tags can be used when searching for a resource as key words for search criteria.
Users can enter as many tags as they like provided individual tags are separated by commas and a given tag is not used by the same author to identify the same resource repeatedly.
Resources or collections stored in the Registry can be associated according to the user's requirements. These can either be dependencies or named custom associations.
Each collection or resource that you create and store on the repository has an associated media
type. However, you also have the option to leave this unspecified enforcing the default media type.
There are two main ways in which you can configure media types for resources.
The first method is by means of a one-time configuration which can be done by modifying the
mime.types file found in the server configuration directory. This can be done just
once before the initial start-up of the server. The second method is to configure the media types
via the server administration console.
Managing media types for resources can be done via the server administration console, by editing the
properties of the /system/mime.types/index collection. This collection contains two
resources, collection and custom.ui. To manage media types of
collections and custom user interfaces, you need to edit the properties of these two resources.
Figure 2: The Breadcrumb
Figure 3 : The meta data panel
Figure 4 : View of Directory Entries
Figure 5 : View of the Content
