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; } } }

iwextattr and multi-line attribute values

System

Does anyone know if/what Interwoven products currently or may in the future set extended attributes to multi-line values?

For better performance I would like to run iwextattr once (-l) when I create the object that represents a file rather than once for each extended attribute (-g) that may exist. I imagine I would use everything before the first = in each line as the attribute name and everything after it and before a linefeed as the value of that attribute. I am not sure if I can reliably parse the output of this command when run with -l though as there could be something in Interwoven products (MetaTagger, VisualAnnotate, etc.) that sets extended attributes to values that span multiple lines (I am relatively sure there is nothing in my custom code that sets extended attributes to multi-line values). I guess I could check the next line of the iwextattr output and if it contains an = character I could assume that it is a key=value pair, but this would not handle the case where the second line of a multi-line extended attribute value contains an = character. This may be a relatively remote consideration but I am trying to write generic, reusable code that will work with this and future releases of all Interwoven products, and I actually remember this being a problem on a previous project (I am not sure if it was my code that was setting attributes to multi-line values or if it was MetaTagger or something else).

Any specifics on this issue would be greatly appreciated.

Find more posts tagged with

Comments

Migrateduser

Hoping to bring this topic to the top again...

Is there any command line/parameter to retrieve the extended attributes as an XML stream instead of flat key=value pairs?

Adam Stoller

I believe there may be one coming - but I'm not sure if it's scheduled for release in 6.0 or post-6.0 - I believe existing commands (iwextattr) will continue to work as they currently do, but the new command will allow more flexibility and better performance for deailing with multiple attributes and/or multiple files.

Since I don't know the details of the tool - nor when it is actually scheduled to be released - that's about all I can say (and some might argue its too much as is) - but I wanted to let you know that issues like this *are* being addressed....

--fish
(Interwoven Senior Technical Consultant)

bboyle

We're using this code:
($value = $self->{'EA'}) =~ s!^.*$key=(.*?)\n([A-Za-z0-9/]+=.*)*$!$1!s;

n.b. $self->{'EA'} contains the output of `iwextattr -l filename`, and $key is the attribute name (e.g. TeamSite/Metadata/Title) passed to the function.

It works so long as attribute values don't contain any text matching "[A-Za-z0-9/]+=". It's a little safer than just checking for "=", but not flawless.

An API for dealing with extended attributes would definitely be a bonus Smiley Happy

milind

Hi,
Please check "-x" option for "iwextattr"

-x Read and write XML with -s and -l options.

Regards
Milind

Hoping to bring this topic to the top again...

Is there any command line/parameter to retrieve the extended attributes as an XML stream instead of flat key=value pairs?