VRR Watermarking at ingest not working on production

[arwenhutt]

Descriptive summary

The process for ingesting pdf's with generation of watermarked service files that was tested and works in staging does not work in production.

I ingested a VRR collection - Layard papers to production with file use value of "document-source" and the "Generate watermarked document and image service files" option selected -- watermarked service images not generated.

Replicated with a second test ingest on production (derivatives not generated):

• Item 1
• Item 2

Also duplicated the test ingest in staging (derivatives were created):

• Item 1
• Item 2

[lsitu]

@rstanonik I found the following error in the log: java.lang.IllegalArgumentException: Can't find command: /usr/local/bin/watermark.sh

It looks like that the watermark.sh program from github https://github.com/ucsdlib/watermark hasn't been on prod installed yet. Could you take a look? Thanks.

[rstanonik]

@lsitu I installed it on lib-hydratail-prod just now. Please try again. Ron

From: lsitu notifications@github.com Sent: Monday, August 12, 2019 10:30 AM To: ucsdlib/damsmanager damsmanager@noreply.github.com Cc: Stanonik, Ronald rstanonik@ucsd.edu; Mention mention@noreply.github.com Subject: Re: [ucsdlib/damsmanager] VRR Watermarking at ingest not working on production (#358)

@rstanonikhttps://github.com/rstanonik I found the following error in the log: java.lang.IllegalArgumentException: Can't find command: /usr/local/bin/watermark.sh

It looks like that the watermark.sh program from github https://github.com/ucsdlib/watermark hasn't been on prod installed yet. Could you take a look? Thanks.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ucsdlib/damsmanager/issues/358?email_source=notifications&email_token=AAUNPICM6CKBHSIRKAY6HD3QEGM2HA5CNFSM4ILDBBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4DH3XI#issuecomment-520519133, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAUNPIF6P36LHYAGX37H643QEGM2HANCNFSM4ILDBBNA.

[arwenhutt]

@rstanonik & @lsitu I retried the test ingest but still no derivatives: https://library.ucsd.edu/dc/object/bb6899053h https://library.ucsd.edu/dc/object/bb7547524c

[rstanonik]

@lsitu damsmanager.properties in prod doesn't have any configuration information about watermark.

[rstanonik]

Looks like I need to jenkins deploy private_config to prod. Let me know if that sounds correct.

[lsitu]

@rstanonik Could you check whether the following lines are there https://github.com/ucsdlib/private_config/blob/develop/damsmanager/production/damsmanager.properties#L113-L116? I think we just redeployed it from master last week.

[lsitu]

@rstanonik I think you've setup a plan in Jenkins for it. And I recalled that you mentioned it was setup to deploy from development branch in the past. But last weekTuesday you talked about to deploy it from master branch so I merged the codes to master and you'd deployed it https://ucsdlibrary.slack.com/archives/C04R0LJSU/p1565119925065100.

[rstanonik]

My mistake. I installed on lib-hydratail-prod, but damsmanager in production runs on lib-ingest. I installed on lib-ingest just now.

Please try again.

Ron

From: lsitu notifications@github.com Sent: Monday, August 12, 2019 12:36 PM To: ucsdlib/damsmanager damsmanager@noreply.github.com Cc: Stanonik, Ronald rstanonik@ucsd.edu; Mention mention@noreply.github.com Subject: Re: [ucsdlib/damsmanager] VRR Watermarking at ingest not working on production (#358)

@rstanonikhttps://github.com/rstanonik Could you check whether the following lines are there https://github.com/ucsdlib/private_config/blob/develop/damsmanager/production/damsmanager.properties#L113-L116? I think we just redeployed it from master last week.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ucsdlib/damsmanager/issues/358?email_source=notifications&email_token=AAUNPIFCU3OLJGCYCO4RRZTQEG3SZA5CNFSM4ILDBBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4DTAZA#issuecomment-520564836, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAUNPIDBOTVCXFTJJU7I4JLQEG3SZANCNFSM4ILDBBNA.

[lsitu]

Thanks @rstanonik . @arwenhutt Could you try it again?

[arwenhutt]

Yay - it seems to be working now. @lsitu how can we get the watermarked service files generated for the Layard collection https://library.ucsd.edu/dc/collection/bb24279581

[arwenhutt]

@lsitu we need the watermarked service files generated for the Layard collection (the ingest which led to this ticket) - can you do that?

[lsitu]

@arwenhutt Do you mean it's still not watermarking as expected?

[arwenhutt]

@lsitu when I do a new ingest it watermarks as expected, but I ingested a collection (Layard) before the code was added to production on 8/12. At that point the derivative creation did not work so the 1139 items ingested do not have watermarked service files. If you click on one of the items you will see that there is no pdf available, and if you look at the metadata there is no file generated at the time of ingest.

[lsitu]

@arwenhutt I am not sure what's the better way to fix it in this case but re-ingest the collection with the ARK for the objects ingested (add ARK column to the spreadsheet) .

[arwenhutt]

@lsitu Ah, so if I add an ARK column and use the excel ingest tool it won't create duplicate records? Would I replace the unique ID with the ARK column or include both?

[lsitu]

@arwenhutt It won't create duplicate object as long as you use the same ARK. We need both the unique ID and the ARK column.

[arwenhutt]

@lsitu I added an ARK column to the ingest spreadsheet for two of the test objects, and then re-imported but got "execution failed" the ingest file and damsmanager reports are here: rdcp-staging\zz_Test\vrr-test

[lsitu]

@arwenhutt Could you use the ARK url in the ARK column like http://library.ucsd.edu/ark:/20775/bb27693246, http://library.ucsd.edu/ark:/20775/bb21208532? Thanks.

[arwenhutt]

@lsitu woohoo! it worked!