Plone-ExistDB integration
Project description
zopyx.existdb
zopyx.existdb integrates Plone 4.3 and higher with eXist-db providing the following features:
mounts an arbitary eXist-db collection into Plone
ACE editor integration
ZIP export from eXist-db
ZIP import into eXist-db
pluggable view mechanism for configuring custom views for XML database content by filename and view name
extensible architecture through Plone Dexterity behaviors
support for XQuery scripts called through the RESTXQ layer of eXist-db (allows you to call XQuery scripts and return the output format (JSON, HTML, XML) depending on your application requirements)
dedicated per-connector logging facility
small and extensible
The primary usecase for zopyx.existdb is the integration of XML document collections into Plone using eXist-db as storage layer. zopyx.existdb is not storage layer for Plone content in the first place although it could be used in some way for storing primary Plone content (or parts of the content) inside eXist-db. There is no build-in support for mapping metadata as stored in XML documents to Plone metadata or vice versa. However this could be implemented easily in application specific code build on top of zopyx.existdb. The design goal of zopyx.existdb is to provide the basic functionality for integrating Plone with eXist-db without implementing any further specific application requirements. Additional functionality can be added through Dexterity behaviors, supplementary browser views, event lifecycle subscribers and related technology.
Installation
Add zopyx.existdb to the eggs and zcml options of your buildout configuration, re-run buildout and install the connector through the add-ons management of Plone.
Configuration
Goto the Plone control panel and click on the Exist-DB configlet and configure the
eXist-db server url e.g. http://localhost:6080
eXist-db username
eXist-db password
Using zopyx.existdb
The package provides a new content-types Connector that will include eXist-db into Plone - either from the top-level collection of your eXist-db database or from a subcollection. You can browse and traverse into subcollections, view single documents or edit text-ish content through the web (using the build-in ACE editor integration).
License
This package is published under the GNU Public License V2 (GPL 2)
Known issues
handling of non-ascii collection and file names
Source code
Bugtracker
Credits
The development of zopyx.existdb was funded as part of a customer project by Deutsche Gesellschaft für Hämatologie und medizinische Onkologie (DGHO).
Changelog
0.1.17 (2014-09-25)
fixed action links
0.1.16 (2014-09-25)
Connector is no longer a folderish object
0.1.15 (2014-09-22)
removed indexing support completely (leaving a specific indexing functionality to policy packages using zopyx.existdb)
0.1.14 (2014-09-15)
fixed subpath handling in create/remove collections
0.1.13 (2014-09-07)
support for removing collections TTW
0.1.12 (2014-09-05)
support for creating new collections TTW
0.1.11 (2014-08-21)
action “Clear log” added
0.1.10 (2014-08-05)
log() got a new ‘details’ parameter for adding extensive logging information
0.1.9 (2014-08-01)
human readable timestamps
0.1.8 (2014-07-31)
minor visual changes
0.1.7 (2014-07-29)
rewritten code exist-db browser code (dealing the correct way with paths, filenames etc.)
0.1.6 (2014-07-29)
fixed improper view prefix in directory browser
0.1.5 (2014-07-13)
minor fixes and cleanup
0.1.4 (2014-07-12)
made webservice query API aware of all output formats (xml, html, json)
timezone handling: using environment variable TZ for converting eXist-db UTC timestamps to the TZ timezone (or UTC as default) for display purposes with Plone
0.1.3 (2014-07-07)
added webservice API interface
various bug fixes
0.1.2 (2014-06-30)
various bug fixes
0.1.0 (2014-06-20)
initial release
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
