I agree with Thomas. We also need to decide what is the expected behaviour of the (Solr) search regarding document aliases. Should the user be able to search for a document using one of its aliases? Suppose Foo.Bar is an alias for One.Two.Three.Four. If I understood correctly your proposal, when the user visits Foo.Bar he will actally see One.Two.Three.Four (e.g. the breadcrumb will be One > Two > Three > Four and not Foo > Bar). This means that normally there will be no mention of "Foo" and "Bar" on the UI, but the user may notice them on the URL. So are "Foo" and "Bar" relevant for this document? i.e. should this document be returned when the user searches for "Foo" or "Bar"? Before we answer this we need to decide who has the right to create a document alias: (1) anyone that can create the alias document (e.g. Foo.Bar) (2) anyone that can create the alias document (e.g. Foo.Bar) and that has edit right on he target document (One.Two.Three.Four) (1) is more natural, but if we decide that the document alias is relevant for the document when performing a search then it means anyone can "tag" a document without edit right. E.g. Alice creates an alias "Bullshit" for Bob's "Best Practices" and now anyone searching for "bullshit" will get Bob's document in the results. So from Solr point of view there are 3 options: * don't index aliases * index aliases along with the target document (e.g. there will be one "row" in the index for "Foo.Bar" and "One.Two.Three.Four", and a multi-valued field "aliases"). This raises the "tag" problem described above. * index aliases as separate documents and thus duplicate the index data corresponding to a document whenever a new alias is created. This will lead to unexpected duplicated search results. Thanks, Marius On Fri, Aug 14, 2015 at 12:26 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: