GeographicEntityLiteProduct
This product has been superseded by the PleiadesEntity Product.
The Geographic Entity Lite product provides Plone content types suitable for constructing and managing collections of simple geographic data items, for example, digital gazetteer entries. The product has been developed using ArchGenXML.
The following content types are provided:
- GeographicEntityLite: built atop the Archetypes Base Folder, Geographic entities can contain 0..n geographic names. This content type provides all standard fields, plus custom fields for:
- alphanumeric identifier (a string)
- geoEntityType (i.e., feature type; a string)
- modern location (a textual description)
- time periods (a list)
- secondary references (a list)
- spatial coordinates (a string encoded according to the geoRSSSimple specification)
- spatial geometry type (a string)
- GeographicNameLite: built atop the Archetypes Base content class, this content type provides all standard fields, plus custom fields for:
- title (this standard field is re-labled in the view template as "nameTransliterated" and it is the intent that an ASCII-transliterated version of the content of the nameAttested field be stored therein)
- alphanumeric identifier (a string)
- geoNameType (a string)
- nameAttested (a unicode string, intended for storing the name in its original orthography)
- nameLanguage (a string, intended to store the name and script associated with the name as attested)
- time periods (a list)
- primary references (a list)
- secondary references (a list)
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 readme.
Future Improvements
This product will be renamed and 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!
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.
