GeoServer
  1. GeoServer
  2. GEOS-5325

Add title and abstract to LayerGroupInfo

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.4, 2.2
    • Fix Version/s: 2.2.3
    • Component/s: WMS
    • Labels:
      None
    • Number of attachments :
      0

      Description

      First step towards increasing the amount of metadata a layer group can expose (hopefully in the future we'll reach parity with normal layers with keywords and other stuff, but that will be another ticket)

        Activity

        Hide
        Justin Deoliveira added a comment -

        I think we have talked about this before but would it make sense to try and abstract out a base class for LayerInfo and LayerGroupInfo?

        Show
        Justin Deoliveira added a comment - I think we have talked about this before but would it make sense to try and abstract out a base class for LayerInfo and LayerGroupInfo?
        Hide
        Andrea Aime added a comment -

        Justin, the issue I see is that neither title nor abstract are part of the layer model, they are coming from the resource instead (and so are other things like keywords, metadata links). So factoring out a common base class does not seem related to this issue, isn't it?

        Show
        Andrea Aime added a comment - Justin, the issue I see is that neither title nor abstract are part of the layer model, they are coming from the resource instead (and so are other things like keywords, metadata links). So factoring out a common base class does not seem related to this issue, isn't it?
        Hide
        Justin Deoliveira added a comment -

        Right... but the plan is to eventually move that sort of metadata back to LayerInfo, or at least I think it would make sense to do so. So yeah, let's table this until that time (sharing base class), and then we can look at refactoring the model.

        Show
        Justin Deoliveira added a comment - Right... but the plan is to eventually move that sort of metadata back to LayerInfo, or at least I think it would make sense to do so. So yeah, let's table this until that time (sharing base class), and then we can look at refactoring the model.
        Hide
        Andrea Aime added a comment -

        Switching all issues that have been in "resolved" state for more than one month without further comments to "closed" status

        Show
        Andrea Aime added a comment - Switching all issues that have been in "resolved" state for more than one month without further comments to "closed" status

          People

          • Assignee:
            Andrea Aime
            Reporter:
            Andrea Aime
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: