| 2010-12-02 01:52:03 |
paul.n |
description |
Three items from Provo --
classschedule19291930brig
classschedule19301931brig
classschedule19311932brig
had their date information changed from "1929" to a invalid date. This caused the item to have no date associated with it at all in the search engine.
What to do:
1) Change the date to be valid (valid formats below)
2) Confirm that this change has been made by replying to this bug report
For reference:
he valid formats for date are:
YYYY or YYYY-MM-DD or YYYY-MM-DD HH:MM:SS
anything other than that in the date field (like YYYY-YYYY) is going to cause problems - like no value entered at all in the search engine
in fact, that ("no value entered at all in the search engine") is exactly what has now happened with classschedule19301931brig. you can see here that the search engine now has a blank value for "date" for that item, because the value provided was in an invalid format:
http://www.archive.org/advancedsearch.php?q=identifier%3Aclassschedule19301931brig&fl[]=date&fl[]=identifier&output=tables
(assigning bug to Jeff Sharpe) |
Three items from Provo --
classschedule19291930brig
classschedule19301931brig
classschedule19311932brig
had their date information changed from "1929" to a invalid date. This caused the item to have no date associated with it at all in the search engine.
What to do:
1) Change the date to be valid (valid formats below)
2) Confirm that this change has been made by replying to this bug report
For reference:
"...The valid formats for date are:
YYYY or YYYY-MM-DD or YYYY-MM-DD HH:MM:SS
anything other than that in the date field (like YYYY-YYYY) is going to cause problems - like no value entered at all in the search engine
in fact, that ("no value entered at all in the search engine") is exactly what has now happened with classschedule19301931brig. you can see here that the search engine now has a blank value for "date" for that item, because the value provided was in an invalid format:
http://www.archive.org/advancedsearch.php?q=identifier%3Aclassschedule19301931brig&fl[]=date&fl[]=identifier&output=tables ..." - Hank
(assigning bug to Jeff Sharpe)
|
|
