uDIG

Catalog view containing per-project entries concern

Details

  • Type: Wish Wish
  • Status: Analysis Analysis
  • Priority: Trivial Trivial
  • Resolution: Unresolved
  • Affects Version/s: UDIG 0.4, UDIG 1.2.M2
  • Fix Version/s: UDIG 1.4.1
  • Component/s: catalog, metadata and search
  • Labels:
    None

Description

Andrea writes:
Also, I'm not sure about it, but I hope the registry contents are per-project, since different projects may have to work with very different set of files. Some of the registry contents may be general enough to be always there, but as a user I would not be happy to see all of my datastores and shapefiles always there. Just my opinion

Issue Links

duplicates

Wish - General wishlist item UDIG-64 Registry's flat structure concerns

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. UDIG-223 shapefile must be handled differently in catalog

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jody Garnett added a comment -
Duely noted - registry is now called catalog.

I will be sure to add a "Filter" to catalog that limits the shown files to those used by the currently selected project. The other workflow catalog was intended for was that of data discovery.

This is likly to be best met by the search view I am in the middle of writing.

Other filter modes for catalog view that would make senese:
- Services / Resources used by current project
- Services / Resources in use right now
- Services / Resources with available content in the current viewport (ie on screen)

Other suggestions?
Show
Jody Garnett added a comment - Duely noted - registry is now called catalog. I will be sure to add a "Filter" to catalog that limits the shown files to those used by the currently selected project. The other workflow catalog was intended for was that of data discovery. This is likly to be best met by the search view I am in the middle of writing. Other filter modes for catalog view that would make senese: - Services / Resources used by current project - Services / Resources in use right now - Services / Resources with available content in the current viewport (ie on screen) Other suggestions?
Hide
Permalink
Jody Garnett added a comment -
I am taking on this issue, the actuall catalog view will remain a low level description of what services and files the system is connected to.

I would like to create a view with four screens:
- Web - wfs and wms and http or ftp urls organized by server
- Databases - organized by server
- Files - works like regular filesystem except that any file we are connected to would have a special decorator
- Temp - staging area for temporary files generated by GIS opperations

All of these pages represent the same idea (a IService with IGeoResource children) presented in a manner suitable for the subject matter. Files are presented in the filesystem, Temp organized by category provided by generating opperation.

All these nouns have the same IGeoResource opperations available to them such as Export and Save As. Save As being a short hand for an "Export to File" opperation.

These views will be done one at a time, and would be center point of a "Catalog Perspective".
Show
Jody Garnett added a comment - I am taking on this issue, the actuall catalog view will remain a low level description of what services and files the system is connected to. I would like to create a view with four screens: - Web - wfs and wms and http or ftp urls organized by server - Databases - organized by server - Files - works like regular filesystem except that any file we are connected to would have a special decorator - Temp - staging area for temporary files generated by GIS opperations All of these pages represent the same idea (a IService with IGeoResource children) presented in a manner suitable for the subject matter. Files are presented in the filesystem, Temp organized by category provided by generating opperation. All these nouns have the same IGeoResource opperations available to them such as Export and Save As. Save As being a short hand for an "Export to File" opperation. These views will be done one at a time, and would be center point of a "Catalog Perspective".
Hide
Permalink
Jody Garnett added a comment -
Yet another duplication of this bug - it is popular :-)
Show
Jody Garnett added a comment - Yet another duplication of this bug - it is popular :-)
Hide
Permalink
Jody Garnett added a comment -
Note to meet the requirements of this origional bug report we could filter the catalog to only show resources used by the current project (it would lose the functionality to browse all connections in this case).
Show
Jody Garnett added a comment - Note to meet the requirements of this origional bug report we could filter the catalog to only show resources used by the current project (it would lose the functionality to browse all connections in this case).

People

  • Assignee:
    Unassigned
    Reporter:
    Richard Gould
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: