We receive afp files to ingest into CMOD. We discovered that occasionally a metadata field that was expected to be populated, had not been populated from the source system. It doesn?t cause an issue loading the file, but the document would be omitted from search results. We have followed up with the folks generating the data when these instances are found, but don?t have an ongoing process to detect occurrences like this. Has anyone put some type of ongoing monitoring or reviewing in place, during or after the load to CMOD?
Thanks.
You might be able to build a named query to find those records -- simply run that query every morning and see if that returns the mystery records. You could automate this by scheduling arsdoc to run the query daily, and eMail the results.
-JD.
Thanks for the information. We do use arsdoc query to extract some pieces of metadata for balancing purposes back to the source systems, so we could check the output for issues like blank fields where there is data expected. When folks discover issues like these, are you updating the metadata in CMOD, unloading and asking the source system to regenerate the data...? Does anyone use exits to do data validation as the files are loading?
I normally ask the provider of the data to ensure that they're sending good files. CMOD is supposed to be an archive, and archives aren't supposed to be storing bad data (or correcting it).