Add name and external_id fields to project_url

[fyliu]

Overview

We need to add name and external_id fields to the project_url table, which was decided here.

Action Items

• Add name and external_id field to project_url
  • ERD
  • Spreadsheet
  • Update Create Table: project_url #41 issue description
• check and release ER: docs: project url fields vs project_url #78 from ice box

Resources/Instructions

• add name field: What the link is called Ex: Primary Repo, Secondary Repo, Description of "other" type urls
• add external_id field: resource id provided by github or google
• both fields should be varchar(255) or CharField(max_length=255)
• external_id can be blank

[shmonks]

When submitting the PR for this issue, change the word 'fixes' to 'partially addresses'.

[shmonks]

Once assignee has completed the code portion, remove 'backend' label and put back in the Prioritized Backlog for db architect.

[dmartin4820]

• It looks like the project_url table has not been created yet as shown in Create Table: project_url #41.

[fyliu]

@dmartin4820 I guess this is more of a db design change issue than a coding issue.

Would you want to check that all the items are done and close it? The work would be working with issues and documents rather than coding.

Edit the issue description and replace the "code" step with "update #41 description". Then check that the 3 steps are done and fix or comment about them if they're not editable.

Looks like @Neecolaa already made the ERD changes. Please check that it looks correct and comment here if there's a problem.

The spreadsheet has a "fields" sheet with the table names and fields, and there's an initial data sheet called something like "projectUrls" that you should check. I started updating it before I realized it's something you could do to familiarize yourself with the document. But I'm not going to bother undoing them. Please just check to make sure it's correct.

The issue #41 description also looks updated. But I see a problem with one of the new fields that you can fix. The requirements are in this issue's description so you can check them one by one.

Lastly, check if #78 dependencies are satisfied and, if so, move its status from ice box to new issue approval.