Date Mapping

[SamiNorling]

In reviewing our mappings, I think it's worth revisiting the mapping of our date fields, if possible. In the IMA's objects data, we have three creation date fields:

date_created date_earliest date_latest

Often, these fields have the same value (e.g. "1961") but sometimes date_created can be more descriptive with date_earliest and date_latest serving to set the date range. For example,

        "date_created": "20th Century\/2ND HALF",
        "date_earliest": "1951",
        "date_latest": "2000",

As our date fields are currently mapped, only date_earliest and date_latest are mapped to E52_Time-Span1, with the properties E82a_begin_of_the_begin and E82b_end_of_the_end, respectively, and it looks like the value of date_earliest is set as the label of E52_Time-Span1, and that is what populates Creation Date in the Browse app.

Would it be possible to use the value of date_created as the rdfs:label of E52_Time-Span1? This would make our visible dates more descriptive, while still having defined xsd:date values for begin and end of the time-span.

If this remapping is possible, my clean-up of our data leading up to the refresh will include a review of dates with that mapping in mind.

[caknoblock]

We can easily change the mapping for the label of Time-Span1, but I would want to get a confirmation from either David or Vladimir that this mapping is a reasonable thing to do in this case.

On Jun 28, 2017, at 8:39 AM, Sami Norling notifications@github.com wrote:

In reviewing our mappings, I think it's worth revisiting the mapping of our date fields, if possible. In the IMA's objects data, we have three creation date fields:

date_created date_earliest date_latest

Often, these fields have the same value (e.g. "1961") but sometimes date_created can be more descriptive with date_earliest and date_latest serving to set the date range. For example,

    "date_created": "20th Century\/2ND HALF",
    "date_earliest": "1951",
    "date_latest": "2000",

As our date fields are currently mapped, only date_earliest and date_latest are mapped to E52_Time-Span1, with the properties E82a_begin_of_the_begin and E82b_end_of_the_end, respectively, and it looks like the value of date_earliest is set as the label of E52_Time-Span1, and that is what populates Creation Date in the Browse app.

Would it be possible to use the value of date_created as the rdfs:label of E52_Time-Span1? This would make our visible dates more descriptive, while still having defined xsd:date values for begin and end of the time-span.

If this remapping is possible, my clean-up of our data leading up to the refresh will include a review of dates with that mapping in mind.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/american-art/ima/issues/21, or mute the thread https://github.com/notifications/unsubscribe-auth/ABB-qUHr0wUwhqNwJcKCSYlwXMvarrj8ks5sInOrgaJpZM4OIJmt.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/american-art/ima","title":"american-art/ima","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/american-art/ima"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Date Mapping (#21)"}],"action":{"name":"View Issue","url":"https://github.com/american-art/ima/issues/21"}}}

[workergnome]

    That seems reasonable to me. 

[SamiNorling]

Suggest this issue be closed. I will go ahead and apply this change in our updated mapping.