item_id: fk, int
borrower_id: fk, int
lender_id: fk, int
Approval: boolean #default false till borrower hit the button
Received: boolean #lender hit the button after receiving the item
return_date: date #expected_return_date

#to be decided
remove the column after the received=true or not

Useful resources:
https://guides.rubyonrails.org/active_storage_overview.html#amazon-s3-service
https://medium.com/alturasoluciones/setting-up-rails-5-active-storage-with-amazon-s3-3d158cf021ff
amazon s3 account: [email protected] password: 1234Uiop

help the user to reset password

register new user form
name: auth_users/new.html.erb

to be decided.

Allow users to log in with FB and TW

Send notification email to borrower on return day

Lender will be able to enter the available amount of a specific item

All the request should be via HTTPS. Redirect HTTP request to HTTPS

Create multistep of form filling when first sign up

name: borrow_reqs/edit.html.erb
Borrower can edit the request details
Auth: limited to the borrower who created the request

• This is a place holder for all the issues related to rating
  **** When working on this, create other smaller and workable issues

Address required when creating user

name: items/index.html.erb

• List all the items on the page (search page)
• filters can be applied

name: borrow_req/new.html.erb
Borrower specifies the following information about the request:

• intended borrow date
• intended return date
• message

Prototype a search bar for item index page.
Add advanced search which available for specified item name and status.

Connection between user_account and user_info

Creating new item

name: items/new.html.erb

The page acts as a user profile page...

name: users/show.html.erb
Auth:

• Everyone: can view: email, "My item: available"
• the user:
  • Manage user profile *
  • My item
    • Borrowed
    • Lent out
    • Saved
    • History
  • My friends < maybe not
    • Add
    • Remove
  • A search bar..?
  • notification

Things to revise

• names of entries have to make sense
• the naming format has to be consistent across tables
• double check the variable types
• dependencies between tables

Pages that require both contents and styling:

• Main page (before login) -COMMERCIAL! MARKETING! -first draft done
• User homepage - MARKETING! -first draft done

Pages that require styling:

• Item search result page (card view looks much prettier!) -first draft done
• User profile
  - show
  • edit/new -first draft done
• Borrow request/Lend message
  -show -first draft done
  • new in item -first draft done
    - new/edit
• item
  • show -first draft done
  • new/edit -first draft done

This is a placeholder task. Detail description will come when it comes to implementation.
Verify data before storing to table

• show errors on a pop-up instead of the body

name: borrow_reqs/show.html.erb
Show the borrow request detail
Auth:

• Borrower: can view, can be redirected to the edit page
• Lender: can approve/decline request

Implement session to keep track of user activities

Try with a random rails project and make sure the project can run on Heroku in the same way as it runs locally.

• Able to view the search items on google map
• Each item will be marked on the map using the owner's location

Use public gems search engine to enable searching for items

• figure out how to redirect to a user homepage after sign-in

List all the editable properties of the item

name: items/edit.html.erb

• this will populate the user related attribute in the item table
• prevent user from editing/destroying the record by checking the session

HTML skeleton for the home page under welcome controller
name: welcome/show.html.erb

Test the current models after implementation of basic views:
Make sure the data stored are of the correct data types.
Make sure the following actions succeed:

• new
• edit
• destroy

Some pages to consider:
• “About” page that describes the service and provides the history of BoLend (to explain why BoLend is so great).
• a page containing the terms of service
• a page describing the privacy policy
• a page with a site map
• a “Contact Us” page
• a page with a FAQ
• twitter, facebook, Instagram (for marketing purposes).

*** May want to place these pages into one folder under views, possible named something like "views/pages/"

user_details cannot reference to user_details table

HTML skeleton for some regular page under welcome controller
name: xxx.html.erb

• term of use
• about us
• private policy
• FAQ

Lenders can ask for deposit before lending itmes out

Emails will be sent to the owner upon

• a borrow request been submit
• a item has been returned

sent to the borrower upon

• Approval/Rejected on a borrow request

This page shows the item details
name: items/show.html.erb

Using Devise:users instead of our customized user_accounts.

Check out the user authentication solution
https://github.com/plataformatec/devise#getting-started

database

Users have to be able to log out their account