Budget: 1000 UAH Deadline: 1 day
Hello. I have extensive experience in website development. What is your project built on?
Complete or redo the Python project "Web service for tracking employee working hours"
I am waiting for any proposals.
The developer who worked on this project has unfortunately disappeared, and we need to make corrections and updates to this project.
A web service for a company with more than 50 employees.
Functionality:
1. Creation of work schedules
2. Creation of vacations
3. Tracking of worked hours
4. Monitoring of vacation for the current + previous years
5. Access levels for department heads and administrators
6. Ability to select the reason for absence or overtime
7. Ability to add comments about the employee's work for each of their working days
8. Generation of reports in pdf format for the selected period
Several screenshots of this project
Budget: 1000 UAH Deadline: 1 day
Hello. I have extensive experience in website development. What is your project built on?
Budget: 1000 UAH Deadline: 1 day
Ready to collaborate with you if the web service is written in Django or Flask
Please write in private messages to discuss the details of the technical specifications
Budget: 27000 UAH Deadline: 30 days
Hello! We have an identical web application that not only allows tracking working hours, creating schedules, tracking vacations, and generating reports, but also includes functionality for automatic calculation of employee salaries. We know well how to organize and improve such a service.
We are ready to help finalize your project, make necessary adjustments, or adapt our experience to your needs. Let's discuss the details to find the best solution for your company!
Budget: 666 UAH Deadline: 7 days
Добрый день!
Готов помочь вам с доработкой и обновлением веб-сервиса для отслеживания рабочего времени сотрудников. Мой опыт в разработке на Python позволяет быстро разобраться в существующем коде и эффективно внести необходимые изменения.
Мои предложения по проекту:
Анализ существующего кода: Проведу аудит текущей версии проекта, чтобы понять структуру и предложить оптимальные решения для доработок.
Доработка функционала:
Улучшу создание рабочих графиков и настройку отпусков с учетом требований компании.
Добавлю или обновлю функционал трекинга отработанных часов с точными расчетами.
Настрою отчетность для генерации PDF за выбранные периоды.
Пользовательские роли и доступы: Перепроверю права доступа для руководителей отделов и администраторов, чтобы гарантировать корректное разграничение прав.
UI/UX улучшения: Если потребуется, предложу улучшения интерфейса для удобства использования.
Детальный отчет о проделанных работах: По завершении предоставлю всю документацию с подробным описанием внесенных изменений.
Буду рад обсудить детали проекта и согласовать сроки и стоимость выполнения. Со мной можно рассчитывать на прозрачность, регулярную обратную связь и качественный результат.
Жду вашего отклика, чтобы начать работу!
Budget: 7000 UAH Deadline: 7 days
Good day. I have a lot of experience in website development. What technologies does your website use? Ready to collaborate.
Budget: 6200 UAH Deadline: 6 days
I propose the following plan for the improvement or redesign of the web service for tracking working hours in Python:
Main functionality:
Work schedule: Creation and editing of schedules by managers and administrators.
Leave tracking: Management of leaves for the current and previous years.
Hour tracking: Automatic accounting of worked hours and overtime.
Access levels: Differentiation of access rights for administrators and managers.
Reasons for absence: Selection of reasons for absence or overtime.
Comments: Ability to leave comments for each working day of the employee.
PDF reports: Generation of reports for the selected period with details of working hours, leaves, etc.
Technical details:
Python/Django or Flask for development.
Database: PostgreSQL or MySQL.
PDF generation: ReportLab or wkhtmltopdf.
Interface: Bootstrap.
Authorization and roles for rights differentiation.
Proposal:
Code audit: Checking the current state of the project.
Improvement/development of functions according to requirements.
Testing and optimization.
Support after implementation and instructions for users.
Ready to discuss details, timelines, and budget.
Budget: 25000 UAH Deadline: 20 days
Good afternoon, I have experience working on web projects, Python flask/django, I would write from scratch since understanding someone else's code is difficult and not always efficient. Price and deadlines after the complete technical specification.
Budget: 5000 UAH Deadline: 5 days
Good day! I am ready to collaborate on this project. Could you please tell me what the existing code is written in? Is there an opportunity to review the code to understand what needs to be improved?
Опишіть ще також що вам треба, якусь конкретну задачу. А то не зрозуміло що потрібно
There is an active production platform with a catalog and automatic updates of external offers and prices. Stack: — Node.js / TypeScript; — PostgreSQL; — existing price refresh service and cron; — separate ready Python module for validation and selection of offers; — staging and production. It is necessary to make targeted improvements to the existing price refresh pipeline without completely rewriting the backend. MANDATORY SCOPE 1. Integration of the Python module — The Python module remains a separate component; — returns a structured result: offers, selected offer, statuses, and risk flags; — Node.js validates the result and performs a write to the database; — provide for error handling and partial/failed runs; — the legacy pipeline is not turned off until QA is completed. 2. Launch refresh by list Add launch: — by one slug/id; — by the provided list of slug/id. Assume CLI or existing service API. A new user interface is not required. 3. Shadow Mode New results must be recorded separately and not affect production until QA. Shadow fields required: — price; — selected offer ID; — direct URL; — offer status; — risk/QA flags; — checkedAt; — engineVersion. 4. Expanding the existing offers table Add: — source; — external_offer_id; — last_seen_at; — last_checked_at; — engine_version; — risk flags or storage in existing JSON; — unique constraint to protect against duplicates. It is not required to create a new parallel offer system if the existing table can be safely expanded. 5. UPSERT, STALE, and DB transaction Replace the current DELETE → CREATE scheme: — UPSERT existing and new offers; — offers missing in the full successful snapshot are translated to STALE; — in case of API error, partial result, or incomplete snapshot, active offers should not become STALE; — updating offers, selected offer metadata, and shadow fields for one model is performed within one DB transaction; — in case of an error, a full rollback is performed. 6. Canonical-safe refresh Price refresh should not change: — brand; — reference; — model; — collection; — name/title; — slug; — descriptions; — images; — SEO fields. Only offer, price, and shadow data are updated. 7. Preserving current cron logic Preserve: — existing cron; — rolling batches; — cooldown; — checking PRICE_REFRESH_MIN_DAYS before calling the external API; — legacy production pipeline until Shadow QA is completed. 8. Audit output One option is sufficient: — shadow columns in the existing admin table; or — CSV export. Minimum data: — model/reference; — production price; — shadow price; — delta; — production/shadow URL; — status; — risk flags; — checkedAt; — engineVersion. A new complex dashboard is not required. 9. Staging and QA — DB migrations; — staging deployment; — smoke test on 5 provided models; — then Shadow Mode on approximately 50 models; — fixing technical errors identified during these runs; — brief documentation of the Python → Node.js contract and rollback procedure. OPTIONALLY ASSESS SEPARATELY Simple technical promotion without a new UI: — promotion of one model by slug; — promotion of a list of slugs; — transferring confirmed shadow values to production; — technical check after rollout. RESULT — Pull Request; — DB migrations; — working integration Python → Node.js; — Shadow Mode; — UPSERT, STALE, and transactional update; — launch by slug/id; — staging deployment; — smoke-test results; — brief documentation; — at least 7 days of bug fixes for the implemented scope after acceptance. IN RESPONSE, INDICATE 1. Fixed price for the mandatory scope. 2. Separate cost for the promotion mechanism. 3. Timeline. 4. Hourly estimate. 5. When you are ready to start. 6. Experience with PostgreSQL transactions, migrations, and ingestion pipelines. 7. What questions need to be clarified before starting. 8. Whether staging, QA, migrations, and bug-fix period are included. Template responses without specific estimates will not be considered. Access to production is not provided at the first stage. Work begins with limited code review and staging.
A centralized server system for collecting and storing data from Planfix, 1C, Meta Ads, and Google Ads is needed, as well as a web dashboard for displaying and analyzing this data. All data, change history, calculations, and aggregated metrics must be stored exclusively in the server database. The dashboard should not store or duplicate business data. It must retrieve the necessary information from the server database via API according to user requests and display it in the form of KPIs, charts, tables, and detailed reports.
We are looking for support for a project based on Yii , we need to make edits and improvements to the database, there is partially a connection with the previous contractor .....................
It is necessary to migrate the database from CRM G-PLUS to MyChatBot Database volume - 26 thousand leads 2 funnels - Call center and Sales department with their own funnels Lead cards (besides name and number) have many different fields Leads also have voice recordings of calls. These also need to be transferred I expect an approximate amount and implementation timeline from the candidate
Create a dashboard for monitoring and analyzing the performance of the company's location network (branches) in Google Business Profile (GBP) through the official Google Business Profile API. Process via a script based on Google Apps Script (link to Google Sheets). Record data in Google Sheets (which serves as a database for Looker Studio). Update: Daily (with an indication of the last update date). Create a Google Cloud service account. The script runs once a day (trigger at 03:00 AM) and sends a request to the GBP API. It retrieves metrics for the previous day for each location (locationId). Records data in a flat format (row = unique combination of Date + Branch ID + Metrics). Key Performance Indicator CardsCard NameGBP MetricDynamic FormatProfile ViewsImpressions (Search + Maps)Percentage %, Sparkline (blue)CallsLocal Services Phone CallsPercentage %, Sparkline (green)Website ClicksWebsite ClicksPercentage %, Sparkline (purple)Direction RequestsDirection RequestsPercentage %, Sparkline (orange)Average RatingAverage Review RatingAbsolute change (e.g., +0.1), Sparkline (yellow)New ReviewsNew Reviews CountPercentage %, Sparkline (turquoise)