Internal Integrated System Management
I extended institution/server management, maps, and statistics in an existing React/Spring MVC system, tracing state and data relationships before adding features and fixing operational errors.
- Role
- Development Team 2 · Frontend/backend feature extension and maintenance of an existing system
- Technology
PUBLIC RUNNING SCREENS
Operational screen record
Problem and approach
I took over an existing internal tool managing institutions, servers, schedules, and users for spatial-information systems. I extended it to support new system types and connected institution/server records with installation statistics. I first traced the existing state and data relationships, then applied focused feature additions and fixes.
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
Technical decision: understand before changing
The frontend relied on React class-component state, lifecycle methods, and this binding. I traced screen state changes and repeated logic before making changes. Rather than rewrite a running system with unclear operational impact, I added features in small units and simplified selected repetition within the existing structure. This taught me to understand current behavior and control maintenance scope.
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. Only one authenticated statistics screen is used as public evidence after identifying labels and detailed data were mosaicked; raw operational data, internal addresses, accounts, database values, license files, and non-public configuration are excluded.