To to list: May-June

[dansand]

• In the snapshot tab, if no animation, revert to figure
• Add "how to cite", based on the creditText field
  • See PR Add 'Cite this model' section in 'Details' tab #78 - @cpalfonso
• What sections currently support markdown/latex formatting, and is it possible to make this apply to all text sections and captions?
• Software section of YAML does not get imported properly, and my attempts to fix this have led to many conflicts.
• Need to add Funder/Funding information to the "about" tab
• Need MATE collection DOI on landing page (http://dx.doi.org/10.25914/yrzp-g882)

[cpalfonso]

I've been unable to build the website locally (interestingly, Netlify doesn't seem to be having any issues), and I've managed to figure out the cause: if no animation is uploaded, the animation field in the markdown file just points directly to the graphics directory:

website/src/pages/models/mather-2022-groundwater/index.md

Lines 143 to 145 in 4635373

	animation:
	src: ./graphics/
	caption: ''

Gatsby then throws an error because this isn't a file. Maybe we should just remove the animation field entirely if one is not provided?

[cpalfonso]

One more thing I've just spotted: whatever process is creating the creditText field in the markdown files isn't grabbing the whole DOI, only the second half:

website/src/pages/models/RodriguezCorcho-2022-ArcCollision/index.md

Line 12 in dbdf4cc

doi: https://doi.org/10.25914/xy60-b940

website/src/pages/models/RodriguezCorcho-2022-ArcCollision/index.md

Lines 14 to 17 in dbdf4cc

	creditText: Rodríguez Corcho, A., Polanco, S., Farrington, R., Beucher, R., Montes,
	C., & Moresi, L. (2024). The Role of Lithospheric-Deep Mantle Interactions on the
	Style and Stress Evolution of Arc-Continent Collision [Data set]. AuScope, National
	Computational Infrastructure. https://doi.org/xy60-b940

[dansand]

Hey @cpalfonso. Thanks for this.

I've been working on some updates, but I've hit some problems with the software section. Currently this does not get loaded properly into the model.js, and my attempts to update this have led to lots of issues, complaints about conflicts. It would be great if you could take a look. Currently the software section is formatted as an array. We could chnage this, but it gives some flexibility later.