On Sep 18, 2012, at 5:14 PM, Jukka Zitting <[email protected]> wrote:
> Hi, > > We now have a couple of initial index implementations for Oak and some > ideas on how index configuration could/should work. In order to start > unifying those approaches and to find some common consensus, I'd like > to throw out an idea of how I think index configuration should work in > Oak. Critiques, improvements or competing ideas welcome! > > First of all I think there shouldn't be just one single place in the > repository where all index configuration should go. It would be nice > if users and applications could define custom indexes on areas they > have write access to, and having to grant them access to some shared > location for that might be troublesome. > > Instead I'd allow a custom indexes to be defined by adding something > like an oak:indexed mixin type and an associated oak:indexes child > node to any node in the repository. Each child node of that > oak:indexes node would configure an index for the subtree rooted at > that oak:indexed node. Index configuration would be stored as normal > content, and the index content in a hidden :index subtree or elsewhere > depending on the type of the index. would this also allow to offer something similar to the virtual nodes based on facettes that HippoCMS currently offers? regards, Lukas Kahwe Smith [email protected]
