Tagger UI data

Hi,

iam successfuly able to tag all my DCR with the relevent metadata using the Tagger UI. I wanted to know where the data that is tagged using the Tagger UI is stored and how we can use that data to process it further

Regards,
-santosh

Find more posts tagged with

Comments

nipper

They are stored as extended attributes and you can use iwextattr to get them from the command line or a perl script. If search is properly configured you can use TS search to get them. Finally you can deploy them to a DB or XML file with datadeploy

Migrateduser

I am able to generate the the metadata xml using the command iwextattr -x / -u. Now when ever i am deploying the DCR's i also have to deploy the corresponding metadata to the filefystem.

i am trying to a use a deploy and run scenario to generate the metadata during deployment and deploy the metadata xml as well. Is there any better way of doing this ?

Also the metadata, is currently handed over to a 3rd party vendor and they claim that the metadata is not readable. Is there a way that we can improve the readability of the metadata .

example : the metadata is currently stored as follows

TeamSite/Metadata/Archive=Archive
TeamSite/Metadata/Archive/Archive=y
TeamSite/Metadata/Brand=HI
TeamSite/Metadata/Brand/HI=y

Adam Stoller

I am able to generate the the metadata xml using the command iwextattr -x / -u. Now when ever i am deploying the DCR's i also have to deploy the corresponding metadata to the filefystem.

i am trying to a use a deploy and run scenario to generate the metadata during deployment and deploy the metadata xml as well. Is there any better way of doing this ?

Also the metadata, is currently handed over to a 3rd party vendor and they claim that the metadata is not readable. Is there a way that we can improve the readability of the metadata .

example : the metadata is currently stored as follows

TeamSite/Metadata/Archive=Archive
TeamSite/Metadata/Archive/Archive=y
TeamSite/Metadata/Brand=HI
TeamSite/Metadata/Brand/HI=y

If you're using the '-x' flag - the format of the metadata is XML - what you show above is the output without the '-x' flag (though both should be readable - so I'd double check with your 3rd party vendor about what they really mean)

As for doing this in a DNR - You could probably do this with a DNRDeploymentJob (note the "Job") before and make sure that if you're using a filelist deployment that you include the name of the to-be-generated metadata file in your filelist so that it gets processed by OpenDeploy after the DNR script has been run.

Migrateduser

Thanks fish that helps, i have configured the Deployment as DNR where iam able to generate the XML's and deploy them to the target location.

I have an other query, Is there a way i can change the metadata tag names

currently its storing as /TeamSite/Metadata/=

TeamSite/Metadata/Archive=Archive

Is there a way i can get rid of Teamsite/Metadata, then it would cater to my 3rd party requirements where they need metadata in name value pairs

Adam Stoller

Thanks fish that helps, i have configured the Deployment as DNR where iam able to generate the XML's and deploy them to the target location.

I have an other query, Is there a way i can change the metadata tag names

currently its storing as /TeamSite/Metadata/<item name>= <value>

TeamSite/Metadata/Archive=Archive

Is there a way i can get rid of Teamsite/Metadata, then it would cater to my 3rd party requirements where they need metadata in name value pairs

That is a name / value pair - the name is "TeamSite/Metadata/Archive" the value is "Archive".

However - that being said - you could certainly modify your DNR script that generates the output to filter it to remove the string "TeamSite/Metadata/" from each line.

Personally - I think you'd be better off with the XML format (-x) output as there are less problems with values containing embeded newlines - compare:[html]TeamSite/Metadata/Foo=This is some text
with newlines
and an equal (=) sign
TeamSite/Metadata/Bar=another value[/html]To:[html]

TeamSite/Metadata/Foo
Thisissometext
withnewlines
andanequal(=)sign

TeamSite/Metadata/Bar
anothervalue

[/html](ignore some of the extraneous space characters provided by the forum software)
The latter can be correctly parsed as XML and the entity values easily converted back into their corresponding characters with fairly standard code / libraries / modules - and there's no guessing whether a newlne indicates the end of a value or whether an equal sign is definitively the separator betweek name and value.

However, if the 3rd party folks can't grok it - I just hope all your metadata is simple one-line values...