-
Notifications
You must be signed in to change notification settings - Fork 9
Fixed $extratInfo typo and added a brute fix for last modification date on PDFs #72
Conversation
…e sample content I had on hand).
I put in place an easy way to normalize last modification metadata metadata into a corona:modDate element. Am also running anything that looks like a date through the date parser to (hopefully) get out xs:dateTime values. Typos also cleaned up. Thanks! |
Your solution is obviously MUCH more graceful than mine! I very much Any thoughts about making this usable outside of Corona? I think folks On Thu, Dec 15, 2011 at 12:39 PM, Ryan Grimm <
|
I'm getting an invalid cast as dateTime when I attempt to upload PDF's. On Thu, Dec 15, 2011 at 12:43 PM, Scott Conroy conroys@avalonconsult.comwrote:
|
I noticed a couple more formats that the date parsing library wasn't handling and added those. I suspect that the problem is in your range index. Is this an index that you created via Corona or the MarkLogic admin interface? I'm putting the parsed date into a normalized-date attribute and leaving the original content as a text node. So make sure that the range index is pointing to the attribute and let me know if that gives you some success. --Ryan On Dec 15, 2011, at 10:19 AM, Scott Conroy wrote:
|
Sorry, I just figured that out while you were emailing me. Much On Thu, Dec 15, 2011 at 1:33 PM, Ryan Grimm <
|
No worries. I just created a new issue (#74) to make it easier to create range indexes on binary metadata without knowing all of the details. --Ryan On Dec 15, 2011, at 10:44 AM, Scott Conroy wrote:
|
I'm finding several variations on the creation and last modification dates on different file types, but this fix works for the specific PDFs I have on hand.