Deliver package to DG for last article

[eliselavy]

Need to update this before

[eliselavy]

Now watermark is added only for article not with status == PUBLISHED Need to fix XML related issues:

191

192

193

194

[eliselavy]

pdf: http://10.240.4.179/prerendered/en/article/dg/4ZDXFXQwhoA8

xml: http://10.240.4.179/prerendered/en/article/dg/4ZDXFXQwhoA8

package: http://10.240.4.179/prerendered/en/package/4ZDXFXQwhoA8

[eliselavy]

https://journalofdigitalhistory.org/prerendered/en/article/4ZDXFXQwhoA8

https://journalofdigitalhistory.org/prerendered/en/article/dg/4ZDXFXQwhoA8

https://journalofdigitalhistory.org/prerendered/en/package/4ZDXFXQwhoA8

2024/04/18 15:13:52 [error] 37#37: *150 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.244.9.63, server: , request: "GET /prerendered/en/package/4ZDXFXQwhoA8 HTTP/1.1", upstream: "http://172.30.0.4:8000/package/4ZDXFXQwhoA8/", host: "journalofdigitalhistory.org"

[eliselavy]

Need to add: proxy_read_timeout 600s; # Increase the timeout to 600 seconds in https://github.com/C2DH/journal-digital-history-docker-stack/blob/master/nginx/default.conf.template

part :

location ~ ^/prerendered/en/ { rewrite /prerendered/en/(.*)/? /$1/ break; proxy_pass http://backend; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; proxy_cache api_cache; proxy_cache_lock on; proxy_cache_valid 200 302 10m; proxy_cache_use_stale error timeout invalid_header updating http_500 http_502 http_503 http_504; add_header X-Cache-Status $upstream_cache_status; proxy_redirect off; }

[eliselavy]

Timeout more on the puppeter. No timeout this morning

[eliselavy]

Still need to aligned the package on the open issue requirements: http://backstage.c2dh.uni.lux/display/DDRI/Publication

structure package has the old requirements

see issue #166

[eliselavy]

Issue Varia 2 online on DG but

• https://doi.org/10.1515/JDH-2022-0006?locatt=label:JDHFULL Redirection on de gruyter : https://www.degruyter.com/document/doi/10.1515/jdh-2022-0006/html

  • https://doi.org/10.1515/JDH-2023-0008?locatt=label:JDHFULL. Redirection on de gruyter : https://www.degruyter.com/document/doi/10.1515/jdh-2023-0008/html

change occur in crossref related to https://github.com/C2DH/journal-of-digital-history-backend/issues/190

[eliselavy]

From DG: Thank you for reminding me. Yes, ideally, we would find a way that you can register the secondary URLs (if only so you can update them should something change in the URL structure for your platform / for an article). For now, I have to write an IT-support ticket every time secondary URLs need to be added. I will write one for the two articles now.

TO DO: to check when it will be done