Informatica PIM. Media Asset Data Quality Check. Version: Date:

Transcription

1 Informatica PIM Media Asset Data Quality Check Version: Date: 7 July 29, 2014

2 Table of Contents Media Asset Data Quality Check 3 Installation and configuration of the example 3 Import of the example into the Workflow Manager 3 Explanation of some steps in the example workflow 3 Step 1: Watchpoint "New Asset has been created" 4 Step 2: Checkpoint "Source filename is not empty" 5 Step 3: Checkpoint "Supplier ID is not Master" 6 Step 4: Checkpoint "Supplier ID is not null" 7 Step 5: Actionpoint "Clear Protocol" 8 Step 6: Checkpoint "Jpg or Png" 9 Step 7: Checkpoint "Resolution >= 72 dpi" 10 Step 8: Checkpoint "Width >= 2 inch" 11 Step 9: Actionpoint "WARN 30000" 12 Step 10: Actionpoint "ERROR 40000" 13 Activate the workflow in the hotfolder 14 Verification of the example in the Supplier Portal 14

3 Media Asset Data Quality Check The supplier portal in versions lower than 7.1 only forwards the data to the Media Manager. All import functionality itself was handled by Media Manager. Since 7.1 the import functionality in Media Manager is extended to perform a quality check of the data (assets) and also send the state of the checks back to the Supplier Portal. The report of the import contains all necessary information about the import. Installation and configuration of the example With Media Manager 7.1 a sample workflow to check the data quality of assets is shipped in the manual folder of the Media Manager installation root. The folder \manual\sampleworklows\dq_check_supplier_portal contains the following files: DQ_Check.zip DQ_Supplier_Portal_MSSQL.xml DQ_Supplier_Portal_ORACLE.xml Info.txt Import of the example into the Workflow Manager Open the workflow administation window in the Workflow Manager of the Media Manager and click on the import button. Select the to your database corresponding xml file. Explanation of some steps in the example workflow The following workflow will be imported. 3

4 IMPORTANT: The workflow has to be modified, because this is only an example. Please adapt the workflow to your business case! Step 1: Watchpoint "New Asset has been created" Operating Instructions: Select the client! 4

5 Step 2: Checkpoint "Source filename is not empty" Operating Instructions: - Description: This checkpoints checks the datafield "PIMG_SOURCE_FILENAME" which is always not empty, when the data is uploaded with the Supplier Portal. 5

6 Step 3: Checkpoint "Supplier ID is not Master" Operating Instructions: - Description: This checkpoints checks the value of the datafield "PIMG_SUPPLIER_ID". The value has to be uneven to "MASTER" otherwise it is an asset of the Master Catalog. 6

7 Step 4: Checkpoint "Supplier ID is not null" Operating Instructions: - Description: This checkpoints checks the value of the datafield "PIMG_SUPPLIER_ID". The value has to be uneven to "null". 7

8 Step 5: Actionpoint "Clear Protocol" Operating Instructions: - Description: This actionpoint clears the database protocol, which can be viewed in the Supplier Portal after a successful upload of assets and import of them in the Media Manager. SQL Command: delete from F_CATALOG_IMPORT_TRAIL where CIMPT_TEXT like '%'+'%KEY'+')' and CIMPT_SEVERITY >20000 Severity value of the database field "CIMPT_SEVERITY" INFO WARN ERROR

9 Step 6: Checkpoint "Jpg or Png" Operating Instructions: Adapt the regular expression to the business case Description: This checkpoint checks the filename with a regular expression. Regular expression:.*\.(?i)jpe?g.*\.(?i)png 9

10 Step 7: Checkpoint "Resolution >= 72 dpi" Operating Instructions: Adapt the value to the business case Description: This checkpoint checks the resolution in dpi. 10

11 Step 8: Checkpoint "Width >= 2 inch" Operating Instructions: Adapt the value to the business case Description: This checkpoint checks the width. 11

12 Step 9: Actionpoint "WARN 30000" Operating Instructions: Adapt the value to the business case Description: This actionpoint creates an entry type warning (30000) into the database protocol for the Supplier Portal. SQL Command: insert into F_CATALOG_IMPORT_TRAIL (CIPMT_JOB_ID,CIMPT_SEVERITY,CIMPT_TIME,CIMPT_TEXT) select CIMP_JOB_ID,30000,SYSDATE,'Resolution less than 72 dpi ' PKOM_MNAME ' (' PKOM_PNR ')' from F_IMGKOMP, F_CATALOG_IMPORTS where PKOM_PNR = '%KEY' and CIMP_CATALOG_ID=PIMG_CATALOG_ID 12

13 Step 10: Actionpoint "ERROR 40000" Operating Instructions: Adapt the value to the business case Description: This actionpoint creates an entry type error (40000) into the database protocol for the Supplier Portal. SQL Command: insert into F_CATALOG_IMPORT_TRAIL (CIPMT_JOB_ID,CIMPT_SEVERITY,CIMPT_TIME,CIMPT_TEXT) select CIMP_JOB_ID,40000,SYSDATE,'Invalid filetype (only png and jpg are supported) ' PKOM_MNAME ' (' PKOM_PNR ')' from F_IMGKOMP, F_CATALOG_IMPORTS where PKOM_PNR = '%KEY' and CIMP_CATALOG_ID=PIMG_CATALOG_ID 13

14 Activate the workflow in the hotfolder Select the new workflow in the administration window of the hotfolder. Verification of the example in the Supplier Portal Upload the example zip file "DQ_Check.zip" into the system. The errors and warnings are displayed in the summary. 14

15 The detail report looks like: 15