{5} Assigned, Active Tickets by Owner (Full Description) (42 matches)

How accurate and precise are our spatial data? This is a question that many systems dodge or explain poorly. Pleiades will do neither of these.

See http://trac.openlayers.org/ticket/506.

Running the quickinstaller after importing the profile clobbers typeinfo settings.

Without reloading the javascript application.

if the geoentities communicate the largest scale for which their coordinates are valid, this could be useful in map drawing and other contexts

Or maybe some new icons that don't seem so alike to the Panoramio ones. See #250

Set up a through-the-web LDAP management app as a stop gap. After Geo Prime, I'll spend more time on the Plone products: #43, #60.

Exploit #149 to set largest scale of an ol map to prevent users from assuming greater accuracy than exists. For maps that display multiple entities, the most restrictive value should govern the overall map ... or over-zoomed entities should be somehow highlighted.

Would be nice to view the roadmap schedule.

http://www.openqa.org/selenium/

What browsers to support, going forward?

Possibly using live search

Can we devise tests to verify that desired configuration components (e.g., map views, smart folders, indexes) are present in a particular plone?

By default, unauthenticated browsers that hit the pleiades plone portal should not be able to create a user account and get a login. We need a script to effect the lockdown as described, manually, under SingleSignOn.

Shouldn't the Full Name field on the Personal Preferences page get initialized from LDAP? Right now, it's blank for new users.

depends on: #220

Give users a way to flag, or report, transliterations of ancient names they consider to be inaccurate.

In a collaborative environment,it will naturally happen that two or more people enter geographic identities which are the same, overlap, or are related in some way. A collaorative system should provide ways to detect when this has occurred and provide ways to resolve or help users deal with it.

I can see three basic scenarios (maybe there are more) each with a different detection and resolution mechanism.

a) simple duplication. Person A enters a brief and sketchy entry for "Rome" without noticing that person B already has an excellent entry for "Rome". Resolution- after brief discussion, person B agrees to use or point to person B's entry and deletes their own.

b) parallel development. Several people have added overlapping information about a location; no one entry is superior to the others and several entries should be merged. This requires a means of detection, the facility for comments on other peoples entries (there, but seems to be disabled by default) and possibly other collaborative discussion tools (wiki,etc) to allow a collaboratively produced, jointly authored entry tobe created which subsumes the earlier ones.

c) relationship. Person C enters "Vaison La Romaine" and person D enters "Room C3, Villa of the Peristyle, Vaison La Romaine". There is a need for both entries, but the relationship of one to the other needs to be discoverable ("see also" or "part of" relationships). Same for non-point entries, such as districts, provinces, etc.

Right now there are customizations in PleiadesSkin? to support a top-level help folder and providing field-level help based on hierarchy and naming conventions. Better to factor this out into a separate product and change the linking mechanism from url fragments to keywords or relations. Also the product should know how to (un)load its own content on (un)install.

to show off the new field-level help linking

Depends on #93, #199