Publish a horizon for Samples keyword aliases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by locating the shared central removal table and both Samples legacy-keyword getters, then inspect their existing deprecation tests and request-mapping behavior. Add the single 2027-08-07 horizon and verify advisories, unchanged alias translations, the full offline suite, and the coverage gate.
Written by the indexing model from the issue text.
Description
What to build
Give the deprecated Samples camelCase keyword aliases one published removal horizon through the package's shared deprecation mechanism. The aliases were introduced on 2026-08-07; use 2027-08-07, matching the repository's one-year horizon convention.
Both Samples getters must read that date from the central removal table and continue accepting and translating every legacy keyword exactly as they do now. This ticket schedules the aliases; it does not remove them or change their wire spellings.
Acceptance criteria
- The central removal table contains one Samples-scoped horizon of 2027-08-07.
- Both Samples legacy-keyword shims emit advisories that name the usable replacement and print that horizon.
- No Samples deprecation still says only "in a future release."
- Tests obtain the expected horizon from the central table rather than duplicating the date literal.
- Every camelCase alias remains accepted and produces the same request as its snake_case replacement.
- Public signatures, parameter mappings, and Samples wire names are unchanged.
- The full offline suite and coverage gate pass.
Blocked by
None — can start immediately.
- Dominant language
- Python
- Stars
- 266
- Forks
- 63
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 19
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DOI-USGS/dataretrieval-python
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
DOI-USGS/dataretrieval-python#421 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
DOI-USGS/dataretrieval-python#415 · 1 comment · 1 reaction ·
-
ready-for-agent
Difficulty 4/5 3-5 days Newbie friendliness 42/100
DOI-USGS/dataretrieval-python#413 ·
-
ready-for-agent
Difficulty 3/5 1-2 days Newbie friendliness 68/100
DOI-USGS/dataretrieval-python#410 ·
-
ready-for-agent
Difficulty 3/5 1-2 days Newbie friendliness 72/100
DOI-USGS/dataretrieval-python#412 ·
All issues in DOI-USGS/dataretrieval-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100