"Default GeoNode Map" is not good default metadata

[sbenthall]

When somebody creates a new map from a layer, it probably should have a default title that has something to do with the title of the layer involved, not the same metadata as the default map.

[dwinslow]

scope creep!

[dwinslow]

so thinking about this a bit more constructively:

A lot of users are going to be coming into the map editor from the new map link in the maps listing, which means a lot of them are going to be using the same "blank" map configuration to start out. I don't think it makes a lot of sense to statically pre-fill the metadata for this. So probably this feature means adding a "magic" mode to the metadata form where adding and removing layers causes some JavaScript to re-generate some default metadata from a template taking all loaded layers into account. Like for a map containing layers on roads, buildings, and bedrock depth it would be something like:

title: "Roads, Buildings, and Bedrock Depth by Sebastian"
abstract: "Roads: <roads abstract>.
    Buildings: <buildings abstract>.
    Bedrock Depth: <bedrock depth abstract>.
    All combined into a map by Sebastian Benthall."

And then the first time the user types into one of the metadata form fields, 'magic' mode is gone forever and they are back in 'regular' mode. Probably, clicking on a form field selects the entire contents to encourage NOT using the auto-generated stuff. But if you don't care, then a lot of relevant keywords are in the description anyway.

[sbenthall]

Actually, working out some design review stuff on map creation workflow that is relevant and may invalidate this ticket. Freezing for now

[sbenthall]

Nope, that review doesn't make this ticket irrelevant.

[dwinslow]

The defaults are blank (and you can't save a map with an empty title) now.