Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Implement Member Activities Aggregation

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Start by reviewing the three APIs named in the task—votes (표결정보), bills (발의법률안), and attendance (출석정보)—and compare their member identifiers, including the related context in #11. Define whether aggregation is feasible, then add tests covering successful aggregation, identifier mismatches, and fallback or clear-error behavior; no file or test path is provided.

Written by the indexing model from the issue text.

Description

Phase: 3 - Complex/Uncertain
Priority: Medium

Why Last: Requires aggregating 3+ APIs, uncertain if identifiers align.

Tasks:

  • Research if APIs share common member identifier
  • Map Service IDs (표결정보, 발의법률안, 출석정보)
  • get_member_activities(member_name) - aggregate votes, bills, attendance
  • Handle identifier mismatches gracefully
  • Tests

Acceptance Criteria:

  • Returns aggregated activities OR clear error if not feasible
  • Fallback to individual API calls if aggregation fails

Risk: High - might not be implementable if APIs use different naming.

Related to: #11

Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from StatPan/AssemblyMCP

All issues in StatPan/AssemblyMCP

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.