Skip to content

Move the commit for Jupyter Notebook from Access the Data repo to Data Science CoP repo #6139

Description

@JessicaLucindaCheng

Overview

We want to update the languages for Access the Data so that visitors to the website can find accurate and up-to-date information.

Action Items

  • Moving the commit for the Jupyter Notebook on access-the-data's repo to the Data Science Community of Practice (CoP) repository (repo).
    • Add the commit to the Data Science CoP repo
    • Remove the commit from the Access the Data repo
  • In a new comment below, identify and list any issues related to the Jupyter Notebook commit that needs to be transferred to the Data Science repo.
  • Once this issue is completed, go to Rollout Plan: Change code to read data from multiple project repositories #6138 and
    • Check off this issue under the Dependency section
    • If all the issues in Phase 1 of the Dependency section are checked off, move each of the issues in Phase 2 of the Dependency section to the New Issue Approval column and apply a ready for prioritization label to each of those issues.

Resources/Instructions

Activity

  1. github-actions commented on Jan 21, 2024

    @github-actions
  2. JessicaLucindaCheng commented on Jan 21, 2024

    @JessicaLucindaCheng
    MemberAuthor

    @ product

  3. JessicaLucindaCheng commented on Jan 21, 2024

    @JessicaLucindaCheng
    Author
  4. changed the title [-]Move the commit for Jupyter Notebook from Access the Data to Data Science CoP[/-] [+]Move the commit for Jupyter Notebook from Access the Data repo to Data Science CoP repo[/+] on Jan 21, 2024
  5. 246 remaining items

  6. hfla-graphql-app commented on Jun 19, 2026

    @hfla-graphql-app

    Hello @JessicaLucindaCheng!

    Please add an update comment using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of your issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last comment was before 06/05/2026, 01:44 AM PDT.

  7. hfla-graphql-app commented on Jun 26, 2026

    @hfla-graphql-app

    Hello @JessicaLucindaCheng!

    Please add an update comment using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of your issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last comment was before 06/12/2026, 01:10 AM PDT.

  8. added
    HLC: CHomepage Launch Countdown Could Have
    and removed on Aug 4, 2026
  9. hfla-graphql-app commented on Aug 7, 2026

    @hfla-graphql-app
  10. hfla-graphql-app commented on Aug 14, 2026

    @hfla-graphql-app
  11. hfla-graphql-app commented on Aug 21, 2026

    @hfla-graphql-app
  12. hfla-graphql-app commented on Aug 28, 2026

    @hfla-graphql-app
  13. hfla-graphql-app commented on Sep 4, 2026

    @hfla-graphql-app
  14. hfla-graphql-app commented on Sep 11, 2026

    @hfla-graphql-app
  15. hfla-graphql-app commented on Sep 18, 2026

    @hfla-graphql-app
  16. hfla-graphql-app commented on Sep 25, 2026

    @hfla-graphql-app
  17. hfla-graphql-app commented on Oct 2, 2026

    @hfla-graphql-app

    Hello @JessicaLucindaCheng-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last update was before 09/18/2026, 12:07 AM PDT PST.

  18. hfla-graphql-app commented on Oct 9, 2026

    @hfla-graphql-app

    Hello @JessicaLucindaCheng-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last update was before 09/25/2026, 12:11 AM PDT PST.

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

Metadata

Metadata

Labels

Complexity: MediumHLC: CHomepage Launch Countdown Could HaveP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)role: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 1ptCan be done in 4-6 hoursstatus: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions