arangodb-community / arangobnb Goto Github PK

Evaluate reviews to determine the language and split them out into separate collections.
We would then link these collections to a view.

The purpose of this is to solve the problem of not know which languages your data contains and how to still be able to evaluate them with a single view.

The date picker will need to be made functional, is currently just a placeholder.

This will have some dependence on the backend and potentially overlap with #4 .

The AQL query that support #13 to allow for keywords to restrict the results shown. This may be a search over the description of the rental or whatever makes the most sense for the dataset.

KOA server and route creation. Please open any necessary related issues.

We will have queries that rely on natural language search and would need a more traditional search input. There is currently no placeholder for this component and it would need to be added.

This will be required for AQL #11

Once results are displayed will need to have filter options. How this is implemented is up to you, just needs to allow for selection keywords to narrow down results.

Just thought I'd open discussion about the structure of the actual project and what could work best.

What would you think about creating the project as a monorepo, using npm workspaces? This way we can maintain and develop each section in isolation without crossover- since technically, they all run in isolation in any case.

Could have a project structure like so, using a "root" package.json to define the workspaces:

/package.json
/workspaces/frontend-vue
/workspaces/frontend-react
/workspaces/backend-nodejs

/workspaces/common     (optionally, if there are shared enums and metadata etc.)

Inside each of these folders they maintain their own dependencies and package.json etc. This would allow us to all work on the master branch as well.

It will still be very easy to get started for newcomers, as we can still create npm scripts in the root package.json to allow people to quickly startup the backend- and their choice of either Vue or React- the default can still be Vue for the general npm run serve, or it could even run both frontends at different ports.

The current "Where to?" input needs to be functional. It is currently just a placeholder that does nothing.

This will have some dependence on the backend and potentially overlap with #4 .

Display AQL query being run in the component. This could be toggled on/off and likely displayed in a box along the bottom or wherever seems appropriate.

The current dataset we intend to use is here https://www.kaggle.com/brittabettendorf/berlin-airbnb-data?select=listings_summary.csv

This may need to change if we find it isn't able to fulfill some of the features we require for the project. However, the initial investigation looks promising.

We will need to model the data and once that is done we will update the readme to contain the working dataset.

Feel free to contribute to this as well if you have a suggested/preferred approach.

Nearby search to show available rentals near a specified address.

Create Foxx microservice to handle the necessary routes.

Note: We have decided on KOA for route handling but creating a Foxx microservice is a nice-to-have to draw comparisons between using a traditional backend service and Foxx.

Going to download and play with the dataset today. Just noticed when I got to the point of downloading ArangoDB from the site, I wasn't sure which version to go for (I know Enterprise would be okay either way) - but would be nice to know which version this project aims to be compatible with.

Also should clarify the minimum version number required for the project- I assume its 3.8 for the new geo features.

Map showing the neighborhoods and display rental availability. Primarily as a visualization but if further functionality, such as click on homes to get more details, can be added as a nice-to-have.

Need to determine the most appropriate view creation that will support desired AQL queries. Will need to come after query decisions.

It seems there has been some update that is blocking our search function as of this morning, it worked last night as is. We should investigate and more likely plan on fully using ArangoSearch for this instead.

127.0.0.1/:1 Access to fetch at 'https://nominatim.openstreetmap.org/search?q=museum&format=json' from origin 'http://127.0.0.1:8080' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Need to decide on a background image. Suggestions welcome, just need something the goes along with the theme.

This task may need to also encompass a suggestion for the colors and theme. Colors should consist of typical ArangoDB colors various greens, browns, but does not need to be dark theme, just whatever seems best.

The current guests functionality will need to be made functional, currently is just a placeholder.

This will have some dependence on the backend and potentially overlap with #4 .

Hi Al, I was testing the latest version of the repo, and the VUE front its not working. The API return status 500
AQL: unsupported SEARCH condition: 'ANALYZER' AQL function: Unable to lookup analyzer 'geo' (while optimizing plan)

After checking on the DB the analyzer geo do not exists, maybe I miss a step somewhere?

Thanks

Query that searches descriptions of rentals.

Ex: Places in Florida with a pool.

Need to display results from the query. Further issues may need to be made to fully support this. Please open as needed.

Update current placeholder for reservations and make it responsive to different screen sizes.