Horde Content Backend
Bugs
People
Description
    Linkback service
    Tagging service
    Search
    Relationship service
    Favicon service
    CMS front end?
Resources



Horde Content Backend

A generic Horde Content system will be created. Initially it will be very basic, providing a horde_content_master table that maps a global horde_content_id to a type and a local id (i.d., global id 32 is a blog post with id 7). This will be a building block for future Horde services, and for things like the linkback service.

In the future, an admin UI for creating and editing content types, including automatic generation of database tables and Rdo Mapper and domain objects, should be written for Horde_Content. This could be the backend of a pretty powerful CMS.


Bugs


People

ChuckHagenbuch is actively working on this project
MichaelRubinsky is working on this project and plans on using the Tagging service in the Kronolith AJAX project


Description

The content backend will include a few generic modules:


Linkback service

The linkback service will provide a generic endpoint for handling incoming trackbacks or pingbacks, and a database table that can track them by horde_content_id.


Tagging service

If possible performance-wise, a Horde-wide content tagging implementation, using content_master_ids, would allow relating tagged content between multiple Horde applications or content types.


Search

Horde_Content_Index will provide an interface for indexing Horde_Content objects in an ElasticSearch (http://www.elasticsearch.org/) cluster. For now, each user will have their own index of all available content to avoid permissions issues. We may introduce a separate public index to avoid duplicating all public content, but right now there isn't an application for this.


Relationship service

Store relationships between two master_ids, with an optional (?) relationship type. If we have a name or summary either in the master table or cached, we can quickly generate a summary of an items related objects.


Favicon service

Instead of having apps store their own favicons or storing multiple copies of favicons for the same site, provide a central favicon type for use by bookmarking and feed applications.


CMS front end?

I'm just going to preserve a quote from Duck here since I'm sure there's something useful to be distilled from it but I'm not capable of doing that distilling right now:



> IMO Jonah should remain as an news feeder or rss aggregator. A CMS module
> should have an editor system, tracing differences between content versions,
> track-backs, connected with other modules (attachments from Gollem, link to
> shopping items from Merk...) and so on. So I would be happy to see an
> dedicated powerful module then extending Jonah or Thomas. I guess as a lot of
> companies uses Horde groupware will really like to see and module for such
> publishing and linking to their data that are already in their groupware
> intranet.

Horde_Content might be the backend that we can build this frontend on.


Resources


    http://en.wikipedia.org/wiki/Linkback
    http://ezcomponents.org/docs/tutorials/Search


Back to the Project List