WLPS - Interwoven integration

Question

We are trying to integrate WLPS and Interwoven here. We have a scenario
where a particular content can apply to multiple countries. So my content
HTML file will have atrributes like :
<META name="type" content = "news">
<META name="Country" content="SINGAPORE">
<META name="Country" content="HONGKONG">
<META name="Country" content="TAIWAN">
My Question is :
1. Academic Question - Is this a legal syntax in html . (I believe it is as
IE does not complain and bother about meta tags)
2. Can WLPS be configiured to support this scenario ?
I see this constraint for WLCS_DOCUMENT_METADATA in SQL which may mean it
does not support it OOB .
ALTER TABLE WLCS_DOCUMENT_METADATA
ADD CONSTRAINT WLCS_DOCUMENT_METADATA_PK Primary Key (
ID,
NAME)
Also when I run dbloader , it only loads 1 record which is Country = Taiwan
I think it overwrites this record bcse of the constraint.
3. What are the implications if I add ID, NAME and VALUE as PK constraint
4. Will my rules engine work if I make this change ?
5. Any documenation available for this type of changes ?

Answer 1

Hiyas,
To shed some light, from a different point of view ...
We used to use SQLServer7, which did not support constraints.
Therefore, there was no constraint between WLCS_DOCUMENT and
WLCS_DOCUMENT_METADATA. And we would will-nilly delete data
from either table. So altering the schema, should have no
adverse effect.
Further, if you analyse the sql trace of a content query,
you'll see that it looks something like -
select [wlcs_document fields]
from wlcs_document, wlcs_document_metadata
where (select [wlcs_document_metadata fields]
     where name="country"
     and value="Singapore")
and (another meta-data sub-select)
and (yet another meta-data sub-select)
So, you see that in a straight content query, you will not run
into trouble either.
The caveat, is that other constructs, such as Ebiz-Control-
Centre, or even the caching may not like multiple metadata
pointing to the same content item.
Conceptually, there is nothing wrong with having multiple
metadata pointing to a single content item. So, in theory, it
should be ok.
dk-
In article <[email protected]>,
[email protected] says...
>
Hi Sanathana,
We are engaged in a similar excercise in my place of work and
have arrived at the same conclusion re the primary key constraint for the multi-valued
data.
Have you tried to implement this yet? We were concerned re any possible adverse
effects that may arise from altering the WLPS DB schema.
How did you get the data from Interwoven into the WLPS DB in the first place -
did you use DataDeploy to populate the WLCS_DOCUMENT_METADATA table?
My other point is that I would not make any judgments on the legality of HTML
syntax based on what IE will or will not accept.
IE, rightly or wrongly, will construct a page from a wide variety of possible
tags and formatting. Netscape on the other hand actually bothers to implement
the spec and therefore will not accept misformed or poor syntactical HTML documents.
Regards,
James
"Santhana Shri" <[email protected]> wrote:
We are trying to integrate WLPS and Interwoven here. We have a scenario
where a particular content can apply to multiple countries. So my content
HTML file will have atrributes like :
<META name="type" content = "news">
<META name="Country" content="SINGAPORE">
<META name="Country" content="HONGKONG">
<META name="Country" content="TAIWAN">
My Question is :
1. Academic Question - Is this a legal syntax in html . (I believe it
is as
IE does not complain and bother about meta tags)
2. Can WLPS be configiured to support this scenario ?
I see this constraint for WLCS_DOCUMENT_METADATA in SQL which may mean
it
does not support it OOB .
ALTER TABLE WLCS_DOCUMENT_METADATA
ADD CONSTRAINT WLCS_DOCUMENT_METADATA_PK Primary Key (
ID,