Closed sbenthall closed 6 years ago
I'd prefer to leave this off for 2.x because much of the functionality overlaps with the group and portals concepts, and I think it needs to be revisited, also there is no real UI for this just yet.
On Mon, Jun 4, 2012 at 10:31 AM, Sebastian Benthall reply@reply.github.com wrote:
http://github.com/GeoNode/geonode/wiki/GNIP-13---Collections
It is proposed to add new functionality to GeoNode that allows Data Layers and Maps to be grouped together into 'Collections' that have a their own pages in GeoNode and some metadata.
In discussion, dwins has suggested this could be a 1.2 feature but that depends on additional constraints.
Reply to this email directly or view it on GitHub: https://github.com/GeoNode/geonode/issues/258
Clearing the 2x. milestone
@jj0hns0n Can you add more info about portals to this one?
We need someone to create a clean pull request from the following branch: https://github.com/jj0hns0n/geonode/blob/contrib-refactor/
I am indifferent with this as we may not need it. So I would give precedence to other GNIPs. In case we will get a PR though, it will be more than welcome :)
@ingenieroariel Link to the branch is broken ...
@jj0hns0n There is no documentation (or issues?) existing for Portals (one dead wiki page: https://github.com/GeoNode/geonode/wiki/Gnip-42---geonode-portals ). Not sure what the overlap is unless more information is provided?
Quick update on the links: https://github.com/GeoNode/geonode/wiki/GNIP-13---Portals---Collections and code is part of this branch along with other stuff: https://github.com/jj0hns0n/geonode/tree/contrib-refactor
Punting to 2.5 ... I would like to merge the contrib module I have in my contrib_refactor branch https://github.com/jj0hns0n/geonode/tree/contrib-refactor/geonode/contrib/portals
Related GNIP was proposed in Geonode 2015 Summit User Survey. Seems the underlying purpose is to provide a project-level categorization of all content unique to whatever project. Might be worth thinking about this differently; that instead of 'creating' portals to silo content that instead add the functionality to geonode_projects with a simple django app (controlled only in admin to add/manage content tags) to apply a high-level category or tag that acts as an appended/additional search filter (foreign key table) to resourcebase. The only thing this would do is tie into the header as pull down menu options under Layers/Maps/Documents which would globally filter search results when rendered to view. Agree on punting to 2.5+
@simod we should be able to do the minimum to get the UI up for this using the new collections work you did recently?
@simod what is the status of the collections work now? I think it should be possible to merge it right?
http://github.com/GeoNode/geonode/wiki/GNIP-13---Collections
In discussion, dwins has suggested this could be a 1.2 feature but that depends on additional constraints.