Skip to content
Snippets Groups Projects
Commit b0543f25 authored by Sorrel Harriet's avatar Sorrel Harriet
Browse files

Adding marksheet

parent 447f5dd4
No related merge requests found
# Marksheet: Databases, Networks & the Web - Term 1 Lab Portfolio
| Student ID | Mark (/10) |
|-----------------------|-----------------------|
| msell010 | 6 |
---
## What your mark means
| Mark | Descriptor | Equivalent Classification |
|---------------|-----------------------|---------------------------------------|
| <4 | Unsatisfactory | Unclassified (fail) |
| 4 | Acceptable | 3 |
| 5 | Satisfactory | 2:2 |
| 6 | Good | 2:1 |
| 7 | Excellent | 1 |
| >7 | Outstanding | 1 |
---
## Marker Comments
Overall a good piece of work which has demonstrated some effort to adapt the example application. A number of comments to note below:
+ Data types: VARCHAR is prefereable to TINYTEXT due to memory overhead
+ You should include a statement to drop tables prior to creating them and your dummy data file doesn't contain much data - noticed afterwards there is an sql file in the root directory with drop
+ It would be helpful to include table headers in your views as some such as the inventory page to make clear what the columns represent. Also not clear what your Request page is showing.
+ Your repo contains a lot of unused files, should ideally only contain your app.
+ You have a db_connect script in the includes folder but you use the one in the root directory?
+ Not a good idea to hardcode the artists in the add records page. You don't need to start the transaction until you are manipulating the database in the postback section and you did not execute the select query which is probably no data was returned for the options
---
## Mark Grid
Breakdown of your marks. Marks are awarded out of 100 and divided by 10 to give you a scaled percentage.
**Please note, full marks will not be given where code bears a very close resemblance to that of the example app.**
| REQUIREMENT | Marks |
|-------------------------------------------------------------------------------------------------------|---------------|
| **BASIC** | |
| Application is well organised with a logical directory structure | 1/5 |
| Includes an .sql file containing a minimum of 4 TABLE CREATE statements | 5/5 |
| Includes an .sql file containing INSERT statements for adding dummy data to tables | 3/5 |
| Statements use correct SQL syntax and make appropriate use of data types | 4/5 |
| Statements include 2 or more logical foreign key constraints | 5/5 |
| Application is deployed at the URL specified in the README file | 5/5 |
| Application is navigable via a single point of entry | 5/5 |
| Application has a minimum of 3 distinct views | 4/5 |
| Successful use of `mysqli` or PDO extention to connect to database | 5/5 |
| Successful use of `mysqli` or PDO extention to query database | 5/5 |
| A table join is used in one or more queries | 5/5 |
| Application includes an HTML form which submits a POST request to a valid URL for processing | 3/5 |
| Form processing script executes some form of data manipulation statement on the database | 3/5 |
| Some basic methods of data validation are used in the processing script | 3/5 |
| **HIGHER LEVEL** | |
| A transaction has been implemented in the application | 1/5 |
| Evidence of extended learning (i.e. use of PHP functions/advanced SQL not taught on module) | 0/15 |
| Contributions have been made on forum | 0/5 |
| Regular commits have been made to GitLab | 5/5 |
| **TOTAL (UNSCALED)** | **62/100** |
| **TOTAL (SCALED)** | **6/10** |
## In case of concerns
If you require further clarification on anything mentioned in the marker's **comments**, or if you have a **reasonable complaint** about your mark, please email Sorrel (s.harriet@gold.ac.uk). Be aware that a minor adjustment to your mark may not affect the scaled percentage.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment