ER: Tools Data format is inconsistent with current data format

[Sebster3]

Emergent Requirement - Problem

In the project files at /_projects, we are currently storing tools data for projects in a csv

Tools: figma, photoshop, google drive

Technologies is being stored in yml array

Technologies

• Node.js
• React

Issue you discovered this emergent requirement in

• Add a Tools filter to the projects check page #4427

Date discovered

2023-04-13

Did you have to do something temporarily

• YES - put a hold on my issue until I get a decision
• NO

Who was involved

@Sebster3 @ExperimentsInHonesty

What happens if this is not addressed

We will have to do some jumping through hoops to make the filter work and that potential will be a problem later

Resources

Recommended Action Items

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

Potential solutions [draft]

Roll out plan

• Figure out what pages call the tools data
  • use the tools data
  • how they use it
  • what will need to change when we move to yml array
• Identify Issues that need to be made
  • P: An issue to make a template & Spreadsheet
    • E: Issue to make the project file changes issue (this issue assigns the person who will make all the project issues and gives them the template and spreadsheet to use)
      • Issues made from the template that changes the data in the project pages(fb) (many issues)
  • E: Create Issue to make the issues for changing the identified files from figuring out which pages call the tools data
    • Create the issue (fb) for each (non project.md) that needs a change
• Final process
  • Confirm that all the backend changes on the feature branch have not changed the way anything looks
  • merge the feature branch into the main
  • release dependency on Add a Tools filter to the projects check page #4427 and update the issue so that it reflects the current changes.

Make the parent issues (dont make the issues for each project file. That will be done by the person who gets that issue assigned).

[github-actions]

Hi @Sebster3.

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 the adding proper labels 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

[github-actions]

Hi @Sebster3, 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 :)

[ExperimentsInHonesty]

• @Sebster3 I noticed you are waiting for the merge team to move your issue Identify which pages call Tools data from each project #4525 forward. I added a time sensitive label and a note for the merge team. I will also add the issue the dev/pm meeting.

[t-will-gillis]

It appears that #4525 addresses this ER in full. Since that issue is "Closed as Completed", this ER should also be closed.