Automatic Transmission Technical Database Module
Budget: $250 – $750 USD
I need a new “Database” module plugged directly into my current PHP-based internal platform for our automotive service shop. The goal is to give our technicians one central, searchable place for every automatic-transmission file we’ve collected—think DQ200, DQ250, 722.9, EAT6, JF015E and any future units we add.
Database structure
• Relational design that treats the transmission itself as the primary entity, not the vehicle.
• Each transmission record can own multiple child documents.
• Documents may be text, images/diagrams or video, and the system must preserve their original formats.
Organisation & navigation
Everything must be grouped “by transmission type” first. Within a transmission, technicians should still be able to filter or tag by document type when they need only PDFs, wiring diagrams, teardown photos, etc.
Search experience
Alongside normal keyword search, I want an AI-assisted search layer that can surface semantically related content (for example, a query for “clutch pack wear on DQ250” should highlight both text notes and tear-down images). If you prefer Elasticsearch, Meilisearch, or a PHP-friendly ML library, let me know—speed and relevance matter more than the specific tool.
Core deliverables
1. SQL schema and migration scripts
2. PHP classes/controllers integrated with my existing codebase for CRUD, upload and permissions
3. Front-end pages (plain PHP/HTML; our UI is Bootstrap 4) for browse, filter and AI search results
4. Setup notes so we can reproduce the environment on staging and production
Acceptance criteria
• I can create a new transmission record, attach at least one file of each supported type, and retrieve them without errors.
• The AI search returns relevant documents within two seconds on a dataset of 1,000+ items.
• Code is PSR-12 compliant and documented.
If you’ve built similar technical libraries or search modules in PHP, please share links or screenshots so I can see your approach.
Database structure
• Relational design that treats the transmission itself as the primary entity, not the vehicle.
• Each transmission record can own multiple child documents.
• Documents may be text, images/diagrams or video, and the system must preserve their original formats.
Organisation & navigation
Everything must be grouped “by transmission type” first. Within a transmission, technicians should still be able to filter or tag by document type when they need only PDFs, wiring diagrams, teardown photos, etc.
Search experience
Alongside normal keyword search, I want an AI-assisted search layer that can surface semantically related content (for example, a query for “clutch pack wear on DQ250” should highlight both text notes and tear-down images). If you prefer Elasticsearch, Meilisearch, or a PHP-friendly ML library, let me know—speed and relevance matter more than the specific tool.
Core deliverables
1. SQL schema and migration scripts
2. PHP classes/controllers integrated with my existing codebase for CRUD, upload and permissions
3. Front-end pages (plain PHP/HTML; our UI is Bootstrap 4) for browse, filter and AI search results
4. Setup notes so we can reproduce the environment on staging and production
Acceptance criteria
• I can create a new transmission record, attach at least one file of each supported type, and retrieve them without errors.
• The AI search returns relevant documents within two seconds on a dataset of 1,000+ items.
• Code is PSR-12 compliant and documented.
If you’ve built similar technical libraries or search modules in PHP, please share links or screenshots so I can see your approach.
Related categories:
PHP
SQL
MySQL
HTML
Bootstrap
Database Programming
Database Development
Elasticsearch