MokoConsulting/MokoJoomStoreLocator
1
0
Fork 0
Code Issues 11 Pull Requests Releases Wiki Activity

CSV import enhancements — column mapping, preview, and validation #27

New Issue
Closed
opened 2026-05-21 20:30:38 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-21 20:30:38 +00:00
Owner
Copy Link
Copy Source

Summary

Enhance the existing CSV import with an interactive column mapping UI, data preview/validation step, and robust error handling. The basic CSV import (issue #10) is functional but needs a production-grade UX.

Current State

Basic CSV import works with fixed column headers (title, address, city, etc.). Geocoding and update-existing options are functional.

Requirements

Column Mapping UI

  • Step 1: Upload CSV file
  • Step 2: Interactive column mapper — dropdown for each CSV column to map to a location field
  • Auto-detect common column names (Name→title, Address→address, Zip→postcode, etc.)
  • Support for ignoring columns ("Skip this column")
  • Remember last-used mapping (store in session or component params)

Preview & Validation

  • Step 3: Preview first 10 rows with mapped data before committing
  • Highlight validation issues per row (missing title, invalid lat/lng range, duplicate detection)
  • Row-level skip/include toggle
  • Summary: "X rows valid, Y rows with warnings, Z rows will be skipped"

Import Options

  • Match existing locations by: title, alias, or custom field (configurable)
  • Conflict resolution: skip, overwrite, or merge (fill empty fields only)
  • Category assignment during import (select category for all imported rows)
  • Default published state for imported locations
  • Dry-run mode (validate without inserting)

File Format Support

  • CSV with configurable delimiter (comma, semicolon, tab)
  • Auto-detect file encoding (UTF-8, Latin-1, Windows-1252)
  • Handle quoted fields with embedded commas/newlines
  • XLS/XLSX support via PhpSpreadsheet (optional, if composer dependency acceptable)

Progress & Reporting

  • Progress bar for large imports (AJAX-based)
  • Import result summary: imported, updated, skipped with reasons
  • Downloadable error report (CSV of failed rows with error messages)
  • Import history log in admin

Geocoding During Import

  • Batch geocode with progress indicator
  • Skip geocoding for rows that already have coordinates
  • Rate limit indicator (especially for Nominatim 1req/sec)
  • Option to queue geocoding for background processing

Acceptance Criteria

  • Non-technical admin can import a CSV without knowing the exact column names
  • Preview catches errors before they enter the database
  • Large files (1000+ rows) import without timeout
  • Import is resumable if interrupted
## Summary Enhance the existing CSV import with an interactive column mapping UI, data preview/validation step, and robust error handling. The basic CSV import (issue #10) is functional but needs a production-grade UX. ## Current State Basic CSV import works with fixed column headers (title, address, city, etc.). Geocoding and update-existing options are functional. ## Requirements ### Column Mapping UI - [ ] Step 1: Upload CSV file - [ ] Step 2: Interactive column mapper — dropdown for each CSV column to map to a location field - [ ] Auto-detect common column names (Name→title, Address→address, Zip→postcode, etc.) - [ ] Support for ignoring columns ("Skip this column") - [ ] Remember last-used mapping (store in session or component params) ### Preview & Validation - [ ] Step 3: Preview first 10 rows with mapped data before committing - [ ] Highlight validation issues per row (missing title, invalid lat/lng range, duplicate detection) - [ ] Row-level skip/include toggle - [ ] Summary: "X rows valid, Y rows with warnings, Z rows will be skipped" ### Import Options - [ ] Match existing locations by: title, alias, or custom field (configurable) - [ ] Conflict resolution: skip, overwrite, or merge (fill empty fields only) - [ ] Category assignment during import (select category for all imported rows) - [ ] Default published state for imported locations - [ ] Dry-run mode (validate without inserting) ### File Format Support - [ ] CSV with configurable delimiter (comma, semicolon, tab) - [ ] Auto-detect file encoding (UTF-8, Latin-1, Windows-1252) - [ ] Handle quoted fields with embedded commas/newlines - [ ] XLS/XLSX support via PhpSpreadsheet (optional, if composer dependency acceptable) ### Progress & Reporting - [ ] Progress bar for large imports (AJAX-based) - [ ] Import result summary: imported, updated, skipped with reasons - [ ] Downloadable error report (CSV of failed rows with error messages) - [ ] Import history log in admin ### Geocoding During Import - [ ] Batch geocode with progress indicator - [ ] Skip geocoding for rows that already have coordinates - [ ] Rate limit indicator (especially for Nominatim 1req/sec) - [ ] Option to queue geocoding for background processing ## Acceptance Criteria - [ ] Non-technical admin can import a CSV without knowing the exact column names - [ ] Preview catches errors before they enter the database - [ ] Large files (1000+ rows) import without timeout - [ ] Import is resumable if interrupted
jmiller added the type/featurearea/componentarea/adminarea/import-export labels 2026-05-21 20:30:38 +00:00
Sign in to join this conversation.
Labels
Clear labels
area/admin
Administrator interface
 area/component
Core component (com_mokojoomstorelocator)
 area/database
Database schema or queries
 area/frontend
Site/frontend display
 area/import-export
Data import/export features
 area/module-map
Map module (mod_mokojoomstorelocator_map)
 area/module-search
Search module (mod_mokojoomstorelocator_search)
 priority/critical
Must have for v1.0
 priority/high
Important for initial release
 priority/low
Future enhancement
 priority/medium
Nice to have for v1.0
 status: pending-testing
Implementation done, awaiting test proofs before close
 status: pending-testing
Implementation done, awaiting test proofs before close
 type/bug
Something is broken
 type/docs
Documentation
 type/enhancement
Improvement to existing feature
 type/feature
New feature or functionality
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels area/admin area/component area/import-export type/feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomStoreLocator#27
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?