Fetch imprint from dynamic ACDH-CH service

[dpancic]

In GitLab by @KlausIllmayer on Jul 28, 2022, 16:43

This issue was touched in #28 but not further handled.

We have every now and then changes in the signing power section of the imprints at OEAW. Therefore we do have a dynamic imprint service which is located at ACDH-CH and should always deliver the current version of the imprint.

@stefanprobst Do you see a way to integrate this dynamic service into one of the MP pages? I guess that this is not easy done within a page holding different text blocks, like it is now in privacy-police. Maybe we should separate the imprint from this page into a dedicated one (which would also fit better Austrian law), what do you think @laureD19?

[dpancic]

In GitLab by @KlausIllmayer on Jul 28, 2022, 17:00

Just a reminder: if we use the dynamic imprint service we need to adapt the values in the redmine issue so that it fits the current text.

[dpancic]

In GitLab by @stefanprobst on Jul 29, 2022, 09:02

the acdh imprint service returns html which we could dump as-is into the "Legal notice" section of the "Privacy policy" page (or a dedicated "Imprint" page).

note however that the imprint text also includes sections on "Copyright notice" and "Data privacy notice"- which we may or may not want to adapt.

also needs decision if the imprint section/page can be built statically or not.

[dpancic]

In GitLab by @KlausIllmayer on Jul 29, 2022, 17:20

yes, i'm aware about the overhead of the imprint text - i guess the copyright/data privacy can be used. i currently see only a problem with english/german version, as it does not work as expected (it always shows both even if i don't define german). but probably we need to have the german version also present, not sure what Austrian law says about it (i remember something in this direction but not sure). i think this could be also another argument for creating a separate imprint page.

regarding statically build: not sure what do you mean with this remark? if it is about explicitly building a static version of imprint page and doing this again, if we are aware about a change in the imprint, then i'm in favour. it does not need to fetch the data from the acdh-ch-imprint-service for every visit (otherwise, i guess it will not happen that much, that people look at the imprint page, so it could be also fine if we always fetch it). @stefanprobst are these the both options you meant where we need a decision?

[dpancic]

In GitLab by @stefanprobst on Jul 30, 2022, 19:11

• it is possible to only request the english imprint text when setting outputLang query param
• yes, fetch imprint once at build time (vs. fetch imprint at request time)

[dpancic]

In GitLab by @KlausIllmayer on Aug 1, 2022, 15:30

• thanks for the hint, i was thinking in the wrong direction, the imprint works like the applied link.
• in this case i'm in favour of fetch imprint once at build time

we still need a decision by @laureD19 if the preference is to have the imprint at the current place or to create a dedicated webpage.

[dpancic]

In GitLab by @laureD19 on Sep 12, 2022, 14:52

if it easier to have a dedicated page for the imprint, I don't mind.
So we would have:

• a new page called "imprint" based on this input automatically updated
• the current page "privacy policy" cut just before what is currently "legal notice"

The only thing I'm wondering, in order to avoid repetitions between those two pages is the necessity to keep the last section from your imprint, the "data privacy notice" as it is stating, with less details, the same than what we have in the privacy policy. Could we delete this part maybe?

[laureD19]

• Privacy Policy
• Imprint > built on acdh content
• Terms of Use

[stefanprobst]

please review #164

[mkrzmr]

@mkrzmr