Reorder the Exporting Data/Project chapter

[bencomp]

This closes #84.

Discuss exporting the cleaned data before exporting a project file. Update the text to flow nicely.
This also reorders the objectives and updates the questions and key points.

Note:

• I put some text that used to be part of the main text in callouts.
• the "saving happens automatically" callout also mentions opening existing projects (which relates to Add instructor note on Open Project #166). It may be better placed at the top of the chapter, to provide context to why you need to export data, unlike many other applications that work directly on files.
• the "Importing a project" section is short and may be moved to an earlier chapter that could cover opening projects as well.

[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/openrefine-socialsci/compare/md-outputs..md-outputs-PR-169

The following changes were observed in the rendered markdown documents:

 06-saving.md | 133 +++++++++++++++++++++++++++++++++++++----------------------
 md5sum.txt   |   2 +-
 2 files changed, 85 insertions(+), 50 deletions(-)

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 2023-07-19 10:18:41 +0000

[bencomp]

Thanks for reviewing, @ndporter!