Add first draft for info on extensions#196
Add first draft for info on extensions#196bencomp wants to merge 1 commit intodatacarpentry:mainfrom
Conversation
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:
Rendered Changes🔍 Inspect the changes: https://github.com/datacarpentry/openrefine-socialsci/compare/md-outputs..md-outputs-PR-196 The following changes were observed in the rendered markdown documents: 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 2025-10-08 16:30:31 +0000 |
Closes #191. Also closes #177 as this is the last sub-issue tracked by that issue.
I'm not happy about the wording yet, but wanted to suggest a first draft.
Extensions do more than what I explain in the body and in the key point at the end, but since that may change over time, I don't want to list all the potential functionalities that extensions could add or improve. @ostephens mentioned that the LC lesson has a section on extensions, but that feels too thin on information.
I summarised the discussion on adding info on extensions and alternate distributions in #177. It looks like alternate distributions are no longer featured on the OpenRefine website, so I would not bring them up.
I would love to hear from @marijane or @ostephens whether you think this is enough information. If so, I can rewrite it into easier to read text. (Or take your wording suggestions :))