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

[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

• This issue is tracked in Rollout Plan: Change code to read data from multiple project repositories #6138

[JessicaLucindaCheng]

@ product

• I was already working on the action items in this issue. See Add additional repo(s) for project: Access the Data #5127 for previous comments and progress update history. Thus, I have self-assigned this issue already.
• I wrote this issue because I didn't want to overwhelm the comment history in issue Add additional repo(s) for project: Access the Data #5127 with my progress updates for something else.

[JessicaLucindaCheng]

Reopening issue because merged prs prematurely closed this issue when it still had action items remaining.

[JessicaLucindaCheng]

Progress Update

• Progress:
  • The Workshop-Feedback_Bigram_Analysis.ipynb has been added to the Data Science repo and the pr to remove it from the Access the Data repo was merged.
• Blockers: None
• Availability: TBD
• ETA: TBD

Action Items

• 1. move the commit for the Jupyter Notebook on access-the-data's repo, to the Data Science Community of practice repo. If you need write access to the data science repo, please let me know by adding this to our agenda. Use instructions from: https://www.elliotblackburn.com/cherry-pick-git-commit-across-repository/
  • Add Workshop-Feedback_Bigram_Analysis.ipynb to the Data Science repo
    • Created pull request: Moving Workshop-Feedback_Bigram_Analysis.ipynb from access-the-data repo data-science#188
      • Needs to be merged (recommend using rebase & merge)
  • Remove Workshop-Feedback_Bigram_Analysis.ipynb file from access-the-data repo
    • Created pull request: Delete Workshop-Feedback_Bigram_Analysis.ipynb access-the-data#296
      • Needs to be reviewed.
        • Asked Sophia Alice through a Slack DM on November 16, 2023. No response from Sophia.
        • Attend the Data Science CoP meeting on Monday, January 22nd at 7pm to ask Sophia Alice.
        • Await the pr to be reviewed by Sophia.
      • Needs to be merged.
        • Ask AJ Price
• 2. identify any issues related to the commit, so that Bonnie can transfer them to the data science repo.
  • Ask AJ to identify and give a list of issue numbers that are not related to CKAN and are part of the workshop bigram analysis. So that Bonnie can move the issues to the Data Science repo. Example: issue Research Plan: Data Expert Persona  access-the-data#163.
    • Slack messaged on Thu, Jan 25, 2024.
    • Responsive received Fri, Jan 26, 2024. Notes from response:
      • "Luis, who made your example issue, was not using Jupyter Notebook, he was doing persona research using Figma, not a bigram analysis."
      • AJ doesn't know anything about the work going on so can't help with finding the issues.
    • Write an issue in the AtD repo
      • Bring this issue back to the Dev/PM meeting for Bonnie to review

[HackforLABot]

@JessicaLucindaCheng

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "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 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 #hfla-site 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 Monday, January 27, 2025 at 11:04 PM PST.}

[HackforLABot]

@JessicaLucindaCheng

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "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 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 #hfla-site 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 Monday, February 3, 2025 at 11:04 PM PST.}