Silva-Ghosts: leading slash /, index for ghosts not listed, Metadata configuration

[Flynt]

(This was found in a Silva-1.1.5 installation)

Item 1: If a ghost URL is added manually, a leading slash "/" must not be
entered or the result is a broken ghost, although Silva adds such a slash when
saving the ghost. From the explanations in the SMI it is very tempting for an
author to place a leading slash. This is confusing for the author.

Item 2: Ghost URLs can be chosen via the button "reference". However, "index"
documents are not listed at all. All other documents (including any index_EN,
index_FR etc.) are listed.
However, if an URL of an "index" document is entered manually or via "paste
ghost", there is no problem at all.

Item 3: If the original source for a ghost acquires a metadata value, the ghost
does not show "acquiring" for this metadata field, but uses the actually
acquired value. This can lead to problems if the acquired value for the
respective metadata field in the new environment for the ghost is different. For
example, the original folder/document acquires a colour "blue" and the ghost
should also show the behaviour of "acquiring" (a differnt colour in the new
environment), but instead has colour "blue" of the original she is pointing to.
Is it possible to introduce a switch for ghosts, so that an author can choose
wether the ghost should use the behaviour "acquired" (if set so in the original)
or the respective absolute value of the original (which the original has gained
through acquisition) ?

(This is issue 411 in the ETH Issue tracker).

[Guido Wesdorp (guido-infrae)]

This should be fixed in a release after 1.3 final, se setting status to deferred
while keeping 'Silva-1.3' topic.

[Guido Wesdorp (guido-infrae)]

Changing topic to 1.4, as this will be the earliest we can resolve this. Since
there were also 1.1 and 1.2 topics, I'm wondering, do we want to have a fix for
this backported?

[Flynt (flyntle)]

I would plead for: _no backporting_ of this issue.

[Guido Wesdorp (guido-infrae)]

Created a follow-up for the last of the three mentioned problems (not entirely
sure whether I understand the issue correctly, please review issue 1405), the
other ones should be fixed. Note that you'll need the Kupu trunk (svn co
http://codespeak.net/svn/kupu/trunk/kupu) to use the current Silva trunk.

In order to solve the first problem (and also partially for the latter) I did
quite a large refactoring of asset and link lookups, there's now only a single
lookup window/set of scripts to handle object browsing in all the different
sitations. This lookup thingie uses the new path mangling code, meaning that
from now one you can use URLs instead of physical paths everywhere (also in
virtual host situations). Also this should mean that what objects are displayed
is correct everywhere.

Please test.

[Andy Altepeter (aaltepet)]

item 1) is resolved.
item 2) index documents are listed in the object lookup window, so this is also resolved.