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

Updating EAs in STAGING area?

System

I'm trying to use the iwextattr CLT to externally update content metadata to be displayed in a customized Tagger GUI called up from a workflow. After using the tool to update the files' EAs in our WORKAREA (and not having it carry over to the Tagger GUI's display), I think I realized that the proper place to make these EA changes is in the STAGING area.

Can someone confirm this for me?

If this indeed is the case... The STAGING area directories are (by default, I presume) not permitted for write access, which is necessary to update the EAs. Is it reasonably safe to open up these files and directories for write access, update the EAs as needed, and then button them snugly back up again? What risks does this present (assuming my presumptions as outlined are correct...)?

Thanks.

Find more posts tagged with

Comments

nipper

you have not used TS for very long have you ?

You cannot make changes in Staging. End of discussion.

You MUST change a file in a workarea and submit those changes to Staging.

I hope you get some training.

Andy

Migrateduser

OK - thanks for the feedback.

I understand the system architecture somewhat, but changing EAs in the WORKAREA doesn't update the content's metadata as far as MetaTagger is concerned. It appears MetaTagger is getting it's Tagger GUI "clues" / "starting points" from the STAGING EAs.

It seems you're saying there's no way to update this metadata other than through the Tagger GUI - is that correct?

nipper

OK - thanks for the feedback.

I understand the system architecture somewhat, but changing EAs in the WORKAREA doesn't update the content's metadata as far as MetaTagger is concerned. It appears MetaTagger is getting it's Tagger GUI "clues" / "starting points" from the STAGING EAs.

It seems you're saying there's no way to update this metadata other than through the Tagger GUI - is that correct?

I think you are a bit confused here.

If I run MT ona file in a WA, it changes the EAs on that file in the WA. You can run the iwextattr -l command on the file to see.

If I save that MD and start Tagger again, it should load that data into the GUI the next time.

If you submit the changes (adding MD to a file is a change) the new MD will be in teh Staging area.

One more point for you to remember. If you copy a new version (via import, or a copy) by default TS will not inherit the EAs from one version to another. There is a special setting to make that work, some searching on devnet can find it, iif it is an issue.

HTH

me

TestReport.rptdesign

Migrateduser

...If I save that MD and start Tagger again, it should load that data into the GUI the next time...

Thank you - this is helpful. I'm not sure what you mean by saving the metadata... I thought adding or updating the EAs for a file IS a "save". It (the metadata) is not stored someplace else, is it?

nipper

When you have the MT screen there should be a save button and a cancel button. THat is what I was talking about. THe EA should be changed at that time. It is visible from the file properties selection.

Migrateduser

Resolved my issue with your capable assistance.

I was modifying EAs in my WORKAREA that don't impact the custom Tagger GUI, which is why I wasn't seeing any change in the GUI contents.

In my case (and maybe others' cases, which is why I'm sharing this experience), I have an EA named "subjectMetatdata0", which holds all the Tagger GUI values in XML format. Changing the value of the XML string (in the WORKAREA) to include or exclude what I need for each file I'm concerned about, and then submitting the file through the workflow linked to the Tagger GUI displayed the values I changed in the WORKAREA. As nipper noted above, the STAGING area remained sacrosanct, and the submit brought along the EA changes to STAGING.
Thanks for the guidance!

two_column.rptdesign

OffenderProductList_two.rptdesign