Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
projects/18 Student CV.md
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
109 lines (70 sloc)
4.89 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Student CVs | |
Build a website where users (students) can share their CV with employers. All CV data should be stored in a database. | |
--- | |
## Testing | |
You are required to create the following accounts to allow the system to be tested. All accounts should have the password `p455w0rd`: | |
1. `student1` | |
2. `student2` | |
3. `student3` | |
4. `student4` | |
All the student should have a valid CV on the system. | |
--- | |
## Feature 1 | |
The homepage can be viewed without logging in. Logged-in users should see a **My CV** link or button that allows them to add or update their own CV which should include the following data: | |
1. Their full name | |
2. A profile picture | |
3. A multiline summary paragraph for displaying on the home page, this should support the use of _markdown_ formatting and be no more that 100 characters long. | |
4. A detailed, multi-line description of their qualifications, this should support the use of _markdown_ formatting. | |
5. A detailed, multi-line description of their skills, this should support the use of _markdown_ formatting. | |
In addition to the data from these fields, the database should also store the following without prompting the user to enter the information: | |
1. The username of the logged-in user. | |
2. The date and time of the last edit. | |
If the user clicks on the **My CV** link in future the data currently stored in the database should be inserted into each form field. | |
> To demonstrate this feature and to prove that the form works correctly you will need to show that the data is being persisted correctly, either by running a database query or an API call depending on the platform and technology you are using. | |
## Feature 2 | |
The home screen should display summaries of all the CVs in the system. For each it should display: | |
1. The person's name. | |
2. A thumbnail photo. | |
3. The short summary. | |
4. The date the CV was last edited (but not the time). | |
## Feature 3 | |
Clicking on one of the summaries should load the full CV including: | |
1. The person's name | |
2. The profile picture | |
3. The multiline summary paragraph with any markdown formatting replaced with html. | |
4. The description of their qualifications with any markdown formatting replaced with html. | |
5. The description of their skills with any markdown formatting replaced with html.. | |
6. The date the CV was last edited (but not the time). | |
## Feature 4 | |
This feature requires you to make changes to the functionality: | |
1. The user profile should now include a full name, phone number and email address. | |
2. If a logged-in user views someone else's CV they should see a button **Contact person**. | |
3. This takes them to a _Send Message_ screen where they type in a message which will be sent to the CV owner. | |
4. The _Homepage_ should include a section which lists all the messages they have been sent plus the name, phone number and email address of the sender. | |
# Feature 5 | |
You will now implements features to help potential employers locate suitable candidates: | |
1. Each CV should include their location address and this should display on a map when the CV is viewed. | |
2. There should be the option for the user to include the highest [qualification level](https://www.gov.uk/what-different-qualification-levels-mean/list-of-qualification-levels) by selecting from a dropdown list. | |
2. There should be an advanced search screen where the person searching can enter the following: | |
1. The location of the job. | |
2. The minimum qualification level required. | |
3. Any skills required. | |
3. The results from the advanced search should be listed in order of relevance with the most relevent at the top. There should be the option to see the details screen showing the full CV. | |
---- | |
## Extras | |
In some assignment briefs you are given marks for the appropriate use of media and using sensors built into the user's device. | |
### Sensors | |
In some assignment briefs you are given marks for the appropriate use of sensors and sensor data. You should be implementing: | |
1. When a photo is requested, the user should have access to the device camera (if available). | |
2. When a user edits their profile page and CV there should be a set home button that captures the current geo-location and stores in in their profile. | |
3. When browsing CVs they should appear in the list with the nearest at the top. | |
4. The user should be able to see matching CVs on a map: | |
1. Clicking a pin show the student name and photo in a callout. | |
2. Clicking this bubble should take the person to the CV page. | |
### Media | |
In the requirements listed above you need to provide the user with the ability to upload photos. For the extra media marks you will need to expand this by: | |
1. Providing the user with the choice of uploading photos, video clips or audio clips. | |
2. Giving users the option to directly capture images, audio and video clips using the built-in camera and/or microphone if available. | |
### Data | |
There are lots of online RESTful APIs you can make use of when developing this system. You should consider: | |
1. [LocationIQ](https://locationiq.com) |