Temporal Data Model Enhancements

Time

Current Implementation Every StoryLayer should have at least one attribute that contains a date-time field. This field should be in ISO 8601 format (2017-12-29T00:24:37+00:00) at any level of temporal resolution from within the full standard. The temporal resolution of the data should be respected upon import. Currently, mapstory supports up to two date-time fields; a start_date and end_date. Any changes to these temporal attributes should trigger any back end actions for dealing with time. (I.E. Updating the the datexd or datexd_parsed fields) Furthermore, Temporal data that contains mixed resolution (ie some features with only Year Data, and others with Year and Month) should convert to the same resolution. Two Examples of how to accomplish this are:

1. Maintain the coarsest grain resolution (ie drop the Month Data in the example above)
2. Convert the coarser data to finer resolution for the entire range of the sub-unit. (ie convert the start date in the above example to YYYY-01 and end date to YYYY-12)
3. Support data imports with time information extending to 4.5 billion years BCE

The user should have the option to select which method to use or be directed to the tools.mapstory.org data formatting tool.

Temporal Editing

Temporal editing involves changing the start-time or end-time information of a feature. Edits should be enforced at the same temporal resolution

Temporal Search (Eras, Ranges)

As a user, I expect to be able to find content based on the time periods I am interested in.

• Add layer-level temporal search filter to Layer and Story Explore tab using eras definitions from gazetteer
• Add layer-level temporal search filter to Layer and Story Explore tab using eras definitions from gazetteer
• Add time-range text box tool to Layer and Story Explore tab that allows users to narrow to Layers and Stories with time spans within the defined range

<< Previous Section | Road Map Home | Next Section>>