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

Intro to NEON Exercises #40

Open
Laura-Puckett opened this issue Sep 11, 2020 · 0 comments
Open

Intro to NEON Exercises #40

Laura-Puckett opened this issue Sep 11, 2020 · 0 comments

Comments

@Laura-Puckett
Copy link
Contributor

Laura-Puckett commented Sep 11, 2020

The naming for the NEON Exercises was very confusing, and made it difficult to determine what was actually assigned.

As it is now, the headers are:

2.9 Intro to NEON Exercises Part 1
  2.9.1: Computational
    2.9.1.1 Part 1: Sign up for and Use an NEON API Token
    2.9.1.2 Part 2: Further Investigation of NEON TOS Vegetation Structure Data
2.10 Part 2: Pulling NEON Data via the API
(too many uses of the word "part" in the above block that describe different layers of the hierarchy without consistent naming convention for layers of the hierarchy)
...
2.14 Intro to NEON Exercises Part 2
  2.14.1 Written
  2.14.2 NEON Coding Lab Part 2
2.15 NEON Coding Lab Part 2
  header titled "Intro to NEON Culmination Activity"
2.16 Intro to NEON Culmination Activity
(multiple headers with the same name, more confusion with the use of "part"

One way of solving this would be to rename as follows:

Exercises Part 1
  Exercise 1A: Sign up for and Use an NEON API Token
  Exercise 1B: Further Investigation of NEON TOS Vegetation Structure Data
  Exercise 1C: Pulling NEON Data via the API
...
Exercises Part 2
  Exercise 2A: Written
  Exercise 2B: Coding Lab
  Exercise 2C: Culmination Activity

I know the numbers will change, this is just a suggestion for the actual header names. So for example, if you assign Exercise 1B from Chapter 2, it might really be something like 2.9.1 Exercise 1B.

There could really be many different ways to make the naming more clear. This is just one suggestion. Ideally, the naming convention for exercises would be the same for every chapter.

Thanks!

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

No branches or pull requests

1 participant