aznboy00 / biblio Goto Github PK

Styling fixes to the website

• General layout fixes
• Upgrade to bootstrap 4.1.3
• Implement partials (_header, _footer, _navbar) with EJS
• Convert PUG files to EJS
• Clean up views folder
• Clean up routes files

• Create classes in models and controllers (routers)
• Make sure the structure follows the class diagram and designs

To respect data persistence between the code and database, SQL queries execution should belong to the model/controller js files.

The password and other database connection credentials are being stored in /db.js. Even though the repository is private, in practice this poses a major security issue. The file should be removed from the repository, added to the .gitignore and manually pushed to the server.

• Remove db.js from the repo
• Add db.js to the gitignore
• Manually push db.js to the server

Implement the necessary methods through Express and CircleCI to implement tests.

• Register
• Login
• CRUD items
• Promote/Demote Users

Create a page for the user to view catalog items with a not-yet-implemented loan button next to the item.

loand_period should be called loan_period.

This needs to be changed in the descript.sql file and all subsequent model,route, and view files as well

Create a login page letting the user to enter their E-mail and password.
Return proper errors if it occurs.

Enable the loan button on the view item page to let the user loan the item. Make sure loan-able becomes false, and it won't show up on any search result and main catalog page.

Add the loan to the transaction log to track the loan and return status of an item.

*** HUGE TASK ***

Design the library's front end.

Create the following view model pages:

• Homepage (Library Browser to-be-done later in future sprints)
• Register
• Login
• User/Admin Control Panel
• Page containing the developers' information

• Navbar is not responsive on smallers screeen
• Tables (catalog, mangeusers) is not responsive on smallers screeen

Just wanted to share this with you all. I was just working on the view a single item page and realized that all together this is how many columns we have for all items (not too many):

1. title
2. author
3. artist
4. publisher
5. director
6. producers
7. label
8. actors
9. type
10. format
11. pages
12. language
13. release_date
14. run_time
15. asin
16. isbn10
17. isbn13

On top of item_id, discriminator, loanable, loan_period

Maybe we made the wrong choice? Maybe we didn't? We could squash four tables into one. Any thoughts? Switching to this type of database architecture might make it easier when it comes to loaning items as well.

• The user can search for a catalog title, isbn etc.
• The user can also sort the search result by price, A-Z, Z-A etc.

All the criteria will be discussed in the meeting.

Sessions should be created into its own class in a sessions.jsfile and referenced in routes/index.js,routes/catalog.js and routes/users.js similar to db.js. Instead of being instantiated in each file every time.

Create a registration form with fields that conforms the database structure.

Implement session checks (user being logged in or not) to show stuff for a corresponding user.

• Architecture Goals
• Architecture Constraints

As @WolfOfTheNorth mentioned during the meeting on Wednesday the 17th. What is everyones thought on restructuring the database as follows?

(moving quantity, loan_period, loanable, and title into the Items table)

Design a database in which aligns with the features that the website will have.
Database structure is subject to change.
Refer to the database design architecture to create the MySQL database.
Make sure the MySQL connection is properly coded and setup.

Refer to team meeting discussion for any other information.

The requirements documents specifies that Magazines are not loanable. As such, the loan period should not be modifiable. In other words, loan_periond should always be set to zero and loanable should always be set to false.

CRUD:
-Create #21
-Read #23
-Update #22
-Delete #24

.js files should not have the same name for a better readability for developers.

On the catalog display page, let any user be able to sort the catalog items by:

• Type
• Alphabetical Title/Author ASC, DESC (toggle)
  (These 2 are the most common characteristics)

Suggestion: if we have time, we could filter by category and filter more columns. (Nice to have)

Make the front end and backend to modify a specific entry.

route page should be: /admincp/edit/{entryid}
fetching the proper data off of the proper entry id

update button will submit the query to update the entry

Use Case #26

Design the frontend and backend with the proper field to enter a new entry to the catalog in Admin Panel.

Use Case #26

Our models are technically a mapper. I think all we would need to change in the code is the name of the director from models to mapper. And then change appropriate diagrams in the sad. The goal would be to follow the class diagram layers.

Create a page that populates a list of users online/offline that can only be accessed by the administrator.

Make the admin not being able to demote him/herself.

Remove quantity from the book, magazine, movie and music tables. Multiple copies of each item will each be contained in a row in the database. In other words, each item has its own unique id. This decision was made to reduce conflicts when loaning out items with multiple copies.

_{As discussed in the meeting on Oct 31.}

-Confirm with admin before deleting a record

users/admincp/manageusers page should not offer the ability to demote the root admin (user_id=1).

Within the user list, the admin has the option to promote a regular user to an administrator.
Return any proper error if it occurs.

Restrict access to admin privilege pages to Admin only.For example /catalog/createitems/createMovie is visible even when you're not logged in and can successfully create a new item.

• Insert new item page
• Update existing item page
• Promote Demote Users page

Make a page within the AdminCP to display all entries.

Use Case #26

Once CRUD is complete. Refactor to use Item.js to CRUD items, as discussed in the meeting Oct 31. Implement it to use some kind of an identity mapper/unit of work.

If an error occurs, make sure the code will output a proper error message instead of redirecting to the index page.

After having spoken to the TA it is confirmed that we are required to create all three:

• Identity mapper #124 (class notes, tutorial)
• Unit of Work #125 (class notes)
• TDG (class notes)

The Music table is missing the type attribute.

The dbscript, models, views, and routes need to updated.

Make sure only admins can edit stuff in the catalog.

Setup Circle CI
Add the build status icon to the README
Update README to reflect the fact that we are using CircleCI and not TravisCI

Don't declare the DB connection on every JS file.

Use Bcrypt for NodeJS for multi-platform compatibility.

Add a delete button on the Catalog page. On click it should delete the entry.

Use Case #26

@abdullahzen's fix in the last PR fixed the problem locally but is still giving build errors on the server. It looks like bcrypt is causing some issues.

there error is:
Error: /app/node_modules/bcrypt/lib/binding/bcrypt_lib.node: invalid ELF header

The branch heroku-build-fix contains some attempts at trying to fix it.

In order to run commands on the server type $ heroku run bash.

I have tried some of these commands with no luck:

$ rm -rf node_modules/;
$ npm install node-pre-gyp -g;
$ npm install bcrypt;
$ npm install -g npm;
$ npm install;
$ npm update;

The branch, populate-table is still working, just to have an idea of the last time the build was succeeding.

If you want to deploy a specific branch on heroku go to the project then click deploy and at the bottom of the page there's the option to deploy a specific branch.

• Implement the back-end code for usercp.ejs to be fully functional.
• Get the user values on the ejs file, then implement the back end method to update the data.
• Implement proper check before submitting the form.

***Must wait for #41 to be completed before starting this.

• Update, Delete, Create Items should belong to admin panel.
• Manage users should be on another page.
• Admin panel should be a page displaying the other pages.

The team members should have access to the script to reset the database.

The script is located in ./dbscript.sql
Run heroku pg:psql -f dbscript.sql

We should confirm the password before registering a new user to prevent password mistypes.

• update music is no longer working on master branch.
• /catalog/createitems/createMovie page is asking for a number as input for Actors, should be text
• /catalog/createitems/createMusic page is asking for a number as input for Labels, should be text

Here is a check list of stuff to do for the DB (initially)

Schema Preview

Click here to see it

ER Diagram

• Rough draft (for now)

Data Model

• Rough draft (for now)

DB Tables

• Users

  • Create Table
  • Script Template
  • Populate
     

• Transactions

  • Create Table (check how to implement itemId FK)
  • Script Template
  • Populate
     

• Books

  • Create Table
  • Script Template
  • Populate
     

• Magazines

  • Create Table
  • Script Template
  • Populate
     

• Movies

  • Create Table
  • Script Template
  • Populate
     

• Music

  • Create Table
  • Script Template
  • Populate