There are projects actively using this. It was designed to allow you to overlay events for participants on a time line as well as data from datasets. It does have a bit of an API but it's not one we officially support, and I am not familiar with it. If this style chart fits your needs exactly then it probably wouldn't hurt to use, however, if you need something a bit more custom I would consider using something else, such as our new vis library. You could also possibly use our time charts, but I'm not sure what exactly your use case is.

The underlying library seems pretty stable, but tricky to customize. The hardest part was undoing their script dependency loading. It would be nice to use the resource dependency scheme you implemented.

If I were to re-implement this today, I think I would still use the same library for the main timeline. However, I probably would have integrated with the new LabKey charting package for the line charts (which wasn't an option at the time).

Let me know if you find a different package that does the same thing.

Matt

PS you can request a login to https://www.itntrialshare.org/ and check out their participant views to see examples.

As Matthew said, we still use it for some of our studies and it works well. The only thing I can add is that the Simile timeline does allow to have the time bands working on different but connected scales, which for instance allows one band to have days and another band to have months, and they stay synched as you scroll. Visually this is very appealing and data-wise you could see the benefit if you had a lot of events in a short time span. We've never implemented that functionality, but it's worth mentioning. http://www.simile-widgets.org/timeline/ shows a demo timeline with different time scales for different bands.

Dennis,

Thanks for the reply. Do you have a sense on the largest amount of data (#of records) you tend to show in a single timeline?

I just looked at the two queries filtered for one of the participants with a well-filled timeline. So, there are two queries for that participant's timeline which each come back with 376 rows, 3 and 4 data columns respectively (4 and 5 if you count the ptid column). In our case that timeline is shown in a psuedo-tabbed ext panel set, so there is maybe a 20 second load that the user wouldn't notice unless they quickly jumped to the timeline tab as soon as the page loaded. We've been pretty happy with the performance and clarity of it, and the fact that it can be nested inside ext components and still work well.

thanks.