Project

General

Profile

Actions

Feature #2157

closed

Dates: improved autocomplete

Added by Alexander Watzinger 4 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Category:
UI
Target version:
Start date:
2024-01-17
Estimated time:

Description

Like discussed in the last meeting we will improve the autocomplete functions of date fields:

If e.g. only a begin year is provided, a time span for this year will be created (instead just the first day of this year). The reasoning behind is that it is the more likely use case and it also prevents accidentally entering a precise date (year-01-01) instead of year range.

Additional information from Stefan from #2156:
If only a year YYYY is entered: set begin_from to 1.Jan.YYYY and begin_to to 31.Dec.YYYY (respectively for end_from, end_to) Same for month and day


Related issues 1 (1 open0 closed)

Precedes OpenAtlas - Feature #2156: Dates: change end data functionalityAcknowledged2024-01-18Actions
Actions #1

Updated by Alexander Watzinger 4 months ago

  • Subject changed from Dates: better autocomplete to Dates: improved autocomplete
Actions #2

Updated by Alexander Watzinger 4 months ago

  • Precedes Feature #2156: Dates: change end data functionality added
Actions #3

Updated by Alexander Watzinger 4 months ago

  • Description updated (diff)
Actions #4

Updated by Bernhard Koschiček-Krombholz about 1 month ago

  • Status changed from Acknowledged to In Progress
  • Assignee set to Bernhard Koschiček-Krombholz

Branch: feature/autocomplete_dates

So far, the dates work as described in the description.

One question is, how will we handle hour, minutes and seconds? Currently, I implemented it in this way, that a timespan from 00:00:01 to 23:59:59 is entered, which would be correct. But as a side effect, the dates will be displayed with hour, minutes and seconds, even if the module is switched off.
Another side effect is, that begin and end will always be a timespan unless year, month, day, hour, minute and second is entered.

So either we ignore time in this case for now, or we have to think about handling it.

Actions #5

Updated by Alexander Watzinger about 1 month ago

I would say we just do autocomplete for dates and ignore time. Time precision should not suddenly "appear" if people work with dates only.
In case someone uses time we shouldn't do an autocomplete because we could run into all kinds of issues there.

Actions #6

Updated by Bernhard Koschiček-Krombholz about 1 month ago

  • Status changed from In Progress to Closed

Thank you, I thought the same.

Feature in develop.

Actions

Also available in: Atom PDF