Pleiades Entity, the Product

The Pleiades Entity product provides Plone content types suitable for constructing and managing collections of geographic data items, for example, digital gazetteer entries. The product has been developed using ArchGenXML and i18ndude. The Pleiades Entity product replaces the GeographicEntityLiteProduct.

The following content types are provided:

  • GeographicEntity: objects instantiated from this class are used to represent, and organize information about, discrete, identifiable geographic entities or features. The Plone content type is subclassed from the Archetypes Base Folder. Presently, Geographic entities can contain 0..n geographic names (see below).
  • GeographicName: objects instantiated from this class are used to represent, and organize information about, names associated with parent Geographic Entity objects. This Plone content type is subclassed from the Archetypes Base content class.

Further documentation of the content types, including after-edit and after-creation behaviors (some fields are automatically filled or rewritten) can be found in the UML model.

Usage

See the PleiadesEntity readme.

Future Improvements

This product will be refactored to reduce its emphasis on (but not eliminate its suppport for) historical geographic data. If you use or subclass this product, keep track of your dependencies!

AT References:

Tickets

GeoEntity tickets

#92
ready GeographicEntityLite for interface internationalization
#93
add tool tips to fields for PleiadesEntity product
#146
add name notes to GeoNames, not just description on GeoEntities (batch creation)
#149
add scale/mmu data to geoentity spatial geometry
#172
add orientation to point features
#186
Need metadata about spatial coordinates
#189
Overlaps and conflicts
#191
Create new content from uploaded KML
#199
context-sensitive help for coordinate order
#205
Need excellent Name reference browser
#206
Need excellent Location reference browser widget
#208
constrain numeric precision to actual precision
#234
commonly used but not attested names
#240
Location metadata incomplete
#248
better duplicate names solution needed
#250
surface place typing in kml
#251
placeType indexes need TLC
#254
professional and distinctive icons
#295
more flexibility for modern location / name
#296
handle made-up names
#306
Conflicts between PleiadesEntity quickinstaller and profiles
#311
provide "bad transliteration" flagging mechanism
#343
Adding new location through plone fails
#350
show all creators on view
#351
indicate object type on view/edit templates

Support

Please subscribe to the pleiades-software email list. The archives may be viewed online without subscription.

Attachments