Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add details to OpenRefine setup as per Issue 234.md #253

Merged
merged 2 commits into from
Oct 31, 2022

Conversation

stephanieuwa
Copy link
Contributor

Adding details about the command line window when OpenRefine first runs as per Issue #234. As raised in the Issue, the Command Line Window was mentioned in the 'Exit' section, but not introduced at the start of the lesson.

Adding details about the command line window when OpenRefine first runs as per Issue LibraryCarpentry#234
Copy link
Contributor

@ostephens ostephens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this @stephanieuwa - just a couple of minor issues before I think this is ready to merge

setup.md Outdated
@@ -22,6 +22,8 @@ If you are using an older version of OpenRefine, it is recommended you upgrade t

Please follow OpenRefine's manual to [install](https://docs.openrefine.org/manual/installing) and [run](https://docs.openrefine.org/manual/running) it.

When running OpenRefine, initially a "Command Line Window" will open. This is a window with a black background. As OpenRefine runs, lines of text will appear in the command line window. Then the Open Refine interface will open in your default web browser. You do not need to interact with the command line window. Leave it open in the background, and work on datasets in your web browser.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor points but I think:

  • command line window shouldn't be capitalised
  • I'm not sure that inverted commas are needed here (we don't, for example, use inverted commas for this in the lc-shell lesson). However if inverted commas are to be used I think it should be "command line" window, not "command line window" (i.e. I think we can assume that learners understand what a window is, but "command line" may not be familiar to them)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ostephens, that's really helpful. I've made those edits. I'm still quite new to GitHub so I don't know if there's anything further I need to do to submit those additional edits to you? They appear to be part of this pull request but I'm not 100% certain. Thanks.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @stephanieuwa - that's exactly the right thing - as soon as you add further edits to the branch you used to create the pull request they appear on the pull request

Editing to improve how the command line window is referred to, as per suggestions on pull request 253
@ostephens ostephens merged commit 264a2b0 into LibraryCarpentry:gh-pages Oct 31, 2022
@ostephens
Copy link
Contributor

Thanks so much @stephanieuwa

zkamvar pushed a commit that referenced this pull request May 1, 2023
Add details to OpenRefine setup as per Issue 234.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants