Todo:
1) Store events for a calendar in AWS -- This was actually once completed by @kaftand and @paul-rinaldi on a separate AWS account than what we now use
2) Store login information for users - cognito (<- amplify)
3) Store "services providers" (searchable by tag, name - RDS(more expensive), Aurora(more managed, less flexible) - compare -- SET UP THIS with Amazon RDS
1) ID (will need to be generated)
2) Label (Name, string)
3) Type (boolean - NonProfit(0) or ForProfit(1))
4) Program and Services (Names, Array of Strings)
5) Description (Multiple lines of text, String)
6) Tags (Multiple names, Array of Strings)
7) Address (Address, String)
8) Phone (Phone, String because of country codes or should we use number?)
9) Fax (Fax, String or number?)
10) Email (Email, String)
11) Website (URL, String)
Todo: 1) Store events for a calendar in AWS -- This was actually once completed by @kaftand and @paul-rinaldi on a separate AWS account than what we now use 2) Store login information for users - cognito (<- amplify) 3) Store "services providers" (searchable by tag, name - RDS(more expensive), Aurora(more managed, less flexible) - compare -- SET UP THIS with Amazon RDS
RDS should comply with http://docs.openreferral.org/en/latest/hsds/ ... need to look into Currently, we have fields:
1) ID (will need to be generated) 2) Label (Name, string) 3) Type (boolean - NonProfit(0) or ForProfit(1)) 4) Program and Services (Names, Array of Strings) 5) Description (Multiple lines of text, String) 6) Tags (Multiple names, Array of Strings) 7) Address (Address, String) 8) Phone (Phone, String because of country codes or should we use number?) 9) Fax (Fax, String or number?) 10) Email (Email, String) 11) Website (URL, String)