# Marksheet: Databases, Networks & the Web - Term 1 Lab Portfolio

|	Student ID	|	Mark (/10)	|
|-----------------------|-----------------------|
|		ma302ap	|			5|

---

## 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 an acceptable submission. You have managed to understand to some extent the example code provided and to produce a basic yet incomplete application. For next term you could focus on improve your understanding of data manipulation on the server side and transactions, as explained in the lectures. Further detail on the marking of your coursework below:

+ Scheme design: Very basic. Operations such as ‘on update’ and ‘on delete’ on the FK constraints are missing. 
+ Your 'add record' view does not seem to work. Therefore, neither does the form nor the transaction.
+ The transaction should have included an ‘insert’ statement to update the ‘inventory’ table.
+ On the transaction view, both links on the table bring you to the same view. This might be confusing for the user.


---

## 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				| 5/5		|
| 	Includes an .sql file containing a minimum of 4 TABLE CREATE statements				| 3/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			| 3/5		|
|	Statements include 2 or more logical foreign key constraints					| 2/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							| 3/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							| 3/5		|
| 	Application includes an HTML form which submits a POST request to a valid URL for processing	| 2/5		|
|	Form processing script executes some form of data manipulation statement on the database	| 0/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							| 3/5		|
|	**TOTAL (UNSCALED)** 										| **51/100**	|
|	**TOTAL (SCALED)**  										| **5/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.