Comment 12 for bug 683953

There are 5 left from this list and only one: classschedule19691970brig
allows me access to the details page.

Jeff

> I thought I was replying directly to Jeff in my previous response. But
> since it's here, I should clarify a bit:
>
> * If invalid formats are entered via modify_xml, I think it would be
> helpful if the user was blocked from submitting or, more likely, a
> red-row generated. This way we would at least know there was a problem.
> * I'm actually not sure if it's possible to get a "master" list of all
> invalid date formats in all items. Looking closer at the link Hank
> provided, there is an easy way to get at least books which include a
> "-" in the date field. There are 126 found:
>
> http://www.us.archive.org/metamgr.php?&srt=updated&ord=desc&w_date=*-*&w_mediatype=texts&w_collection=americana&w_sponsor=Brigham*Young*University&w_scanner=scribe1.provo.archive.org&w_repub_state=4%20or%20-1&fs_date=on&fs_identifier=on&fs_mediatype=on&fs_format=on&fs_collection=on&fs_sponsor=on&fs_scandate=on&fs_scanner=on&fs_curatestate=on&fs_repub_state=on&fs_size=on&fs_noindex=on&off=0&lim=25
>
> There should probably be a project to find all invalid formats for other
> centers but I think there are ways to do it w/out Hank creating some
> master list like I suggested in my previous response.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/683953
>
> Title:
> Invalid date information in items
>
> Status in Internet Archive - Tech Support:
> In Progress
>
> Bug 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:
>
> "...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)
>
>
>
>
>