-
Notifications
You must be signed in to change notification settings - Fork 1.1k
GNIP 9 Profile Migration to idios
GeoNode currently implements django-profiles to handle user profiles. The geonode.maps.models.Contact class is used as the AUTH_PROFILE_MODULE. It is proposed to migrate the AUTH_PROFILE_MODULE to a new class that extends from idios.models.ProfileBase and move it to the new geonode.people module.
Eldarion has done the initial work on this feature.
https://github.com/eldarion/geonode/tree/add-idios
https://github.com/eldarion/geonode/tree/profile-migration
Jeffrey Johnson
TBD
For Review and Comment
Idios provides a more flexible and extensible profile module to base GeoNodes profile on than the existing implementation of django-profiles. Users of GeoNode have expressed an interest in customizing the fields captured in the existing Profile module, and this is not currently accomplishable without directly modifying the geonode.maps.models class which makes future upgrades or merges difficult.
It is proposed to add a hard dependency on idios (https://github.com/eldarion/idios) and migrate the existing geonode.maps.models.Contact class to geonode.people.Profile which should extend. from idios.models.ProfileBase
Migrations for existing sites (See GNIP 19) ... work has been already been done to handle for this migration, but it depends on django-south.
Many existing tests use the geonode.maps.models.Layer class which relies heavily on the existing geonode.maps.models.Contact class when handling metadata. Existing tests should pass, and any new tests necessary to maintain or increase coverage should be added.
Do nothing. The current implementation works without issue.
See discussion on the geonode-dev list here.
https://groups.google.com/a/opengeo.org/group/geonode-dev/browse_thread/thread/68700bd5074dd323