openlibhums / openlibhums/janeway
Issue pub date shouldn't be required
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
The Issue date cannot be empty, which causes problems for imports (Import/Export/Update plugin) unless you include a full datetime string that the parser recognizes. The problem likely doesn't show up for normal submissions because the field defaults to now, but the importer doesn't make use of the default.
Describe the solution you'd like
Allow null values in the Issue model's date field
Describe alternatives you've considered
In the imports plugin, populate the issue date with datetime.now if the date provided in the CSV is not successfully parsed
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.
Research direction
Inspect the Issue model's date field and the Import/Export/Update plugin mentioned in the issue, starting by checking how empty or unparseable CSV dates are handled. Done means an issue date may be null and imports no longer require a parser-recognized datetime when the source date is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100