Allowing a second silva instance access to the DL

[Richard H.]

We have just given the testwww site (on the test server) access to the doucment library that is used by the test staff site on the same server.

To do this, I simply activated the 'Silva OAI 2.3.1' and 'Document Library Integration' service extenions within the relevant Silva instance. I also then copied the existing 'document library (oai) service' and 'cherry source' from the staff silva instance and pasted them in the Silva root for testwww.

This works except for the following two problems:

(i) Each document in the produce dlist from a DL listing is appearing twice
(ii) Logged in as me, I could define the DL Listing object but when I tried to save it wanted me to login with different credentials. I had to login with a loclaly defined admin account.

I am certain we saw both these issues last year when we implemented the DL on the new staff site. Are these bugs or have I missed a step or done something wrong somewhere?

[Kit Blake (kitblake)]

This should 'just work'. Could you try deleting the objects you copied and create them using the Add select list menu? It *should* be ok to copy these things across roots, but maybe one or the other stores a path within Zope, or something like that. You could open the 'original' in one tab and make the new one in another tab, then copy/paste the settings.

[Richard H. (richard-hewison)]

Hi Kit,

I'm just going through creating a new OAI service from scratch for testwww.beds to be the same as testin.beds and I have a question.

I assume it's okay to select the 'create storage' option when defining the service, even though the storage has already been created once (within the same Zope instance) for the testin.beds silva instance?

>>> On 24/07/2009 at 17:18, Kit Blake <email address hidden> wrote:
> This should 'just work'. Could you try deleting the objects you copied
> and create them using the Add select list menu? It *should* be ok to
> copy these things across roots, but maybe one or the other stores a path
> within Zope, or something like that. You could open the 'original' in
> one tab and make the new one in another tab, then copy/paste the
> settings.
>
> --
> Allowing a second silva instance access to the DL
> https://bugs.launchpad.net/bugs/404094
> You received this bug notification because you are a direct subscriber
> of the bug.

[Richard H. (richard-hewison)]

Deleting the copied service and creating a new one from scratch removed the double entries problem from the DL Listing objects on testwww.beds. So, to conclude; you can't simply copy these across from one Silva instance to another.

>>> On 24/07/2009 at 17:18, Kit Blake <email address hidden> wrote:
> This should 'just work'. Could you try deleting the objects you copied
> and create them using the Add select list menu? It *should* be ok to
> copy these things across roots, but maybe one or the other stores a path
> within Zope, or something like that. You could open the 'original' in
> one tab and make the new one in another tab, then copy/paste the
> settings.
>
> --
> Allowing a second silva instance access to the DL
> https://bugs.launchpad.net/bugs/404094
> You received this bug notification because you are a direct subscriber
> of the bug.

[Kit Blake (kitblake)]

Now that we know about the separate storage per Silva root, that makes sense.