feat: add a Little Green Light gift export reader (ingest preset)
メンテナーはふだん 1 日以内に返信
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 55/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- numpy, pandas, python, scikit-learn
調査の方向性
Read philanthropy/ingest/_raisers_edge.py and the shared aggregator in philanthropy/ingest/_civicrm.py; verify Little Green Light export fields and pledge/payment terminology against its public help center and API documentation before implementing. Add the reader, exports, CLI or preset registration, stability-tier row, changelog entry, and tests in the named files. Run the import check, make ci, and make riskcov; done means the required behaviors pass without adding dependencies or network code.
索引モデルが issue の本文から書いたものです。
説明
What's needed
Same pattern as the other CRM bridges in philanthropy.ingest (CiviCRM, Raiser's Edge, NPSP): a thin, CRM-specific header-alias map plus a commitment/payment exclusion filter, delegating the roll-up to the shared aggregator in philanthropy/ingest/_civicrm.py. This issue adds the bridge for Little Green Light.
Where to look
| File | Purpose |
|---|---|
philanthropy/ingest/_raisers_edge.py |
Closest existing example: header aliasing, a documented default exclusion set, delegation to the shared aggregator |
philanthropy/ingest/_civicrm.py |
The shared aggregator (civicrm_contributions_to_features, read_civicrm_contributions) and its private helpers |
tests/test_raisers_edge.py |
The test depth expected of your new tests/test_little_green_light.py |
philanthropy/cli.py |
_FEATURE_SOURCES and the features --source dispatch — wire your new source in the same shape, unless the read_gifts preset registry (a separate, in-flight PR) has already landed, in which case register there instead |
What to build
philanthropy/ingest/_little_green_light.py: a header-alias map from Little Green Light's real export labels (its gift/donation export) and API field names onto the canonicalcontact_id/receive_date/total_amount/gift_typenames; a documented default exclusion parameter for whatever its pledge-vs-payment split actually is (find out exactly how from the docs — do not assume it matches Raiser's Edge or NPSP); alittle_green_light_gifts_to_features(...)function; and aread_little_green_light_gifts(path)reader delegating toread_civicrm_contributions.- Verify every field name and every commitment/payment vocabulary term against Little Green Light's own public help center and API documentation before writing it down. Cite the doc URLs you actually used in your PR body, the way PR #233 does for NPSP. This issue does not assert any field name as fact — confirm everything yourself.
- Export the new names from
philanthropy/ingest/__init__.py(__all__, alphabetical) and add a stability-tier row todocs/reference/index.md(Tier 2/Beta — a test enforces every public symbol has a row). tests/test_little_green_light.pyat the depth oftests/test_raisers_edge.py: header aliasing from every spelling the docs name, the commitment/payment double-count trap and its exclusion, the exclusion set being documented/overridable/disabled byNone, currency parsing, schema/dtypes, empty input, missing required columns.CHANGELOG.mdentry under## [Unreleased], and add yourself toCONTRIBUTORS.mdif you'd like.
Hard constraints (same as the rest of this ingest series)
- Dependencies stay scikit-learn/pandas/numpy/joblib only — no new package, no API client, no network code anywhere in
philanthropy/. File-export reader only, never a live API connector. - No new estimator class.
- Build the exclusion logic from Little Green Light's own public docs only — never from an institution's actual configuration or data.
- Follow AGENTS.md's order: implement, export, verify with
python -c "...", then write tests, thenmake ci.
Verifying
python -m pip install -e ".[dev]"
python -c "from philanthropy.ingest import little_green_light_gifts_to_features, read_little_green_light_gifts; print('OK')"
make ci
make riskcov
Claim this issue with a comment before starting; a maintainer assigns within 24 hours.
- 主要言語
- Python
- スター
- 11
- フォーク
- 23
- 平均マージ
- 1日 8時間
- マージ済み PR(30日)
- 35
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
PhilanthroPy-Project/PhilanthroPy のほかの issue
-
enhancement help wanted roadmap
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
PhilanthroPy-Project/PhilanthroPy#345 ·
メンテナーはふだん 1 日以内に返信
-
beginner documentation good first issue roadmap
難易度 2/5 半日 初心者へのやさしさ 68/100
PhilanthroPy-Project/PhilanthroPy#342 ·
メンテナーはふだん 1 日以内に返信
-
beginner enhancement good first issue roadmap
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
PhilanthroPy-Project/PhilanthroPy#340 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 半日 初心者へのやさしさ 35/100
PhilanthroPy-Project/PhilanthroPy#357 ·
メンテナーはふだん 1 日以内に返信
-
documentation roadmap
難易度 2/5 1時間未満 初心者へのやさしさ 30/100
PhilanthroPy-Project/PhilanthroPy#352 ·
メンテナーはふだん 1 日以内に返信
PhilanthroPy-Project/PhilanthroPy の issue をすべて見る
似ている issue
-
Server mode OAuth2: 'NoneType' object is not subscriptable on every request after re-submitting the OAuth2 login while already logged in対応中かも @Rarasinhoo が今日担当しました。 オープン
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
pgadmin-org/pgadmin4#10733 ·
メンテナーはふだん 3 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
aws-samples/sample-per-model-bedrock#752 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
int-brain-lab/mpci#32 ·
-
area:docs priority:p2 type:docs
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
jejjohnson/geostack#120 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
sublimelsp/LSP-vue#203 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信