librelist archives

Re: Home, Map, Data page UI changes coming up

From:

Sebastian Benthall

Date:

2010-07-14 @ 18:06

One thing i forgot to mention:

With the removal of the Featured Map from the home page and the combining of
the "CAPRA Maps" and "Community Maps" tabs into a single view, there is no
longer a use for the 'featured' and 'endorsed' fields on the Map model.

So I think we should remove them.

Possible reasons NOT to remove them: somebody wants to do something with
these properties in a specific custom instance; it's a pain to do a database
migration.

Neither of these reasons seem particularly strong, but I wanted to ask
first.

On Wed, Jul 14, 2010 at 12:44 PM, Sebastian Benthall <seb@opengeo.org>wrote:

> Attached is an image with three wireframes for what will probably be the
> three most-visited pages of the site, the home page, the data tab, and the
> maps tab.  (At some point, we've discussed that it's likely that we will be
> merge the data and maps tabs.  But for that to make sense we would need to
> have a way of unifying map and data search, which we certainly won't do by
> 1.0.)
>
>
> Not everything shown in the wireframes has been thoroughly scoped out, but
> I wanted to call attention to some of the changes proposed:
>
>  * Remove the "Featured Map" from the home page, in favor of more direct
> access to the main functionality of the site (cartography, data search)
>
>  * Allow data search from the home page
>
>  * For these views, there is no content in the sidebar.  However, the main
> content block is still restricted in width as though the sidebar were there.
>
>
>  * The Maps view has a search box, analogous (to the user) to the Data
> search box.  This should do a full text search on map titles and abstracts.
>
> I'm going to make some tickets for these features and other related UI bits
> soon.
>
> Any questions/comments?
>
> --
> Sebastian Benthall
> OpenGeo - http://opengeo.org
>
>


-- 
Sebastian Benthall
OpenGeo - http://opengeo.org

On 07/14/2010 02:06 PM, Sebastian Benthall wrote:
> One thing i forgot to mention:
>
> With the removal of the Featured Map from the home page and the 
> combining of the "CAPRA Maps" and "Community Maps" tabs into a single 
> view, there is no longer a use for the 'featured' and 'endorsed' 
> fields on the Map model.
>
> So I think we should remove them.
>
> Possible reasons NOT to remove them: somebody wants to do something 
> with these properties in a specific custom instance;
That person can jump through some JOIN-shaped hoops.  I don't think we 
should include things in GeoNode that aren't being used by an actual 
deployment.
> it's a pain to do a database migration.
In a real database, dropping a column is easy (although not automated by 
Django, barring an extension like South).  In sqlite (used on the demo 
at geonode.capra.opengeo.org) it is impossible; you have to dump the 
data and rebuild the database.  But that kind of offline massaging is 
also required for some other changes currently in discussion (see the 
thread on background layers which has evolved into a discussion of 
projections in map configurations).  So I am +1 on dropping the 
'featured' bit.
>
> Neither of these reasons seem particularly strong, but I wanted to ask 
> first.
>

--
David Winslow
OpenGeo - http://opengeo.org/

Good times happening over in this branch, for anyone interested in tracking
progress or contributing:
http://github.com/sbenthall/geonode/commits/welcome

On Wed, Jul 14, 2010 at 2:13 PM, David Winslow <dwinslow@opengeo.org> wrote:

> On 07/14/2010 02:06 PM, Sebastian Benthall wrote:
>
>> One thing i forgot to mention:
>>
>> With the removal of the Featured Map from the home page and the combining
>> of the "CAPRA Maps" and "Community Maps" tabs into a single view, there is
>> no longer a use for the 'featured' and 'endorsed' fields on the Map model.
>>
>> So I think we should remove them.
>>
>> Possible reasons NOT to remove them: somebody wants to do something with
>> these properties in a specific custom instance;
>>
> That person can jump through some JOIN-shaped hoops.  I don't think we
> should include things in GeoNode that aren't being used by an actual
> deployment.
>
>  it's a pain to do a database migration.
>>
> In a real database, dropping a column is easy (although not automated by
> Django, barring an extension like South).  In sqlite (used on the demo at
> geonode.capra.opengeo.org) it is impossible; you have to dump the data and
> rebuild the database.  But that kind of offline massaging is also required
> for some other changes currently in discussion (see the thread on background
> layers which has evolved into a discussion of projections in map
> configurations).  So I am +1 on dropping the 'featured' bit.
>
>
>> Neither of these reasons seem particularly strong, but I wanted to ask
>> first.
>>
>>
> --
> David Winslow
> OpenGeo - http://opengeo.org/
>



-- 
Sebastian Benthall
OpenGeo - http://opengeo.org