: I have generic material that _contain_ dates: historic time lines, : certificates, news articles, forms, deeds, testimonies, and wildly : free form genealogical information. The dates have no specific : structure, obvious context, nor consistency.
identifying an extracting dates from bulk text sounds like a pretyt interesting analysys problem ... if you wrote a Tokenizer that could recognize dates, you could then format them using something like DateTools to ensure it would be easy to find them ... but Lucene Analyzers can not currently create terns in multiple fields - so if you wanted a special "date" field for each doc, you would have to extract those dates in a preprocessing step. if you aren't picky how your index is stored however, there is no reason why you can't have a single field with your "text" terms and your "date" terms ... you would just have to be careful to know the differnece in searching ... make your analyzer prefix all of your date terms with soemthing it would never let your regular terms start with (ie "__") and make sure you bear that structure in mind when creating your RangeFilter on dates. : Now this is where my personal knowledge of Lucene breaks down. : Assuming I can extract each date from a source's body and convert it : to a usable format, can a Lucene Date Field hold more than one date? fields can contain as many values as you want -- or none at all. : If the answer is yes, problem solved! I'll just pile on a ton of definitely yes. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
