This is part one of a two-part assignment for 337. In both parts, you will be working on an online-marketplace app called Ostaa (Finnish for “buy” or “purchase”), along the lines of web applications such as OfferUp and Mercari. In part 1, the main emphasis will be on the server-side; getting the database schema set up, responding to various types of queries, adding new users and items, etc. You also have to write a very simple client (mostly for testing purposes). In part 2, you’ll build a more usable and complex client-side, and perhaps also make a few changes to the server code.
The ultimate purpose of the Ostaa website will be for users to be able to have an account, log in, and then post, view, and purchase items for sale.
You will need to have a database schema set up to store the necessary information on the server.
A real online marketplace would probably have a more complex database, but for this assignment, you will only need two document types: Item and User.
The schema should look similar this, though you are welcome to make additions or modifications if you’d like, as long as all of the same information is captured:
// Items
{ title: String,
description: String,
image: String,
price: Number,
stat: String }
// User
{ username: String,
password: String,
listings: [...list of item ids...],
purchases: [...list of item ids...] }
Notice how each user should have a list of listings and purchases. The listings are the ids of the items that this user has listed (posted) to the site for sale. The purchases are the list of the ids of items that this user has purchased.
For the purposes of this assignment, you’ll be required to have this server live via digital ocean, and you should include at least 4 items and at least 2 users populated already.
The server should support a number of different kind of requests (including static file requests). These request paths are:
/get/users/ (GET) Should return a JSON array containing the information for every user in the database./get/items/ (GET) Should return a JSON array containing the information for every item in the database./get/listings/USERNAME (GET) Should return a JSON array containing every listing (item)for the user USERNAME./get/purchases/USERNAME (GET) Should return a JSON array containing every purchase (item) for the user USERNAME./search/users/KEYWORD (GET) Should return a JSON list of every user whose username has the substring KEYWORD./search/items/KEYWORD (GET) Should return a JSON list of every item whose description has the substring KEYWORD./add/user/ (POST) Should add a user to the database. The username and password should be sent as POST parameter(s)./add/item/USERNAME (POST) Should add an item to the database. The items information (title, description, image, price, status) should be included as POST parameters. The item should be added the USERNAMEs list of listings.When working on these features, it should be fairly easy for you to test out the GET features (you can just type the URLs into the browser).
However, it might not be quite as straightforward to test the functionality to add users and items.
Thus, you’ll also be required to implement a very simple client, which can be used for adding these.
You should create a very simple, single-page client for this application. In part 2 of the assignment, you will create a more involved client. For now, the client it just going to be used as a page to test adding new users and new items (for particular users) to the database. You are welcome to get creative with the styling, but simple is acceptable also. See below for an example of adding a user and an item for that user.
As you are probably familiar with by now, this is what the apps file structure should look like:
/ostaa
> server.js
> live.txt
/public_html
> index.html
> ?.js
> ?.css
As with PA 7, for this project, you are required to get this application set up live on the internet, using digital ocean, as I have shown in the past.
You should include a file named live.txt in the same directory as server.js.
This file should have just one line in it, representing the address that your web app is running on, so that we can go and test it.
You are required to leave it up-and-running for at least 3 (72 hours) days after the assignment due date so that we can check.
Here are some other examples of various requests / searches using this Ostaa API/server.
Make sure that you take a look at the style guide on the class site before turning in your project.
You are required to use the express module to handle requests, and the mongoose module for database interactions.
You may use fetch or XHR for the AJAX requests.
You may work on this project in pairs.
You may not change teammates between PA 8 and 9.
For this assignment, you should create a zip file of the entire ostaa directory and submit that to Gradescope.
The project is due by 7pm on Monday, October 30th, 2023.