Hello,
We use Content Integrator to connect to CMOD and retrieve documents. There is a business requirement to programmatically update a CMOD metadata value based on a request from a source system. The use case is if the source system sends an updated document, a CMOD metadata value of the prior document needs to be updated to indicate that the document is no longer valid. Our understanding is that the Content Integrator connector does not support the update of a metadata value in CMOD. Have you used the ODWEK API ODHit.updateValuesForHit method? If so, can you provide any implementation details?
Thank you.
Quote from: LSanderson on February 05, 2016, 06:19:03 PM
Hello,
We use Content Integrator to connect to CMOD and retrieve documents. There is a business requirement to programmatically update a CMOD metadata value based on a request from a source system. The use case is if the source system sends an updated document, a CMOD metadata value of the prior document needs to be updated to indicate that the document is no longer valid. Our understanding is that the Content Integrator connector does not support the update of a metadata value in CMOD. Have you used the ODWEK API ODHit.updateValuesForHit method? If so, can you provide any implementation details?
Hello,
You can look at this chapter on the documentation for the programming part of ODWEK : http://www-01.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.odwek.doc/dodwj000.htm (http://www-01.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.odwek.doc/dodwj000.htm)
For your specific question: http://www-01.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.odwek.doc/dodwj030.htm (http://www-01.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.odwek.doc/dodwj030.htm)
And also look for this redbook: http://www.redbooks.ibm.com/abstracts/sg247646.html (http://www.redbooks.ibm.com/abstracts/sg247646.html) for a more generic and practical approach of ODWEK.
Hope that helps.
Thank you for the information. It is very helpful.
Also, of those who have implemented a process to update metadata, did you set it up to be "real-time" like a service, or in a batch mode where a file of needed updates is processed on a schedule?
Wherever possible, I prefer to run modifications to metadata in batch during periods of little to no end-user activity. There are only a few things that are worse than locking up a database table in the middle of the day.
Well you need to check. With my experience on several customer, we never experience any locks.
But it would be good to test it before going with "real time" update, if you get such locking...
You must keep in mind, that CMOD is an archive, and normally the indexes are also part of the archiving document.
Some countries, like Switzerland, don't allow changes in the metadata without some business approval and some compliant report showing the change, etc...
The only exception is some "status field". where they are not part of the document itself, but more from a workflow perspective.
That's why the application group fields are per default "not updateable", because this is against the goal of an archive to modify the data.
I am just saying that, without knowing what you are planning to do. But I felt the need to tell you this important matter... because you might in your case be impacted, or not!!!
Thank you very much for the responses.
Our use case is similar to what has been described - updating a "status field" of a document. The field will indicate if the document should not be presented to the requesting system.