ER: discrepancies in meeting data sourced from API calls to VRMS vs. `vrms-data.json`

[roslynwythe]

Emergent Requirement - Problem

Two discrepancies were noted:

1. meeting data sourced from API calls to VRMS (/events-check) do NOT show Civic Tech Jobs DEV meeting Wed 5-6 pm, but that meeting is displayed on pages using vrms-data.json as a data source (/projects/civic-tech-jobs or /events)
2. meeting data sourced from API calls to VRMS (/events-check) show Civic Tech Jobs DEV meeting Fri 2-4 pm, but that meeting is NOT displayed on pages using vrms-data.json as a data source (/projects/civic-tech-jobs or /events)

Note: Currently /project-meetings uses API calls to VRMS but will be modified in the near future to use vrms-data.json

Issue you discovered this emergent requirement in

• Refactored JavaScript files so that Events page sources meeting data from vrms_data.json #6815

Date discovered

5/7/2024

Did you have to do something temporarily

• YES
• NO

Who was involved

@roslynwythe

What happens if this is not addressed

Erroneous/incomplete meeting data may be displayed on the website

Resources

Screenshot of Civic Tech Jobs meetings in VRMS

taken on 2024-06-02

Recommended Action Items

• Make a new issue
• Discuss with team
• Let a Team Lead know

Potential solutions [draft]

Create an issue to identify the source of the discrepancy

• if the source is front end code that retrieves or displays meeting data, create a front end issue to fix
• if the source is back end code that retrieves or stores meeting data, create a back end issue to fix
• if the source is VRMS, hand off to that team

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels