georgegriff / com3014 Goto Github PK

Determine a front end architecture/module design

decide on database design type and link up with data access objects

Implement hibernate into data model and interactions with hibernate into the DAOs

show that you can retrieve a project match for a user,

probably need some data in the database, should be coming v soon

allow AuthProvider::retrieveUser to handle thirdparty authentication iva linkedIn

may be easier to setup separate REST Service for OAuth login

Required mechanism:
in UI:
Click "Sign in through linked in" -> linked in
User sent a linked in oauth dialog to accept.
Linked will return and will call an oauth callback on the server with an Auth Token

Our server the communicates with LinkedIn token endpoint
we get a token back via a callback url

we then store the token in user account info along with refresh token (and maybe expiry time?)

our service can then call LinkedIn API on behalf of user

stuff

Design a basic user class that would interact with the database and create user objects to be consumed by the server

The matcher is currently being supplied with too much information. I.e peoples emails and project owner

Arrange a meeting to discuss the project with team

with source directories

Make the login screen pretty

Develop a spring REST service to retrieve data

only allow users to access the project profiles of project theyve created or projects that theyve matched to

implement passwords for the login system that map to database users

Design the basic layout of the Appication

Generate some projects and associate them with users (who created the project) in the database

optimise frontend assets and copy them into the deployment folder.

tiles with add button

generate some users in the db so we can create some test data

research and investigate different types and possibilities of implementations

some program that matches a project to a user...

Create a PUT endpoint for editing a project that belongs to a user.

A user should only be able to edit their own projects

set up session handling different users

Discuss how we intend to use github to manage the project

show that can retrieve set of possible users that match a project role

Service and REST Services

i.e. find matches for user

find matches for project

Dont want algorithm always running need to design in such a way that has a "cache" of available potential matches

REST service will pull from that cache, up to 20 matches, when frontend starts to run out of potential matches
subsequent rest calls will get the next 20, etc.

when the user/project accepts or reject, entry is removed from cache.

when cache is empty, or near empty, algorithm repopulate the cache.

refactor and improve matchmaking algorithm, develop in such a way that algorithm can work for user matching as well projects

Provide a way of linking a user (creator) to a project

Only allow users to view their own profiles

and potentially only profiles of their matches

depending on how easy is with spring, go t for https.

Look for tutorials on how to do implement login in spring boot

Get the maven plugin for frontend functioning, may break peoples environments

needs more up to date maven version than netbeans has.