New Function #17
openNew Function #10: {API] 사용자 API 개발 (USER API development)
[API] Log
Description
1.[API] Exhibit (Log excel sheet on #10)
- 1) User location log
- 2) User statistics
2.Git
- nmkpg_cyber_user
Related issues
Updated by Deca Park about 2 years ago
- Copied from New Function #15: [API] Exhibit added
Updated by Toby Pham about 2 years ago
- Status changed from In Progress to Resolved
- Assignee changed from Toby Pham to Deca Park
Updated by Deca Park about 2 years ago
- Status changed from Resolved to Feedback
- Assignee changed from Deca Park to Toby Pham
1.POST /user_log
1) logic
- if user_id & log_time (PK) is already existed, UPDATE it (if not, INSERT)
2.GET /stats
1) response
a) total_move_distance / avg_move_distance
- value is float (until 2 decimal point) (currently, integer is returned)
Updated by Toby Pham about 2 years ago
- Status changed from Feedback to Resolved
- Assignee changed from Toby Pham to Deca Park
Updated by Deca Park almost 2 years ago
- Status changed from Resolved to Feedback
- Assignee changed from Deca Park to Toby Pham
[Test Issues]
1.API (/api/stats)
1) response
- although user log data exists, reponse > dashboard is returned with NULL wrong
- dashboard.avg_move_distance : set value until 2 decimal point (ex: 15.12)
Updated by Toby Pham almost 2 years ago
- Status changed from Feedback to Resolved
- Assignee changed from Toby Pham to Deca Park
Updated by Deca Park almost 2 years ago
[Test Issues]
1.API (/api/stats)
1) logic change
a) avg_stay_time
SUM(stay_time) / COUNT(DISTINCT user_seq)
FROM st_user_log
WHERE user_seq != {param user_seq}
b) avg_move_distance / avg_view_count
- similar with 1.1).a)
2) response > avg_stay_time / avg_move_distance / avg_view_count
- set value until 2 decimal point
(currently, avg_move_distance is not applied)