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

MetaTagger in 6.1

awgolk

Does anybody know how to turn this thing off? We currently use another process to assign metadata and I can't find in the documentation where to turn it off.

Sorry it is actually called the Tagger GUI

Edited by awgolk on 06/29/04 01:06 PM (server time).

Find more posts tagged with

Comments

Migrateduser

Perhaps you would be interested in the section "Eliminating the Tagging Step from ContentCenter Standard Wizards" in the UI Customization Guide. It this the "this thing" to which you were referring?

Brinko Kobrin
Interwoven Staff Engineer

gzevin

well, removing just the tagging step will not help. One needs to remove the 'Tag' menu option from both interfaces

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

awgolk

Yes this is exactly what I was looking for.

Migrateduser

I've attempted to follow the steps in this section of the UITK document - Eliminating the Tagging Step from ContentCenter Standard Wizards by adding the following lines into <iwhome>/local/config/lib/content_center/customer_src/etc/conf/customer/application_custom.xml:

<applications>
<application id="ccstd">
<param id="skip-tag-step" value="true" />
</application>
</applications>

but when I run make_toolkit.ipl from my customer_src directory, it appears to work:

Buildfile: /interwoven/iw-home/local/config/lib/content_center/reference/build.xml

init:

compile:

validate:

files:
[war] Building war: /interwoven/iw-home/local/config/lib/content_center/customer_out/customer.tk.war

update:

[exec] ***** Analyzing content_center *****
[exec] Previous install of customer toolkit: Tue Jul 27 15:53:32 2004
[exec] Changed files: 1
[exec] WEB-INF/conf/customer/application_custom.xml

[exec] ***** Updating content_center *****
[exec] Updated WEB-INF/conf/customer/application_custom.xml
[exec] Resetting Interwoven UI services... done.

BUILD SUCCESSFUL
Total time: 53 seconds

However, when I look at the resulting output file in my customer area (<iwhome>/local/config/lib/content_center/customer/WEB-INF/conf/customer/application_custom.xml) it does not include these lines, as if nothing was updated and the time stamp on that xml file is not updated. What the ****?

Has anyone successfully removed the auto-tagging from the CCSTD workflow process? If so, please enlighten me on what I'm doing wrong...

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Edited by Smitty77 on 07/28/04 08:19 AM (server time).

iwovGraduate

Has anyone successfully removed the auto-tagging from the CCSTD workflow process?

Yes. TS 6.0; W2K and TS 6.1 W2K.

If so, please enlighten me on what I'm doing wrong...

Beats me.

The only thing I have different in my file is the closing of <param tag. See below: notice the <param></param> instead of <param/>. (Shouldn't make any difference but I have learned the hard way not to assume too much)


<applications>
 <application id="ccstd">
 <param id="skip-tag-step" value="true">
 </param>
 </application>
</applications>

Migrateduser

Strangely enough I tried that - only because I needed some change made to force the make_toolkit.ipl script think something had changed in my XML file and attempt to copy it over again. This is baffling. I've been able to do customizations in the ui_custom.xml file with no problems. This is the first change in application_custom.xml I've made. Here's the exact contents of the application_custom.xml file - let me know if I put the XML in the wrong place:

<?xml version="1.0" encoding="utf-8"?>


<iwov-ui>
<applications>
<application id="ccstd">
<param id="skip-tag-step" value="true" />
</application>
</applications>
</iwov-ui>

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

Smitty77 wrote:
However, when I look at the resulting output file in my customer area (<iwhome>/local/config/lib/content_center/customer/WEB-INF/conf/customer/application_custom.xml) it does not include these lines, as if nothing was updated and the time stamp on that xml file is not updated. What the ****?

TeamSite 6.1 does not use the "customer" directory. The update should have been made in the /interwoven/iw-home/local/config/lib/content_center/customer_out directory. This change was made to simplify the experience for developers who, in 6.0, were often confused by the difference between the "customer" and "customer_src" directories. The "customer_out" directory should be mostly opaque to users, and should never be modified directly.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

Why is there a customer directory path then?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

So what am I doing wrong? Why am I still seeing the Metatagger page when I go through CCSTD? Do I need to do something after running make_toolkit.ipl in order to see the change? All I did was logout and log back in to CCSTD. Did I miss a step?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

> Why is there a customer directory path then?

I assume that you upgraded the system from 6.0. As explained in the documentation, you can remove the customer directory after migrating your customizations to the customer_src directory. It is not safe for us to automatically remove the directory.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

Ok. Can you please point me to the documentation that explains that?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

> So what am I doing wrong?

Try removing the <iwov-ui> tag that you have wrapped around <applications>. It is not used in the applications config file.

BTW, make_toolkits.ipl has an option (-native_ant) to validate the XML config files. It should catch many common problems. See the customization guide for details.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

Dang it - the default application_custom.xml file looks like this:

<?xml version="1.0" encoding="utf-8"?>


<iwov-ui>
</iwov-ui>

The README file doesn't mention anything about the application_custom.xml file to indicate the <iwov_ui> tags should be removed. The default file you distribute should not contain tags that shouldn't be there. Talk about confusing...

Thanks for the help - that did the trick. That was definitely not clear. I figured since I wasn't getting any errors in my output from make_toolkit.ipl it was something I was doing wrong. Thanks again, Brinko.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

I found the documentation - the section at the end of the UITK manual which talks about upgrading from 6.0 to 6.1. It is a little vague about deleting the whole customer directory structure, but I can see where one could draw that conclusion. Thanks.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

> Dang it - the default application_custom.xml file looks like this:
> ...
> <iwov-ui>
> </iwov-ui>

Sorry. It looks like this was a bug in the application_custom.xml file in 6.0. It was fixed in 6.1, so it should not appear with a clean install. Unfortunately, the problem is not fixed during an upgrade to 6.1 because our installer is not smart (complex) enough to merge our changes with customizations that may have been made.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

For what its worth, after a 6.0 to 6.1 upgrade, you should have a directory customer_src_new that contains the files that would be present in a clean 6.1 installation. You may want to compare its contents against that of your customer_src directory.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

Ahh, good to know. We won't have these same issues when we upgrade our production box as that will be a 5.5.2 -> 6.1 upgrade. Thank goodness this is all on our dev server. Thanks for the info on all this - very helpful.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com