Skip to content

Consider adding instructor notes for good db design/the quirks of the data #99

Open

Description

@JordanPedersen

@librarianlise is also interested in giving more context about the data (at least to instructors so they can use the information at their discretion). Examples include:

  • certain results can look weird, but it's actually just the data set (i.e. there are many issues to one journal, and the other journals all have one issue)
  • time permitting, how it could be valuable to talk about better ways the database could be structured (i.e. a separate subjects table)

Activity

  1. librarianlise commented on Feb 5, 2020

    @librarianlise
    Contributor

    I noticed that the possibility of a separate subjects table is brought up in section 9 (which we didn't teach) so something to consider when we get to this issue.

  2. jyssy commented on Aug 7, 2020

    @jyssy
    Contributor

    @JordanPedersen I like this idea. I think putting this at least here: https://librarycarpentry.org/lc-sql/guide/index.html, would be useful. Is that something you think makes sense? Sort of adding as FYI, as questions may arise?

  3. librarianlise commented on Aug 14, 2020

    @librarianlise
    Contributor

    @jyssy that is indeed what Jordan and I were thinking. 👍

  4. self-assigned this
    on May 14, 2021
  5. jyssy commented on May 14, 2021

    @jyssy
    Contributor

    @kristindawn plans to work on this during May 14 2021 sprint.

  6. jyssy commented on Mar 18, 2022

    @jyssy
    Contributor

    @kristindawn just checking on this issue - finally getting into issues after a while. Still making progress. Do you need anything? thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions