Identify what is required for the website that VRMS provides

[FamousHero]

Overview

We are overfetching data from VRMS when creating the event and project pages. We should only receive the data we need to fufill page creation to ensure data privacy and security.

Action Items

• [ ] Find data provided by VRMS in _data/external/vrms_data.json
• [ ] Go through the code-base and find all references to this file
  • [ ] Check all event, project, and project meetings pages for references
• [ ] Note all data provided by vrms_data.json that is being used within the site
• [ ] Write your findings in a comment below this issue. Since there won't be a PR linked with this issue:
  • [ ] move to Questions/In review
  • [ ] Apply label "Ready for dev lead" to this issue

Merge Team

• [ ] After this issue has been closed, release the dependency on #7527

Resources/Instructions

• This issue was initiated by #6145
• Formatter to read json file
• Data File
  • File location
  • file raw
• Pages project data event data appears on
  • https://www.hackforla.org/projects/311-data (any project page like this) has event data
  • https://www.hackforla.org/events/ has event data
  • https://www.hackforla.org/project-meetings

info provided by VRMS

{ "location": { "city": "state": "country": }, "owner": { "ownerId": }, "brigade": "checkInReady": "_id": "hacknight": "name": "eventType": "description": "project": { "recruitingCategories": [], "partners": [ "Seeking" ], "managedByUsers": [], "_id": "name": "description": "githubIdentifier": "projectStatus": "location": "githubUrl": "slackUrl": "googleDriveUrl": "googleDriveId": "hflaWebsiteUrl": "videoConferenceLink": "lookingDescription": "createdDate": "__v": }, "date": "startTime": "endTime": "hours": "createdDate": "updatedDate": "__v": 0, "videoConferenceLink": }

[FamousHero]

@roslynwythe I'm going to keep this in draft until I make the large issue. Once I link this as a dependency I'll add the "ready for dev lead" label

[HackforLABot]

Hello @santisecco, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

[HackforLABot]

Hi @floydferrer, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[floydferrer]

i. Availability: M-F 10a-5p ii. ETA: 11/26

[floydferrer]

Had some questions clarified during the 11/26 standup, will need to adjust ETA to 11/27.

[HackforLABot]

@floydferrer

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, December 30, 2024 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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, January 6, 2025 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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, January 13, 2025 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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, January 20, 2025 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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, January 27, 2025 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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.}

[HackforLABot]

@floydferrer

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 10, 2025 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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 17, 2025 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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 24, 2025 at 11:05 PM PST.}

[HackforLABot]

@floydferrer

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, March 3, 2025 at 11:04 PM PST.}

[HackforLABot]

@floydferrer

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 Tuesday, March 11, 2025 at 12:05 AM PST.}

[HackforLABot]

Hi @Khinememe-Kyaw, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[Khinememe-Kyaw]

i. Availability: 4pm -11pm ii. ETA: 18 Mar

[Khinememe-Kyaw]

I don't see these two data on the site. I believe one for testing.

• location: city: Los Angeles state: CA country: USA owner: ownerId: '123456' brigade: Hack for LA checkInReady: false _id: 6514d16f609cb4002070f9b4 name: Test-EventName hacknight: Online eventType: Team Meeting description: Testing project: recruitingCategories: [] partners: - Josh managedByUsers: - Josh _id: 644748563212e6001fbca24a name: Testing description: testy location: www.test.com githubUrl: updated_github_address.com slackUrl: updated_slack_channel.com googleDriveUrl: updated_google_drive.com projectStatus: Active createdDate: '2023-04-25T03:26:14.482Z' __v: 0 githubIdentifier: Spiteless hflaWebsiteUrl: updated_website.com/test34 googleDriveId: update_google_drive_id23 date: '2024-03-07T06:00:00.383Z' startTime: '2024-03-07T06:00:00.383Z' endTime: '2024-03-07T07:00:00.383Z' hours: 1 createdDate: '2023-09-28T01:05:51.900Z' updatedDate: '2024-03-05T03:27:26.383Z' videoConferenceLink: example.com __v: 0

• location: city: Los Angeles state: CA country: USA owner: ownerId: '123456' brigade: Hack for LA checkInReady: false _id: 675f28ed5e2bad00286c3e11 name: 2024 Winter Social hacknight: Online eventType: Team Meeting description: '' project: recruitingCategories: [] partners: [] managedByUsers: [] _id: 5f4b48fb1127403d8c56aa07 name: Hack4LA hflaWebsiteUrl: 'https://www.hackforla.org/' createdDate: '2025-03-17T10:03:51.155Z' date: '2024-12-15T23:30:00.639Z' startTime: '2024-12-15T23:30:00.639Z' endTime: '2024-12-16T02:30:00.639Z' hours: 3 createdDate: '2024-12-15T19:07:25.639Z' updatedDate: '2024-12-15T19:07:25.639Z' videoConferenceLink: 'https://www.meetup.com/hackforla/events/297884803' __v: 0

[Khinememe-Kyaw]

Hey @t-will-gillis, I completed reviewing the JSON data and identified fields that are not being used on the site. I also see this Fix for "Schedule Monthly" Workflow #7994 but I am not sure if I have to do anything. Please let me know if there’s anything else I can do. Thanks!

[t-will-gillis]

Hi @Khinememe-Kyaw Thank you for working on this!

When I read through the related issues, I believe that the goal is this:

• The automation is scraping far more info into file _data\vrms_data.json than we need, for example this is the data that is being scraped for each project:

  VRMS data current

  

• However, this is far more data than we actually need to populate the "Events", "Project Meetings", and individual project pages on the Website.

• For example, the Events page is using project.name, name, data, startTime, and endTime (<-- check if that is correct), and the individual projects are using other pieces of data from the VRMS data.

• So the goal of this issue is to identify which data points we actually are using so that automations only scrape the VRMS data that the Website needs.

Along with the notes from the description above, it might help to search the code base for: https://github.com/hackforla/website/blob/gh-pages/assets/js/utility/vrms-events.js or utility/vrms-eventsjs to get an idea of the data that is actually being used.

Let me know if this makes sense or not- thanks!

[Khinememe-Kyaw]

@t-will-gillis Got it! I'll work on it this evening and reach out if I have any questions. Thanks!

[Khinememe-Kyaw]

@t-will-gillis I’ve checked in utility/vmrs-events.js, js/events and js/projects as well as the Hack for LA project pages (https://www.hackforla.org/projects/*). here are the data points that I’ve seen being used:

name date startTime endTime project.partners project.name project.description project.projectStatus project.location project.githubUrl project.slackUrl project.googleDriveUrl project.googleDriveId project.hflaWebsiteUrl

Please let me know what I can do next. Thank you!!

[t-will-gillis]

Hi @Khinememe-Kyaw Great- Thank you for your work on this! You have listed the VRMS data points that are being used on the website.

Closing this as successfully completed and releasing the dependency on the next step.