Just recently I had a need to utilize the USERDATA metadata that most on clovertech are aware of.
I decided to attempt much of the journey for myself as a learning experience with the help and guidance of my co-worker Jim Kosloskey (thanks Jim buddy).
Once my initial go at it was done, I searched on clovertech for other examples.
I did not find many specific examples, so I decided to share my efforts for others that might benifit from having some specific examples in addition to the concept.
In my case, I have the Xlate check if a document is too big for the field it gets mapped to.
In the Xlate I set the USERDATA metadata to contain a keyed list entry for
DMS_document_too_large_for_TRAN
which gets set to “Y” when truncation occured and “N” when truncation did not occur.
You will notice the proc (xlt_USERDATA_keylset.tcl) below that sets the USERDATA metadata in the Xlate uses xmp.
# Begin Module Header ==========================================================
#
#——
# Name:
#——
#
# xlt_USERDATA_keylset.tcl
#
#———
# Purpose:
#———
#
# Set the USERDATA metadata keyed list entry
#
# If the specified USERDATA metadata keyed list entry does not exist it will be created.
#
# If the specified USERDATA metadata keyed list entry already exists then it will be overwritten
#
# Any other existing USERDATA metadata will be preserved.
#
#——–
# Inputs:
#——–
#
# xlateInVals 0 = @xlt_USERDATA_key
#
[code]# Begin Module Header ==========================================================
#
#
# Name:
#
#
# xlt_USERDATA_keylset.tcl
#
#
# Purpose:
#
#
# Set the USERDATA metadata keyed list entry
#
# If the specified USERDATA metadata keyed list entry does not exist it will be created.
#
# If the specified USERDATA metadata keyed list entry already exists then it will be overwritten
#
# Any other existing USERDATA metadata will be preserved.
#
#
# Inputs:
#
#
# xlateInVals 0 = @xlt_USERDATA_key
#
Russ Ross
RussRoss318@gmail.com