Bitemporal

Bitemporal Data Management handles historical data along two different timelines, making it possible to rewind the information "as it actually was" in combination with "as it was recorded" at some point in time. It facilitates the creation of complete audit trail of data.

  • temporal - commonly used for handling data involving time "as it was recorded"
    • Where did John Thomas live on August 20th?
    • Where was the Blue Van on October 12th?
  • bitemporal – handles data along two different timelines, making it possible to rewind the information "as it actually was" in combination with "as it was recorded" at a chosen point in time
    • Where did John Thomas live on August 20th as we knew it on September 1st?
    • Where was the Blue Van on October 12th as we knew it on October 23rd?

In MarkLogic 8, the following Bitemporal capabilities are available:

  • All operations are supported both in XQuery and Javascript, and in XML and JSON formats
  • set-up a temporal collection
  • CRUD: insert/update/delete temporal documents into temporal collection
  • Query: query against temporal collections: period-range-query (Allen operator with a period value) and period-compare-query (join like query) on temporal collection.
  • Ingest bitemporal documents through MarkLogic Content Pump (MLCP)
  • Set up configuration with REST API
  • Ingest and query with Java and Node API
  • Support for security roles and permissions

Next Steps

For more information see: http://docs.marklogic.com/guide/temporal

Comments