Add Extra Inputs to DB Schema

[jacobvenable]

There are some extra inputs we're requesting from our providers that the current DB schema doesn't account for. We'll need to come up with a structure for these additional items.

Categories and Sub-Categories (completed)

~Categories are not specifically listed in the current schema. We should create a structure for labeling resources that belong to them.~

Contact Person Information

We are requesting a point of contact that can be separate from the contact information placed in the app. This would be for Upswyng to reach out about a particular resource. Items include:

• name
• email
• phone

Images (completed)

~Images are not currently part of the DB structure. We need to determine what the structure for the images will be. I"m good with it being something as simple as below.~

{
"images":[
    {
        "id":"123yvu1231bv23",
        "url":"https://lkwaefoweif.com/image1.jpg",
        "description":"brief description of the image"
     },
    {
        "id":"09nhgfnbdv212j",
        "url":"https://lkwaefoweif.com/image2.jpg",
        "description":"brief description of the image"
     }
]
}

~This structure would exist in each resource node (where images are provided).~

~We would also want to determine where these images will live, but this won"t necessarily stop dev from using placeholders.~

What should the client know before using your service?

Occasionally a service may have some tips helpful to using their service successfully. Some examples include:

• You must have a valid ID in order to use our service .
• To qualify, you must be of some age group.
• Etc.

[jacobvenable]

@rhinodavid Could we get images added next?

[jacobvenable]

Moved this out of MVP since the remaining items aren't needed for release.