`Bibliogram` ‧ `Privacy Policy` ‧ not tracked anymore

tosdr-bot commented 7 months ago

No version of the `Privacy Policy` of service `Bibliogram` is recorded anymore since 22 April 2024 at 19:27:27 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

request to https://bibliogram.art/privacy failed, reason: connect ECONNREFUSED 72.52.178.23:443

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

[ ] https://bibliogram.art/privacy

If the source documents are accessible through a web browser

Edit the declaration:

Try updating the selectors.
Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

If the source documents have moved, find their new location and update it.
If these terms have been removed, move them from the declaration to its history file, using 2024-04-22T19:27:27Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-04-22T19:27:27Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

tosdr-bot commented 5 months ago

No version of the `Privacy Policy` of service `Bibliogram` is recorded anymore since 19 June 2024 at 1:33:17 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

Fetch failed: request to https://bibliogram.art/privacy failed, reason: write EPROTO 80FC62697C7F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 80

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

[ ] https://bibliogram.art/privacy

If the source documents are accessible through a web browser

Edit the declaration:

Try updating the selectors.
Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

If the source documents have moved, find their new location and update it.
If these terms have been removed, move them from the declaration to its history file, using 2024-06-19T01:33:17Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-19T01:33:17Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

tosdr-bot commented 4 months ago

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

tosdr-bot commented 3 months ago

No version of the `Privacy Policy` of service `Bibliogram` is recorded anymore since 29 July 2024 at 13:27:07 UTC

The source document has been recorded in a snapshot, but no version can be extracted. After correction, it might still be possible to recover the missed versions.

What went wrong

Fetch failed: Timed out after 30 seconds when trying to fetch 'https://bibliogram.art/privacy'

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

[ ] https://bibliogram.art/privacy

If the source documents are accessible through a web browser

Edit the declaration:

Try updating the selectors.
Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

If the source documents have moved, find their new location and update it.
If these terms have been removed, move them from the declaration to its history file, using 2024-07-29T13:27:07Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-07-29T13:27:07Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

tosdr / tosdr-declarations