Mention ExifTool for reading and writing metadata

[uschille]

Closes #325

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/datacarpentry/image-processing/compare/md-outputs..md-outputs-PR-337

The following changes were observed in the rendered markdown documents:

 02-image-basics.md | 6 ++++++
 md5sum.txt         | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2024-11-30 21:20:18 +0000

[K-Meech]

Thanks @uschille ! I wonder if it would be better to incorporate this text further down in the 'Accessing Metadata' callout? We already mention Fiji/ImageMagick at the end of this callout as options for handling metadata, so perhaps it could be added as another option there?

I'm not sure about including ExifTool in the main text as it isn't the most easy-to-use tool. What do you think?

[uschille]

Good point @K-Meech, thanks! I have moved the text to the callout.

[K-Meech]

Looks good to me!