No future dates should be present in metadata record
Open
validation-check
- Dominant language
- Python
- Stars
- 7
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Dates provided to the model should not come from the future. Use cases to prevent:
- prevent "Publishing" dandisets with assets from the future
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is identified. Start by locating the Python schema or model validation for metadata dates and determine how publishing dandisets with future-dated assets is currently permitted. Done means future dates are rejected and the publishing case is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100