Paula Muir is a Software Developer with IBM Content Manager OnDemand for Multiplatforms in Boulder, Colorado. She has 20 years of experience with Content Manager OnDemand and 15 years of experience in the data indexing field. Her areas of expertise include indexing and loading data, and AFP and PDF architecture.
Last time I mentioned that I was writing an IBM Redbooks publication, Content Manager OnDemand Guide, and that I could write a whole book about document indexing for IBM Content Manager OnDemand. Why?
I could write a book about indexing in order to explain:
- The different data formats
- Indexing concepts and what the point is of the whole thing
- How indexing is misused
- Common user errors
- How to fix badly formed data
- How to use the CMOD graphical indexer
- How to use the ACIF exits
I'll think of more later.
Today, in addition to red wine ( we'll get to that ), this is the super condensed explanation of PDF floating triggers, which is a new feature of the PDF Indexer in CMOD V9. Hang on!
Warning: If you know nothing about indexing, the following will make no sense to you. Just skip to the bottom and read about wine.
In order to understand floating triggers one must understand group triggers.
Group triggers occur once in a group.
All the group triggers must be found before any fields are collected.
When any field based on a group trigger changes, a new group is started.
Therefore the group triggers and fields determine group boundaries.
A floating trigger may occur multiple times or may not occur at all in a group.
Floating triggers operate independently of each other.
Floating triggers do not define group boundaries.
Since the floating trigger may not occur, a field based on a floating trigger must have a default value defined.
Also, because the floating trigger may not occur, or may occur more than once, a field based on a floating trigger cannot be combined with other fields. Otherwise, the results would be chaotic.
The index values collected from the floating triggers will appear in the Search Results in the same row that contains the index values for the group to which it belongs.
Example of group triggers and floating triggers
Here is an example of a document where a float trigger is needed. In the following statement, the text “Checking Account Balance” or “Savings Account Balance” might or might not occur, depending on whether the accounts exist. If they do exist, you would like to collect the balance amounts to use as fields.
The group trigger will be “Name”, the float triggers will be “Checking” and “Savings”.
For a verbose explanation of what I just said, with examples of why one would ever want to use a floating trigger, see the article in the Content Manager OnDemand Newsletter for 4th Quarter 2012, at:
I was recently in Germany with my Dad, and tasted a wine called Spatburgunder. I had no idea what it was until I got home and looked it up. I only knew that I really, really, liked it. I found out that Spatburgunder was the German name for Pinot Noir. Really! Of course I can't find any Spatburgunder here in Colorado. But maybe if you're on the east or west coast, along the trade routes and all that, you might find some. It's great!
I was going to write about Italian wine. Next time.
For Content Manager OnDemand related blog posts, see:
- 5 Things To Know about IBM Content Manager OnDemand
Enha nced Ret enti on M anag emen t fe atur e in IBM Con tent Man ager OnD eman d
to s ucce ssfu lly inde x yo ur d ocum ent s
- PDF Floating Triggers – If you just have 5 minutes to learn it – Here it is
- How indexing is misused and Italian wine
kin d of sto rage do I us e fo r CM OD ?
al w orld vie w of Con tent Man ager OnD eman d co ncep t s
- Exporting information to a local server to send to Content Manager OnDemand Support
- Need to do tracing? How to turn on the Content Manager OnDemand trace facility
- The CMOD adoption process and why people love it
For more information on Content Manager OnDemand, see IBM Redbooks publications: