Logical Vs Physical Registry Navigation Structures

Hi, I agree that it would be nice to have various perspectives in looking at the registry. Btw, can you explain your requirement in detail? We do provide a tree-like navigation structure to the resources/collections stored in the registry via the administration console. Do you expect to have something in addition to that? Thanks, Senaka

Firstly, I think it would be very nice to have a document that describes 'A typical collection hierarchy' that would fit general organizational structures. I don't think it is difficult to come up with since most organizations at the enterprise level will have typical departments like sales, marketing, purchasing, finance, corporate, IT etc. Of course you would combine or or many of these as the organizations become smaller. From a perspective standpoint I can think of at least 3 different perspective views that a user should be able to see. I'm sure there can be more. 1. Organizational View - a view based on the organizational structure of an organization. 2. Logical View - e.g. from an IT perspective a logical view could show a technical view showing collections for all schemas, web services, JDBC Services, JMS services, Ruby Servcies, Perl Servcies etc. 3. Physical View - physical path view of the collection and resources. From a functional standpoint when you login as a user you should be able to see you default view(meaning that there should be user preferences stored to store their default perspective view) and there should be a link(maybe on top of the resource section) to switch to other perspectives. Hope this helps. THanks

Hi, Well, this can be easily achieved by adding a handler to create this collection structure with the collection having defined media type. And, for anyone navigating this collection structure, we can provide a custom user interface. The collection structure itself can be created through a custom user interface. FYI, if you didn't know, a handler is a way in which you can extend the registry, and a custom user interface is a customized page that appears when you browse resources, which can be configured based on media types. Thanks, Senaka