The build system is currently Microsoft specific and also requires a JRE to be installed for the google closure compiler. These dependencies limit who can use it and also make it difficult to get started. There is a lot of momentum behind using Grunt (which depends on Node.js) to do Javascript builds now because it runs everywhere and has a great package management system to install dependencies. Moving to grunt would reduce your dependencies to just Node.js (which many people already have) and give you cross platform. I would be happy to explain how this works if you like and even do the work

YouTube for example.

Hey, great work!
Is there a way that can add/delete entry in a loaded timeline?

Hey,
I cant make it run in my localhost.
Uhm.. there is no error showing in my chrome console.
Just a ajaxloader keep loading something.

http://www.lfffoundation.com/article/timeline/id/78

http://www.makepublic.uk/campaign-timeline/8

Can you have a look at what might be happening here?

Timeline is brilliant, but it would be great to have greater control of the zoom level so that timelines spanning a short time period but with many events (e.g. 1939-1945) don't display in an overlapping lump.

Is there a way this can be achieved, so that the zoom level can be increased right down to a single month, and also set at a high zoom level by default?

Is there an option/workaround for vertical timeline?

/cc @edsilv

Nice project! ✨

This timeline predates the IIIF Presentation API (or at least, Wellcome's use of it).

However, the data model (label, description, images, image services, dates) maps nicely to a IIIF manifest, or a collection. It would be good to drive the timeline from a manifest or collection, to give a different/alternative/interesting rendering of IIIF material that has date info available.

The is useful because lots of people already have the material as IIIF, they don't need to do too much to manage new timeline data. Any ad hoc IIIF resources, for storytelling can be stored in a Presentation API server if necessary. For example a IIIF Collection created specifically to sequence a set of works for a blog post.

I would add an extra, optional, timeline-specific service to provide the "loose" date format the timeline supports (e.g., Romans leave Britain: 410 CE) for which IIIF navDates (“YYYY-MM-DDThh:mm:ssZ”) are inappropriate. Lots of people would be be happy driving a timeline off of navDates only, so if that's all there is use that; otherwise, get the more historical friendly date format, without misleading precision - provide this as a service extension.

Use cases:

1. Display of newspaper issues, periodicals, etc - likely to already to have navDate anyway, and be in Gregorian calendar to boot. Show highlighted front pages from a particular journal. Easy win.
2. IIIF Collection of works by particular author/creator - see timeline of published novels; paintings by artist over career, albums, etc (David Bowie albums with covers on timeline)
3. Archival items over the course of a career; thumbnail service on item-level manifest gives appropriate highlight (see also https://groups.google.com/forum/#!topic/iiif-discuss/2pKcLuxic4I); trace emergence of ideas from an ad-hoc IIIF collection (links between manifests/canvases as hotlink annotations to reconstruct correspondence). Trace emergence of scientific ideas through correspondence over time.
4. other cool stuff. Any collection, manifest or canvas level search results returned as IIIF collection (see IIIF Discovery) could be rendered on a timeline if date info available.

Hello,

I forgot to post about this :

We have used the Wellcometrust timeline for one of our projects. It was published in autumn 2017, you can see it here (in french, there could be geographic restrictions also).

The events are also discoverable from our main application (indexed in a SOLR database, you can see it here.

The « app » is hosted in a angular app and there is communication between both app to share data and functionality. The backend the « editors » are using to create the events is an Apex application.

I fixed a few bugs and added a few functionnalities that where requested for the needs of the project, like « filters » to be able to select a subset of events (implemented client side but using some precalculated data / index, a second source of data). The SOLR indexation was added after the autumn release, we could probably add a filter based on text content or facetted search now.

The timeline library / app worked well overall, I tought the code quality was pretty good. On the negative side there are performance issue when there is alot of events and I was not able to fix it without introducing some issues in the animation. Also, the model of « hidden » events and how zoom affect the result is sometimes hard to understand, we have added the display of a informative text to help the understanding.

Our project budget doesnt let us go further in improving it but the rendering of the events and animation could surely benefit from a rewrite.

Thanks for sharing the sources of timeline!

Hello,

I have to integrate Timeline in our Angular application (a copy that we will customize) that have it's own deployment constraints (and I also need to be able to test on a local server setup and a shared server) and encountered a few issues. I will be able to fix that but I wanted to share the information in case that would be usefull to someone else.

1. The loading of files expect a precise folder organisation. It's not possible to move all the files within a common "Timeline" folder. By ex. domain/build/. It's problematic in our case because I have to mix the files with our applications files instead of having them in the same "vendor" folder (img and css is relatively loaded, so no problem there).

2. The calculation of the scriptUri in embed.js is is done using the last script tag. This is not compatible with our use of Angular component as the script tag is then in the middle of the DOM. I have not investigated this one completely but I noticed that the domain was the domain of the hosting app, not the one of the source embed file.

3. updateParentHash manipulate directly window.parent.document.location. It was working fine at first (I just had to add a "reloadOnSearch: false" in the route definition to prevent unintented route change when clicking on a "event") but things stopped working when i corrected scriptUri to refer to the common server hosted files (and embedding the timeline in my local server), very likely because of CORS /security limitation. I think it would be more appropriate to add a custom message on easyXDM.Socket and update the url through the embed bootstrap script (or explore other solution to be able to relay the message at the angular app level).

Thanks for sharing Timeline, it's very nice!

timeline not working
https://wellcomelibrary.org/collections/digital-collections/makers-of-modern-genetics/genetics-timeline/
shows empty page (only header and footer of the page)