Andreas Hartmann wrote:
Doug Chestnut wrote:
Andreas Hartmann wrote:
[...]
An internal link URL might look like this:
document://{pubId}:{area}:{uuid}:{language}
Do we really need to have the pubID contained in the internal links?
It would be really nice if we could resolve the pubId from the uuid.
I could see moving content from one pub to another with ease.
Yes, I also thought about this. But it raises the question of resolving
the publication for a UUID. I see two approaches:
- manage a global index
Lucene? We already maintain an index of all documents. If we make
lucene a core module, we could perform a query for a doc with our uuid
(uuid field), then get the pub(s) the doc belongs to from the pubid field.
The sitetree file could be replaced by a parentDoc and childrenDoc
fields in the lucene index. The sitetree would be generated (and
cached?) from the lucene index.
Want to have internal links between multiple lenya instances? Use the
solr module instead of the lucene module.
In 1.5+ this function could be handled by a jcr search module or rdf module?
--Doug
- ask each publication if it contains the UUID
Both options didn't seem very appealing to me, so I discarded
this approach. But of course, moving content to a different
publication can't be neglected, so we should really consider
excluding the publication ID.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
