scrapinghub / scrapinghub/dateparser
output precision for dates with incomplete data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 520
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 6
Description
Hi,
as you maybe know from my other issue i'm trying to parse date from an bibliographic database into an ISO8601 String.
This format is machine-readable and has the advantage, that if the data is incomplete, i don't need to fill it up with guessed Dates.
At the moment i find it quite hard to determine how precise the datetime object is, which i get out of the parser, and which dates are parsed and which are filled up over the 'RELATIVE_BASE' setting.
Wikidata has a nice Feature for their date-objects, the precision value: (see also: https://www.wikidata.org/wiki/Help:Dates )
It would also allow to parse Dates from a string like "19th Century" to a machine-readable date-object without loosing the information that its actually a date-range...
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
No files, tests, or entry points are identified in the issue, so first inspect the dateparser parsing and datetime-object APIs. Define how precision, values supplied by the parser, and values filled from RELATIVE_BASE should be represented, including incomplete dates such as “19th Century”; done when this information remains machine-readable without guessed precision being lost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100