MetaTagger 4.1.1: Multiple fields using one taxonomy

Hi there,

MetaTagger 4.1.1 (Upgrading from 3.6)
Solaris 9

We are in the process of upgrading to MetaTagger 4.1.1 from 3.6. I’m struggling with converting one of our taxonomies to the new version. We have a recognizer taxonomy called "Agencies" that I’ve successfully imported and deployed to MetaTagger 4.1.1.

However, two other fields need to use the "Agencies" taxonomy (Not sure what the correct term is, but "browse only" fields comes to mind). In MetaTagger 3.6, this was simple. For example, here’s a snippet from our old 3.6 metatagger.cfg:




    DESCRIPTOR_LIST
    Agencies
    Agencies
    Agencies_lookup
    Agencies


    DESCRIPTOR_LIST
    Agencies
originatorLevel2      
Agencies_lookup 


    DESCRIPTOR_LIST
    Agencies
originatorLevel1      
Agencies_lookup

Notice how this configuration allowed the two fields ("originatorLevel1" and "originatorLevel2") to use the Agencies_lookup database. This way, we only had to maintain one taxonomy.

With MetaTagger 4.1.1, it's unclear how to map out this same configuration without creating and maintaining a completely separate project for each of the three fields (which is highly undesirable).

Thanks in advance,

Find more posts tagged with

Comments

Migrateduser

The following from browseonly.smf in $DB_HOME



  browseonly
  browseonly
  browseonly_lookup

  CONTROLLED_VOCABULARY
  browseonly_lookup.db
  browseonly_lookup_index0.db
  browseonly.smf
  false

Migrateduser

Thanks for taking time to reply, snkmoorthy. I definitely appreciate it! It certainly makes sense if the db name is the same as the .smf file name. However, what if I need the .smf file to use a db of a different root name? (i.e., originatorLevel1_lookup.db doesn’t exist in our case). Instead we need this originatorLevel1.smf to use the Agencies_lookup db. “Agencies” is our master taxonomy that we manage through MetaTagger Studio.

Just for grins, I created a file called originatorLevel1.smf with the following configuration:



originatorLevel1
  Agencies
  Agencies_lookup

  CONTROLLED_VOCABULARY
Agencies_lookup.db
  Agencies_lookup_index0.db
  Agencies.smf
  false

When I try to tag a file in the MetaTagger UI, it chokes when it gets to the “Search” part. I’ve attached a screenshot of the resulting error. In short, it’s complaining that it can’t find a db called “originatorLevel1_lookup.db”. My question is…Why can’t we get it to use “Agencies_lookup.db”?.

As I stated in my original post, using a single taxonomy (db file) for multiple fields was easily accomplished in MetaTagger 3.6. How can this be done in 4.1.1?

Thanks,

Migrateduser

I was hoping you would run in to this. The problem is at the TaggerUI end, which just takes the 'item' from your datacapture.cfg and appends a '_lookup' when we click Browse/Add and sends it to MT,in this case originatorLevel1_lookup. At this point, I think the only way out is to copy/symlink the indexes atleast the lookup dbs to originatorLevel1_lookup.(basically replicating the project dbs)

Migrateduser

Thanks again, snkmoorthy. I'm glad that you undestand the problem. As you can imagine, it's somewhat of a challenge to explain.

The good news is that your idea of using a symbolic link worked! I hadn't even thought of going that route. Here's what the new originatorLevel1.smf file looks like now:



  originatorLevel1
  originatorLevel1
  originatorLevel1_lookup

  CONTROLLED_VOCABULARY
originatorLevel1_lookup.db           
originatorLevel1_lookup_index0.db    
  originatorLevel1.smf
  false

The "originatorLevel1" field in the MetaTagger UI now browses the Agencies db successfully.

I still have a support ticket open with Interwoven regarding this. Hopefully they'll have a "cleaner" solution to this. I'll report back here if they do. If not, then I think this solution will do fine.

Thanks,

Migrateduser

Just to follow up...Interwoven Support has responded on this issue. They have reviewed this thread and agree that the solution stated above is the only way to accomplish this. Needless to say, I'm left scratching my head as to why this capability from MetaTagger 3.x wasn't retained in 4.x *shrug*

I indicated to them that this would make a good KB article for others attempting to do the same thing.

Thanks,

Migrateduser

Remember that this is not entirely an MT issue. You could have an SMF file referring to a different db in and use iwmtbatch/iwgenmetdata with suggest_by_tag or just suggest, and it will work. It is just that TaggerUI has made the assumption that an SMF file will always have a corresponding "_lookup" db(by which it sends $project_lookup to MT), which results in this problem.

Migrateduser

... Needless to say, I'm left scratching my head as to why this capability from MetaTagger 3.x wasn't retained in 4.x *shrug* ...

Dan,

Your concern is extremely valid. We definitely could have done a better job of migration and compatibility analysis in the 3.x to 4.x migration. While there were a number of important features added, not all the flexibility of the 3.x releases was preserved.

On a more positive note, it is likely that we will have a better solution with TS 6.7.1 SP1. In that service patch, single-file TagUI will allow more flexibility in mapping items to MT field names, including the ability for two items to use the same MT field.

Regards,
Clark

Migrateduser

Thanks, cbreyman. I appreciate your insight! We're definitely looking forward to SP1, for fixes other than this, of course Smiley Wink