We're currently building an application where some of the data (for legal reasons) have an extra dimension - time.

For instance, we have a bunch of locations that is owned by a single company. However, a location might be sold from one company to another, and the users need to enter when this takes in effect (in the future or the past) as well as see the history over time for these updates. The dates are important, due to the legal aspect of it all.

Do you have any examples / best practices when working with time in this way?

Right now I'm thinking of opening a new screen when editing this data, allowing to input updates in a table-like view along the lines of:

Update company for location: New York

  • Company Entity 1 - [DATE_FROM] -- [DATE_TO]
  • Company Entity 2 - [DATE_FROM] -- [DATE_TO]
  • Company Entity 3 - [DATE_FROM] -- [DATE_TO]
  • Company Entity 4 - [DATE_FROM] -- [DATE_TO]
  • Add new

  • "Working with" is very broad. Could you share exactly what you're looking for (data input methods, UI design, procedural UX, etc.)? – Alan Jul 20 '15 at 12:50
  • In this context, it's clear that "working with" means entering and modifying, and no doubt sorting chronologically. Anything else, @Laust-Deleuran? – JeromeR Jul 21 '15 at 8:50
  • @AlanGeorge, JeromeR is spot on - we're basically talking about the usual CRUD tasks. – Laust Deleuran Jul 21 '15 at 15:20
  • Interesting use case... I think the closest I've seen would be Linked In's edit profile page. The section where you input your positions has a "time period" field and that vaguely resembles this. You have "Add New Position" at the bottom. Clicking on each "Position" goes into edit mode with a period to adjust the time period. Seems like you may have an additional constraint where date ranges shouldn't overlap. If so, that'll be the toughest part to capture in the UI. – nightning Jul 21 '15 at 22:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.