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

EA's :numberOfChunks,subjectMetadata0!

Arash

Hi!

We are using the TS 6.5 SP2, OD6.1.1.

After running File->Tag for a dcr and then clicking on finished, the properties
for the tagged dcr shows two extra EA's:
numberOfChunks :1
subjectMetadata0:
<metadata>

Does anybody know why we are getting these extra EA's and how
we can rid of them?

Thanks

Regards
Arash

Find more posts tagged with

Comments

Adam Stoller

Hi!

We are using the TS 6.5 SP2, OD6.1.1.

After running File->Tag for a dcr and then clicking on finished, the properties
for the tagged dcr shows two extra EA's:
numberOfChunks :1
subjectMetadata0:<?xml version="1.0" encoding="UTF-8" ?>
<metadata></metadata>

Does anybody know why we are getting these extra EA's and how
we can rid of them?

Thanks

Regards
Arash

Are you using (or have you used) MetaTagger? - I believe both of these items come from MetaTagger though I'm not sure exactly why.

Arash

No, we have not used the MetaTagger.

Regards
Arash

Adam Stoller

No, we have not used the MetaTagger.

Regards
Arash

Check with Support then - the only mention I saw of those particular metadata fields was in a MetaTagger manual...

Frederik

hi,

I can't answer the original question, but given Ghoti's mention of MetaTagger, I can say that on a Solaris system with
- TS 6.5 SP2 + patch 1614 & Search 1.0 SP2 & OD 6.0.2
- no MetaTagger
- no changing of the out-of-the-box Extended Attributes config (IWHOME/local/config/datacapture.cfg)

I also get those 2 EA when setting tags on a random file.

[html]TeamSite/Metadata/Business Unit: Admin
TeamSite/Metadata/Business Unit/Admin: y
TeamSite/Metadata/Creation Date:
TeamSite/Metadata/Description:
TeamSite/Metadata/Expiration Date:
TeamSite/Metadata/Keywords:
TeamSite/Metadata/Title: my title
numberOfChunks: 1
subjectMetadata0: <metadata>[/html]

Adam Stoller

hi,

I can't answer the original question, but given Ghoti's mention of MetaTagger, I can say that on a Solaris system with
- TS 6.5 SP2 + patch 1614 & Search 1.0 SP2 & OD 6.0.2
- no MetaTagger
- no changing of the out-of-the-box Extended Attributes config (IWHOME/local/config/datacapture.cfg)

I also get those 2 EA when setting tags on a random file.

[html]TeamSite/Metadata/Business Unit: Admin
TeamSite/Metadata/Business Unit/Admin: y
TeamSite/Metadata/Creation Date:
TeamSite/Metadata/Description:
TeamSite/Metadata/Expiration Date:
TeamSite/Metadata/Keywords:
TeamSite/Metadata/Title: my title
numberOfChunks: 1
subjectMetadata0: <metadata>[/html]

Is it possible that 'search' adds them? I'm just guessing - as I haven't personally witnessed this issue.

Frederik

Is it possible that 'search' adds them? I'm just guessing - as I haven't personally witnessed this issue.

I doubt it
- Search is installed, but not really configured. I'm 99.9% percent sure I tried this in a branch that was not added as "branch to be indexed".
- The file I tagged was not tagged nor submitted before. Immediately after tagging, those EA were visible in File-Properties, even without submit or anything... Normally, search/indexer would not have 'known' about this file.

Adam Stoller

I doubt it
- Search is installed, but not really configured. I'm 99.9% percent sure I tried this in a branch that was not added as "branch to be indexed".
- The file I tagged was not tagged nor submitted before. Immediately after tagging, those EA were visible in File-Properties, even without submit or anything... Normally, search/indexer would not have 'known' about this file.

Hmm - maybe it has to do with a specific version/SP/patch of TS whether or not the tagging function adds those fields - or maybe I've just been looking at files which were tagged programmatically with iwextattr and not through the GUI...

However - all that being said ...

Does anybody know why we are getting these extra EA's and how
we can rid of them?

I'm not sure what their purpose is - perhaps someone from IWOV (Support?) can explain.
As for getting rid of them - you can use iwextattr to get rid of them - but do you really care?
What problems do their existence cause?

Arash

For the moment this does not cause any problem for us.
We just wanted to know the reason we are getting these EA's, because we have to explain for our users what these EA's are.

nickcolorado

It looks like the subjectmetadata0 attribute provides an xml representation of the teamsite extended attributes on a file. We would like to extract this attribute as the xml on the file instead of extracting each extended attribute individually but are unable to find any documentation referncing the attribute, its purpose, or if the attribute is supported. Can anyone provide any information on the field? It also looked like the subjectMetadata0 extended attribute contains only metadata applied via metatagger. Is it possible to get the subjectMetadata0 extended attribute to contain all extended attributes, including those that are not metatagger enabled?

Thanks,
Nick

Adam Stoller

It looks like the subjectmetadata0 attribute provides an xml representation of the teamsite extended attributes on a file. We would like to extract this attribute as the xml on the file instead of extracting each extended attribute individually but are unable to find any documentation referncing the attribute, its purpose, or if the attribute is supported. Can anyone provide any information on the field? It also looked like the subjectMetadata0 extended attribute contains only metadata applied via metatagger. Is it possible to get the subjectMetadata0 extended attribute to contain all extended attributes, including those that are not metatagger enabled?

Thanks,
Nick

If you are dealing with EAs (as opposed to file attribute metadata) - you can get the XML for all of them using iwextattr -l -x vpath

If you are talking about file attribute information as well (owner, last modified date, last modified by, etc.) - unless you are somehow tacking those on as EAs you would have to either

stat

the file or use the iwattrib CLT - the latter, unfortunately, does not provide a means to extract all attribute values in one run (in any format).

As I'm not sure what "subjectMetadata0" - I do not know whether it would get picked up via iwextattr or not - but you should be able to determine that quite easily by trying it.