Jeongdo UIT Integrated System Management
A maintenance project that added organization, server, schedule, user, and statistics capabilities to an existing internal geospatial-system administration tool and resolved operational issues.
- Role
- Platform Development Team 2 · Frontend and backend feature additions and maintenance for an existing internal system
- Technology
PUBLIC RUNNING SCREENS
Operational screen record
Overview
This internal operations tool consolidates organization-level installation and operating information for multiple geospatial systems supported by the company. It connects organization and server details, installation schedules, license-related files, users and permissions, and common codes, while presenting nationwide installation status by region and system type.
Frontend feature expansion
• Connected organization list, detail, registration, and editing workflows with schedule, statistics, common-code, and user administration screens using React 17, React Router, and Ant Design • Branched organization and server forms by system type and implemented server addition and removal, address lookup, validation, and license-file upload and download flows • Built OpenLayers 6 distribution maps that place organization coordinates over regional boundaries with system-specific markers and selected-organization details • Visualized installed and uninstalled status by region and system distribution with ECharts, adding system navigation and a collapsible statistics sidebar • Improved responsive and mobile layouts, search-state persistence, permission-based menus and actions, plus Axios authentication and error handling
Backend feature expansion
• Implemented and refined APIs for organizations, server settings, users, common codes, schedules, statistics, and map data using a Java 8 and Spring MVC Controller–Service–DAO structure with MyBatis and Oracle • Added transactional create, update, and delete flows that save each organization with either multiple servers or system-specific server settings, then assemble related data for detail views • Added aggregation queries by region, installation status, and system type, plus organization-coordinate queries consumed by OpenLayers maps and ECharts statistics • Connected Spring Security JWT authentication and BCrypt password handling to user approval, affiliation, and role-management workflows • Integrated multi-file upload and download and Apache POI Excel output for organization and server information
Legacy React in my first assigned project
This was the first project assigned to me after I joined the company. Although the frontend used React 17, it was organized around class-component state, lifecycle methods, and this binding rather than functional components and Hooks. Tracing page-level state and repeated code in an unfamiliar style was difficult. Instead of attempting a full rewrite, I first learned the existing structure and operational impact, added the required changes in small increments, and consolidated some repetition. The experience taught me how to read legacy code, control the scope of change, and improve a live system safely.
Feature additions, maintenance, and contribution boundary
The Git history from January through October 2024 confirms work on adding system types, integrating organization and server administration, system and regional statistics, address search and mobile screens, user affiliation and roles, maps and charts for additional types, and server registration and deletion fixes. I was not the original designer or builder; this record covers only the feature additions and bug fixes I performed on the inherited codebase as a member of Development Team 2.
Verification and publication boundary
The functions and technologies are grounded in the supplied frontend and backend repositories and their commit history. I confirmed that the operating page responds over HTTP and that its deployed frontend bundle matches the supplied local build. Authenticated operational data and screens are not used as public evidence, and internal addresses, accounts, database values, license files, and non-public configuration are excluded.