Profiling the atlas retrieval code hasn't thrown up any horrors - quite a few chars are getting allocated in the sql calls but there's not much we can do about that.

Indexing the atlas entries seems OK. They're all accumulating "atlas" in the metadata field, so we can look at adding a new rank option to prefer atlas entries.

Been thinking about how to integrate a wildcard atlas entry, which will display the map at any given lat/lon. The display side would be fairly easy, but the integration itself is trickier. Would the entry itself hold the form code? If not, and the form is on a jsp, how would the web server know which entry to request without a nasty bit of hardcoding? We could give it a particular category (like we do for jacket pages), but then we still need to know which volume to use. If the result is displayed as an entry page, would we want the entry title to reflect the requested coordinates? Alternatively, we could bypass the entry system entirely and have all the logic in a jsp, making appropriate requests so that the logs reflect usage of the atlas data.

I think the best solution would be to have an RML element to handle it in a similar way as we do for atlas-click navigation.

How badly do we want this feature? Have to say I'm quite keen to get off atlases and on to the next big thing asap.

T

- posted by Tim Bruce @ 5:02 PM