nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

metadata capture - select box adds multiple EA's

Johnny

TS 6.5 SP2 Solaris 8

When using a select field (not multiple select) there appears to be two EA's that are always set.

1. TeamSite/Metadata/_Field_=_Value_
2. TeamSite/Metadata/_Field_/_Value_=y

I've always noticed this behavior but I'd like to supress the second EA. I don't even understand what it's there for.

Any clues?

Find more posts tagged with

Comments

nipper

I think it is there for search

Just gives you 2 ways to ge tto the data

Johnny

Any clue as to how to disable it?

nipper

no, why ?

Johnny

We have EA tuple processors that read the EA's and send them to BEA Portal via BulkLoader. So now we'll have to strip out any keys with '/' in them. I'd rather remove the feature than work around it.

gzevin

TS 6.5 SP2 Solaris 8

When using a select field (not multiple select) there appears to be two EA's that are always set.

1. TeamSite/Metadata/_Field_=_Value_
2. TeamSite/Metadata/_Field_/_Value_=y

I've always noticed this behavior but I'd like to supress the second EA. I don't even understand what it's there for.

Any clues?

hey John,

this was the case at least since 6

I filter them out when process metadata, probably you should do the same....

gzevin

We have EA tuple processors that read the EA's and send them to BEA Portal via BulkLoader. So now we'll have to strip out any keys with '/' in them. I'd rather remove the feature than work around it.

I think you'll wait too long Smiley Happy

So far I was not given any rationale behind this 'feature'.. But it did not bother me much... just work around

gzevin

I think it is there for search

Just gives you 2 ways to ge tto the data

don't understand your sentence Smiley Happy

how do you get to it when you just see by 'y' that it's simply set....

nipper

don't understand your sentence how do you get to it when you just see by 'y' that it's simply set....

for a phd, you certainly do not understand much

If I have a scrolling list selections a,b,c,d. Each can map straight to a DB column and you can get to it with a simple select

Migrateduser

Someone from engineering once explained to one of my colleagues that they "had" to code it that way to handle any element that could be multivalued. To me that seems like an egregious extension of the word had. There are a number of reasons why this behaviour really bothers me - like the inability to deploy a properly normalized data model from multi-valued EAs. The sheer ****-ugliness of it is pretty annoying, too.

gzevin

for a phd, you certainly do not understand much

If I have a scrolling list selections a,b,c,d. Each can map straight to a DB column and you can get to it with a simple select

still don't, actually. how does this relate to what John has asked?

gzevin

Someone from engineering once explained to one of my colleagues that they "had" to code it that way to handle any element that could be multivalued. To me that seems like an egregious extension of the word had. There are a number of reasons why this behaviour really bothers me - like the inability to deploy a properly normalized data model from multi-valued EAs. The sheer ****-ugliness of it is pretty annoying, too.

I hear you, bro! Smiley Happy

nipper

I have noticed a VERY big problem with this implementation. It is true on TS 6.5 as well as 6.7.1

if I have a select Label 1 -> ValueA, B, C
Label 2 - Value A, G, R
etc

When I save my choice. The initial selection is not remember. Thus if you do a save metadata again, you lose the choice that was made earlier.

Andy