I must admit I like Jody's best, because the other two seem to repeat existing views (project, layers).
The purpose of the catalog, as I understood it, was to show possible available data sources, not data already loaded into projects or layers (for which the project and layers views already exist). So the catalog can and should also show things that are not loaded into any project. As a consequence, it should not be limited to data in projects, and not differentiate between data in a project or not. Also the concept of a layer is that a datasource is configured in a project. You can make two layers of the same data source and style them differently, but they would still be the same single data source in the catalog. So the catalog should not contain projects or layers, only data sources (and classifications of data sources, as Jody's suggestion indicates). On Sat, Jun 4, 2011 at 9:15 PM, Mifan Careem <[email protected]> wrote: > Hi All, > > I am in the process of attempting to figure out the best possible > combinations to use for Catalog View Browse project. As you might be aware > of, the idea is to use best practices from Eclipse and the Java Browsing > Perspective to provide a better view experience to the user [1]. > > The current catalog view shows all the layers loaded which can be quite > hard to browse when the number of layers increase. I'd love to hear your > thoughts on the following grouping ideas for a better catalog view. This is > available on wiki with screens at [2] > > Version 1: > Projects -> Data Sources/Type/Service -> Layers > Projects would contain the list of projects loaded in the workspace > Data Sources would contain the different data sources (ArcSDE, Files, > Mapserver) under the project > Layers would list the layers under the project's particular Data Source > (An image is available in [2] named Version 1, under the June 10 Weekly > Report) > > Version 2: > Projects -> Data Sources/Type/Service -> Categories -> Layers > Projects would contain the list of projects loaded in the workspace > Data Sources would contain the different data sources (ArcSDE, Files, > Mapserver) under the project > Category would be a logical grouping of the layers, maybe based on an > ontology or some standards > Layers would list the layers under the project's particular Data Source and > categorization > (An image is available in [2] named Version 2, under the June 10 Weekly > Report) > > Version 3: > Services -> Layer -> Type > This is from Judy's original proposal. > Services would be a list of services that are loaded > Layers would be the layers > Types would be the types of layers > (An image is available in [2] named Version 3, under the June 10 Weekly > Report) > > I'd assume that the combinations can be perspectives with individual views? > > I'd like to see what the community thinks of the above - please suggest any > new groupings as well that I might have left out. > > [1] > http://udig.refractions.net/confluence/display/UDIG/GSoC+2011+-+Catalog+Browse+View > [2] > http://udig.refractions.net/confluence/display/UDIG/GSoC+2011+-+Catalog+View+Reports > > Cheers > > Mifan Careem > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
