#43 Implicit doc validation by eXist before import and save

[Swami Kevala]

Set up eXist and schemas so that it does implicit validation each time we add a document to the database - as described in earlier email

[mjc1904]

Logged In: YES
user_id=2010147
Originator: NO

I carried out the steps mentioned in the email and it doesnt work for me. However, this is most likely to be something strange with my vista setup. Why do I get a different database when running as administrator?

I then tried switching off validation but none of the queries (e.g. transcriptText.block) work because of the new namespaces (as you suggested might happen). This is a lot of work to put namespaces everywhere and also very risky because what if one or two queries are missed?

One alternative would be to use a single namespace instead of the three currently specified. Then that could be set at the top level as the default.

But is all this worth it given all the problems?

I think loading a saved transcript into the transcript editor is probably a far better test than the schema validation itself anyway.

I've committed the catalog file to SVN and redesigned the file structure for schemas, conf files and sample files - so it should be a bit clearer now where things are.

[mjc1904]

Logged In: YES
user_id=2010147
Originator: NO

As discussed, delaying till later.

[Swami Kevala]

Logged In: YES
user_id=2004405
Originator: YES

changed priority to 7 from 8

[Swami Kevala]

Logged In: YES
user_id=2004405
Originator: YES

including the reference file

[Swami Kevala]

Logged In: YES
user_id=2004405
Originator: YES

Vista problem?