When parsing dates '-' character is deleted

[keithkade]

example: http://www.metmuseum.org/Collections/search-the-collections/488690

Other special characters are ok: http://www.moma.org/collection/browse_results.php?criteria=O%3AAD%3AE%3A28723&page_number=1&template_id=1&sort_order=1

[quyin]

can you also give the meta-metadata field that is involved, with type info
and full xpath?

Best Regards,
Yin Qu (屈垠)

On Tue, Jan 28, 2014 at 5:45 PM, Kade Keith [email protected]:

example:
http://www.metmuseum.org/Collections/search-the-collections/488690

Other special characters are ok:
http://www.moma.org/collection/browse_results.php?criteria=O%3AAD%3AE%3A28723&page_number=1&template_id=1&sort_order=1

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14
.

[keithkade]

scalar name="year" xpath="(//dd[preceding-sibling::dt[contains(text(),'Date:')]])[1]"/

[quyin]

The Met museum wrapper might not be working correctly now. @keithkade could you please check? Please also check if the bug still persists after fixing the wrapper, and update in this thread. Thanks!

[keithkade]

currently updating the wrapper. the bug is still there

[quyin]

is this field of type "String" or "Date"?

if it is "Date", it's possible that the date format is parsed into a java.util.Date object, and serialized into a slightly different format (without dashes) -- which means it's not a bug but a feature. but we might want to change the serialized date format if the use case requires.

[keithkade]

it is a string.

inherits from artwork.xml which has following definition:
scalar name="year" comment="Year the work was created." scalar_type="String"

[quyin]

that's weird. when you are done with the wrapper please reassign this to me and I'll take a look.

[quyin]

the dash character is unicode. so I suspect this is another manifestation of the unicode issue we were having.