Closed Maspital closed 2 months ago
One thing I need to think about is how to deal with redirects (3xx), as these will be pretty common. I'll probably first test if there are any non-DOI links which do this - if there aren't things are pretty easy, if there are, I'll probably have to define manual exceptions for the link-checking process.
Additionally, this should also check internal links like /intrusion-detection-datasets/content/datasets/iscx_ids_2012
as these will always generate errors in editors like PyCharm.
Checking this should be pretty straightforward (just verify the files existence relative to the root of the repository).
Some linke are relative, like ../datasets/ait_alert_dataset
, which is similarly trivial - just keep in mind that the initial ../
is only there because GitHub Pages throws a tantrum otherwise, for the purpose of verification it should be ignored.
Implement a tool which parses through all markdown files and checks URLs for their return codes. This could also be integrated into the build process.