List view
- No due date•5/5 issues closed
Syfte: Det hade varit coolt och användbart att kunna söka på den nya hemsidan. Kunna söka på nyheter, events, eller kanske till och med i våra styrdokument. Overview: **1. Content Analysis** - **Website Content**: Go through and create records of the informations in the databases in the backend. For example, news, events etc. - **PDF Documents**: List all PDFs available on the site that need to be searchable. **2. Text Extraction** - **PDF Parsing**: Utilize libraries such as PyPDF2 to extract text from PDFs. **3. Indexing** - **Search Engine Selection**: - **Elasticsearch**: A distributed, open-source search and analytics engine. - **Algolia:** An alternative to do this, free to 1 M records and 10 000 searches. - **Data Structuring**: Organize extracted text into a structured format (records) suitable for indexing. **4. Backend Integration (Using FastAPI as the rest of the backend)** • **API Development**: Create endpoints to handle search queries and return results. • **Data Synchronization**: Ensure the search index is updated with new or modified content. **Additional tips:** - **Highlight Matching Terms**: Many search engines (like Elasticsearch) provide options to highlight matching terms in the results. - **Pagination**: Add pagination to avoid loading all results at once. Updates: ** 11/11 2024 ** I have decided to try to use elastic search for this implementation.
No due date•1/4 issues closedThis milestone is to build out the booking system of LC, Syster Kent and Alumnirummet (and hopefully more)
No due date•2/2 issues closedThis is a milestone make our new backend work with salto as we want it to do!
No due date•2/2 issues closedThis involves several steps which are outlined in the issues
No due date•3/3 issues closedHave a route to enable and disable fredmansky
No due dateFor this we need to have a route to store and retrieve documents and then make it compatible with the app
No due dateMake the backend compatible with the contacts page on the app. Will require the setting up of the new mail server which is a problem of unknown difficulty.
No due dateThis milestone is for everything surrounding the car
No due date•1/1 issues closedThese are the things that the database should implement: int? id; String? title; DateTime? starts_at; DateTime? ends_at; String? description; String? location; bool? drink; bool? all_day bool? food; bool? cash; //ska inte finnas, kommer läsas från price bool? closed; bool? can_signup; bool? drink_package; int? price; List<String>? dress_code; int? event_user_count; List<List<String>>? user_types; //SKA INTE IMPLEMENTERAS PÅ ETT TAG Contact? contact; int? max_capacity; String? dot; EventSignup? event_signup; EventUser? event_user; List<Group>? groups;
No due date•4/4 issues closedThis is the milestone to make the cafe functional in the app using the new backend
No due date•2/2 issues closedThis is the milestone to make the songbook functional in the app using the new backend
No due date•2/2 issues closedThis milestone is about the user backend routes, dbs and schemas. These are the member of the usermodel that we want to implement: We want the following in the get User schema: int? id; String? email; String? firstname; String? lastname; int? start_year; List? food_preferences; Should come from enum or something String? food_custom; String? phone; String? program; String? member_at; Maybe a datetime? String? student_id; bool? notify_event_users; bool? notify_messages; bool? notify_event_closing; bool? notify_event_open;
No due date•6/6 issues closed