Home / FAQ / Correction of broken links / Correction of broken links: Details

Correction of broken links: Details

This workflow aims to identify, verify, correct, or delete wrong or outdated URLs in keep.eu. The workflow concerns broken or potentially broken links detected through URL validity checks, and includes four entity types:

  • Programmes;
  • Projects;
  • Partnerships;
  • Documents.

In the current operational procedure, only programme URLs and document URLs are verified further.

This workflow follows a monthly cycle: A list containing URL validity check results in keep.eu is received on Fridays. This list triggers the operational review of potentially broken links.

Step I1. Periodic receipt of URL validity check results

The workflow starts when a list containing URL validity check results in keep.eu is received. This step is automatic.

The URL validity check results table includes the following information:

  • Entity label;
  • Entity page;
  • Invalid URL;
  • Response code;
  • Attempted URL.

The table covers four entity types:

  • Programmes;
  • Projects;
  • Partnerships;
  • Documents.

In the following steps of the workflow, only programme URLs and document URLs are verified.

I2. Verification of programme and document URLs

The data manager verifies programme and document URLs identified in the URL validity check results.

Programme URLs:

Programme URLs are checked to confirm whether they are effectively broken. If a programme URL is confirmed as broken, it is deleted manually. The one exception concerns the 2014-2020 and 2021-2027 programming periods. In this case, the correct programme URL is searched and inserted instead of simply deleting the broken URL.

Document URLs

Document URLs are checked to confirm whether they are effectively broken. If a document URL is confirmed as broken, it is deleted manually.

Response-code exceptions

Some response codes are ignored and do not trigger correction or deletion, namely:

  • ‘Potential SSL issue’;
  • ‘429’;
  • ‘403’.

The response codes ‘429’ and ‘403’ are ignored because they refer to YouTube and Vimeo videos.

I3. Clarification of issues

If needed, open questions related to programme URLs or document URLs are discussed in dataflow meetings.

This step involves:

  • Data manager;
  • Technical manager;
  • Project and product manager.

The purpose is to clarify cases where it is not immediately clear whether a URL should be corrected, deleted, ignored, or otherwise handled.

I4. Wrong or outdated URLs are amended or deleted

After verification and, if needed, clarification, the data manager amends or deletes wrong or outdated URLs.

The action depends on the type of URL and the applicable rule:

  • Broken programme URLs are deleted manually;
  • For 2014-2020 and 2021-2027 programme URLs, the correct URLs are searched and inserted;
  • Broken document URLs are deleted manually;
  • Ignored response-code cases are not amended.

This step closes the workflow.

Roles and responsibilities

The data manager is responsible for:

  • Reviewing URL validity check results;
  • Verifying programme URLs;
  • Verifying document URLs;
  • Deleting confirmed broken programme and document URLs where applicable;
  • Searching and inserting correct programme URLs for the 2014-2020 and 2021-2027 periods;
  • Bringing unclear cases to dataflow meetings where needed.

The technical manager is responsible for:

  • Supporting clarification of unclear technical cases;
  • Supporting interpretation of URL validity check behaviour where needed;
  • Supporting discussion of recurring or systemic URL issues.

The project and product manager is responsible for:

  • Supporting clarification of cases where operational or strategic judgement is needed;
  • Ensuring that the workflow remains aligned with keep.eu’s usability and data-quality objectives;
  • Supporting documentation and future workflow evolution.