This week I worked on manually adding individual items to the new IU Hoagy Carmichael Omeka site. This will not be how we migrate most of the content, but the experience provided me an opportunity to mock-up how the site might look in its fully operational form. The process of downloading derivative image files and manually adding Dublin Core metadata is tedious, but it is very helpful since it allows me to get a feel for how best to present these items and the collections that I will be rebuilding. In a way, it’s an early trouble-shooting experience because sometimes there isn’t a one-to-one comparative way of representing items in the Omeka site from the same items in the legacy site. I’m looking at this week as an opportunity to identify the subseries that will be relatively straightforward in processing and migrating, and the subseries that will require more time.
One challenge will be figuring out how to utilize a ‘page-turning’ plug-in for text items that are comprised of multiple pages. By default, Omeka organizes multiple pages all on the same webpage by stacking the images on top of each other, in a simple hierarchical display that the user simply scrolls through. Ideally, we will download a paginator plug-in that has been customized for Omeka, either ‘Doc Viewer’ or ‘File Paginator’.
At Nick’s suggestion, I also investigated the app ‘Timeline JS’, which allows users to create visually dynamic timelines on a webpage. I watched a brief ‘how to’ video, and the app seems straightforward. I believe I would be able to create the timeline with ‘Timeline JS’ and embed the created link in an <iframe> tag on an Omeka Simple Page.
Next week, Nick will show me how to install Omeka plug-ins on the IU hosted server, which will allow me to add new dynamic layers to the site, like the aforementioned timeline, collection tree structures, and page-turners.