Metadata Date Field Interface Limits

New post

November 21, 2017 15:41

Hello,

I have added a new Metadata template for our enterprise. The template contains a field with the type of "Date"

When I go to set the metadata field on any file, I am limited to about 10 years back. I noticed that if I mess a bit with the date picker, I can go even further back. It just takes a lot of clicking. If I have a really old date (say, 1950s) is there a better way to enter that in, maybe with a string value or by typing into any fields? I do plan to set some metadata through the API (which should theoretically work) but was looking for some work-arounds if any are available.

Thanks for your time!

Comments

4 comments

Murtza

December 08, 2017 13:56
Just to clarify, are you saying the API is limiting the value you can set for date field on metadata template to ten years, but in the web app you are able set it to an older date?
0

Comment actions Permalink
randolphj

December 20, 2017 13:08
Thanks for the reply .
When setting a date metadata field through the box web interface (not the API), the fields provided were limiting me to 10 years in the past. I found that through the user interface I could "inch" it backwards 10 years at a time.

Admittedly, I didn't follow up on this issue with the API since we changed our approach here to use a Number metadata field for tracking dates.

Just for future reference, it's my understanding that Metadata fields with the Date type can only go back to Jan 1, 1970. Is that correct?
0

Comment actions Permalink
pandacantante

February 14, 2018 13:49
Agreed this is a limitation. Why aren't you allowed to just type a date when setting metadata? Even setting dates that do show within the 10 year menu is painful. It's so slow to have to click through using a GUI for date selection.
0

Comment actions Permalink
wwb099

May 27, 2020 11:47
Hi - 2020 checking in, this is still a problem.
0

Comment actions Permalink

Please sign in to leave a comment.