Is there a more effective approach than associating the model’s source code at Software Heritage by including a link to the Zenodo record in the repository’s README file, which directs users to access the data, results, and interpretations?
@alexkies: sorry for the delay in responding. Software Heritage is intended to support just the archiving and downstream study of source code. Equivalent projects have been attempting to do the same for public datasets —be these input or output data — by offering linked open data (LOD) infrastructures and allied cataloging systems. Software Heritage differs in that the project is monolithic — collecting everything within one single physical portal, albeit mirrored across the planet for security.
Stepping back, the particular suite of infrastructure sought will depend on whether the aim is repeatability — so that the original model can be rerun to produce the exact same results (at least to floating point precision). Or reproducibility — so an independent team can produce scientifically identical results, but not necessarily with the same software or even the exact same input data.
Neither objective — repeatability or reproducibility — are easily met under today’s workflows and infrastructures. Indeed, both requirements remain major challenges.
For work within this community on LOD, see this recent YouTube: Publishing open, annotated, and FAIR data with the OEFamily