Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RevcontentPrivacy Policy ‧ not tracked anymore #1337

Open
1 task
OTA-Bot opened this issue Feb 25, 2024 · 2 comments
Open
1 task

RevcontentPrivacy Policy ‧ not tracked anymore #1337

OTA-Bot opened this issue Feb 25, 2024 · 2 comments
Labels
location Fetch location is outdated [managed by OTA]

Comments

@OTA-Bot
Copy link
Collaborator

OTA-Bot commented Feb 25, 2024

No version of the Privacy Policy of service Revcontent is recorded anymore since 25 February 2024 at 6:39:42 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

How to resume tracking

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

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-02-25T06:39:42Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-02-25T06:39:42Z 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

@OTA-Bot OTA-Bot added the 429 Fetching fails with a 429 (too many requests) HTTP code [managed by OTA] label Feb 25, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented Feb 25, 2024

Tracking resumed

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

@OTA-Bot OTA-Bot closed this as completed Feb 25, 2024
@OTA-Bot OTA-Bot reopened this May 23, 2024
@OTA-Bot OTA-Bot added location Fetch location is outdated [managed by OTA] and removed 429 Fetching fails with a 429 (too many requests) HTTP code [managed by OTA] labels May 23, 2024
@OTA-Bot
Copy link
Collaborator Author

OTA-Bot commented May 23, 2024

No version of the Privacy Policy of service Revcontent is recorded anymore since 23 May 2024 at 0:41:36 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

How to resume tracking

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

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-05-23T00:41:36Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-05-23T00:41:36Z 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
location Fetch location is outdated [managed by OTA]
Projects
None yet
Development

No branches or pull requests

1 participant