A Simple Zenodo Access Checker for Storyline

Carmel — clean solution, and yes, this exact pattern generalizes well. The version I'd build: parameterize the domain and the Storyline variable, then loop over a small list of { url, variable } pairs when the slide loads. One script covers every external dependency in the course instead of one trigger per host.

Two honest caveats about no-cors fetch, since the behavior can surprise people:

1. The response is opaque — you can only tell "something answered" from "nothing answered." A domain can be up while the specific resource is broken, so this catches network-level problems, not dead links or changed DOIs.

2. Some LMSs block or delay cross-domain fetch from inside a SCORM package even when the learner's network is fine. Worth testing on the actual LMS, not just Review 360: if the advisory fires there on a healthy network, it's the environment, not Zenodo.

One more thought: an advisory tells the learner what went wrong, but not what to do. Where the paper matters, consider swapping the DOI link for a "request the PDF from your facilitator" button when the check fails — an advisory parks the learner, a next step keeps them moving.