Post related comments

[uskudarli]

Need guidance to users as to how to enter. Dates etc. Should be with calendars that make this work easy.
But, in absence of that you want to tell users.

Also you don't want users to talk like computers (2020-06-13)   it is for communities. You can internally store that

but present human readable. This is SO common. Ready solutions are everywhere.

Request Method:	POST
http://100.27.5.146/instance/create/26
2.1.1
ValidationError
["'June 2 2020' value has an invalid format. It must be in YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ] format."]
/usr/local/lib/python3.8/site-packages/django/db/models/fields/init.py in to_python, line 1390
/usr/local/bin/python
3.8.3
['/appserver', '/usr/local/lib/python38.zip', '/usr/local/lib/python3.8', '/usr/local/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/site-packages']
Sat, 11 Jul 2020 13:34:37 +0300

---

Try 2. All field values (EXCEPT for Q codes) disappeared so I had to start over.
However, it shows an error that Q codes are required! See picture below.

---

Try 3 -- after also re0adding q codes

What kind of location is this?

[enderortak]

I tried to explain how location input works on this comment.

For the issues you reported, I totally agree. Because of the timing issues, we mostly focussed on the functionality of the "happy path", and had to spend less time on user experience.

[onebitme]

Dear @uskudarli , I totally agree what @enderortak said. As an addition maybe this can be helpful,
Adding location part from user manual:

[uskudarli]

I see, this is not a geolocation type. It is nice for visualization but not a data type.

[sinag]

I see, this is not a geolocation type. It is nice for visualization but not a data type.

Totally correct, what we have is just a workaround