• Trim your Data in a Spreadsheet using the =Trim() function (VIDEO Demonstration)

• Put your Data in THIRD normal form (3N) to reduce data redundancy and improve data integrity. Find the Columns that have duplicates. These columns will land up being other tables (use a new sheet in the same data file)

  • Remove the duplicates (Excel or Google Sheets)

  • A-Z the data

  • INSERT a column before and create an ID column that will be numbered 1 to ...

  • VIDEO Demonstration

• Using VLOOKUP or EXACT/MATCH (VIDEO Demonstration)

• Create your tables with no formulas

  • copy and paste without formulas

• Database Structure (VIDEO Demonstration)

• Make csvs (How to in MS Excel or Google Sheets) (VIDEO Demonstration)

• Database setup (here is some info on users defined for the database) (VIDEO Demonstration)

• import your data from MS Spreadsheets or Google Sheets csvs to your PHPMyAdmin database (VIDEO Demonstration)

Evidence of testing must be supplied showing that adding material to the database worked correctly with screenshots. See Checkpoint 1.

1. Linking data in related tables or nodes using queries or keys

JOIN tables in relational database

• A relational database is a collection of data items with pre-defined relationships between them. These items are organized as a set of tables with columns and rows. Tables are used to hold information about the objects to be represented in the database.

• A JOIN is a means for combining columns from one (self-join) or more tables by using values common to each (IDs)

2. Writing custom queries to filter and/or sort data (group by)

3. Using logical, mathematical and/or wildcard operators

Presentation of data is on a PHP/HTML Website.

Evidence of testing has been supplied showing that the various queries return the expected results.

Evidence of comprehensive testing has been supplied showing that adding material to the database works correctly and that the various queries return the expected results.

The examples above are indicative samples only

You MUST explain the relevant implications to achieve this standard. See at the bottom of this page for a resource for Relevant Implications for Databases, also see this page.

In an assessment, your implications can be recycled from the practice task provided you make changes where necessary so that your explanations match the outcome you are making.

Implications should include functionality, usability, accessibility, aesthetics, intellectual property and social. Example (The examples above are indicative samples only): Explain ...

• why copyright/IP needs to be honoured

• why the database/website needs to be easy to use

• why the information needs to be accessible.

You have asked a volunteer to test the database and has made improvements/changes based on this testing. Tests were made to ensure that:

• it is easy to use

• the display of the output is in a logical order that is easy to read and understand

• the queries make it easy to filter and extract required data from the database.

The examples above are indicative samples only

*When you set up your entry form, please put each field on a new line. This is different to our original wire-frame design.*

• We can allow users to add items to the database via a form

• We can check that user input is validated using html

• Alternately, responses can be validated using php which gives us more control over the formatting and error messages (this is covered later in this ePub (E)

For example* (partial evidence):

• Any images that are used in the outcome are cited in the supporting documentation and are either original artwork or creative commons/public domain images.

• The information is accessible (e.g. images have alt tags and student has checked that site is readable for colour blind users).

*The examples above are indicative samples only

For example* (partial evidence):

They changed data types of some of their fields to ensure all data was using an accurate data type.

They ran a series of test queries and corrected the table structure to ensure the queries could link data from more than one table, including:

• testing of potential SQL queries that include SELECT and JOIN statements

• testing of PHP output when using connection and queries.

You carried out usability tests at key points during the creation of the database to ensure that it was fit for purpose and easy to use. They used information from testing at each point to improve and refine the outcome. For instance, they checked that:

• the input form was easy to use and that the error messages were visible and easy to understand

• query results were easy to understand

• searching was easy for users (e.g. users could easily run the queries based on the structure of the data).

*The examples above are indicative samples only

For example* (partial evidence):

There are no grammatical or typographical errors. The layout demonstrates effective application of design principles.

• The selection/sorting features of the webpage are obvious.

• The web indicated the current selection/sort being performed by the user.

• PHP Validation Rules present

*The examples above are indicative samples only