Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#13 Decade breakdown oddity

open
chickmarkley
None
5
2007-10-24
2007-09-11
David Reynolds
No

Perform a simple search on "girard" and click on "break down results by decade". The title "Christian pamphlets; Vol. 7" shows up in the decade group "1800s" based--I assume--on a dateIssued of "1800-1856]-1856". On the other hand, the title "Destruction of $150,000, Girard, Ala." has dateIssued elements of both 1900 and 1920, but it does not show up in either of those decade groups. The same situation applies to the title "River of Whiskey".

There are 29 records returned by the original search, but only 27 show up in the decade breakdown. The two titles mentioned seem to be the only ones not accounted for.

Discussion

  • chickmarkley
    chickmarkley
    2007-09-12

    Logged In: YES
    user_id=1814905
    Originator: NO

    Christian pamphlets falls where it is because the CDL temper analysis determines 1800 as best fit, I suspect because of the one closing bracket. I believe that record to be also incorrectly coded because it has multiple dates within the originInfo with a keyDate attribute.
    Records may not have a parsable date, these will be dropped from a faceted search

     
  • Kat Hagedorn
    Kat Hagedorn
    2007-10-05

    • assigned_to: nobody --> khage
     
  • Kat Hagedorn
    Kat Hagedorn
    2007-10-24

    • assigned_to: khage --> chickmarkley
     
  • Kat Hagedorn
    Kat Hagedorn
    2007-10-24

    Logged In: YES
    user_id=1885374
    Originator: NO

    Still happening, because of multiple keyDates. How is this being handled?

    I assume the reason the date in display looks like this:
    Date 1800-1856]-1856 1800-1856 1856
    is because of multiple keyDates, and would normally not happen.

    However, this field should be labeled "Issue Date", not "Date" in display.

     
  • chickmarkley
    chickmarkley
    2008-01-08

    Logged In: YES
    user_id=1814905
    Originator: NO

    This is an implementation error and will be fixed next time items are regenerated on server.