 How's it going, everyone? Welcome to Cabin 2 Museums. I'm Chris Arnold. I'm a software application developer at the Indianapolis Museum of Art. This is an open-source project we've been working on for a while, built on top of Troubles, so I'm here to kind of just share a little bit about what we've been doing. How many museum people do we have? So this is also my first Troublescom presentation by Stutter. Sorry, work that we've done in the museum community is part of the IMU lab. So, what is HAP? HAP is an open-source set of tools for creating mobile tours. Let me start over. HAP is an open-source set of tools for providing mobile tours in your museum. It's a project that began in 2009. We've done this in collaboration with several museums and vendors. The reason we created HAP is at the time in 2009 a lot of the existing tools were just not that good. The other reason we did this was to build community support and adaptation of the turmoil metadata specifications, as it means for representing the content and the experience. It's a XML standard that we created in collaboration with other vendors so that even if you don't use, there's a standardized spec that any vendor can utilize. The third reason was to help foster open-source participation in the museum community. At the time when we started creating this, there was just a lot of tools available to museums and the open-source realm, advocates of open-source and being museum people. What is HAP and Tourmoyle? What it is is a content authoring environment, a native iOS application, a jQuery mobile web application, and an open-source standard for storing and accessing that data. So, here we have the building blocks of HAP. The foundation, we have the authoring layer. This is built on Drupal. And then the tab suite sits on top of that, and this is what provides the tools that content editors can create, which is the TourML specification, the iOS app. The mode is a specification for mobile content. If you see above, this is essentially what a tour looks like. With any tour, you have stimes, a stop would essentially represent an object. If you bend your stops, they can be interconnected to other stops if you have other artworks that are related to the specific stuff that you're doing, assets through connections and asset references. The assets are just your media. It's fairly open. We also provide tour sets in the TourML specification. Essentially, as a tour set, it's just a way to contain many tours. So, within your museum, you can start the app. There's just more of a breakdown. So, within TourML, you have a tour set, a tour, your tour metadata, asset stops, and connections. That makes sense so far. That is the content layer. So, here we have the application layer. This is the jQuery mobile app. It's just built on jQuery mobile and backbone. Pretty straightforward. It can be ran on your website or it can be bundled in. So, there's three views here that are provided out of the box. The first is a keypad view. The way we utilize this is if you were in a, we have a simple three-digit code in that stop code and then they'll get the relevant information. Their option is just a fairly straightforward list of stops that are available. The more open-ended the user doesn't have to know which stop they want to go to. They can see what options are available. Lastly is the map view. This is most relevant if you're using geolocation data, where you can plot all of your stops on a map. Specifically, we use this opinion at the Museum of Art for our 100 Acres Art Nature Park. So, visitors can come to the park. The second aspect is the Native iOS app. So, this is written in Objective-C, works on iPad, and here you see two examples. One on the left is an app we call Launchpad that we created for the Art Institute of Chicago. That is an in-gallery piece that they had. The highway way and exhibition. Buddy familiar to Drupal is probably pretty familiar with what this screen looks like. It's fairly straightforward. It provides out-of-the-box on the left the ability to create the different types of stops. We provide a few basic types out-of-the-box, but you can create any type of content type that you wish as a stop. So, Drupal site. This right here is just an example of the highway way tour. If you were on the tour page, you see a listing of your stops, you have the ability to refine the search by code and stop type. And then we provide several options up here at the top for web app preview, export, geolocation entry, and tap. It just utilizes the open layers module and just on a map, plot out the points that they want the stop to, like this, and tour a while. You see that we have a tour a while content, that data is stored in a data field, and then we store the properties of the centroid, which would be the center point of location. And then a bounding box, which would give you the framework reference. With all these features, it's also extremely expandable. This is an example that does not come in tap, but it was an example that we used for the Art Institute of Chicago's iPad. So they wanted to do a cluster view where each of these pictures represents artwork, and the way that the user utilizes this in the app is they can scroll through at any time, tap on any of these objects, and then dive in to find more information. So to make this easier for the content editors to create, we essentially mimic that interface on the Drupal node edit page. So we even added that it's not a real iPad, it stimulates that, and authors can go through, click and drag to slide through. They can use their scroll bar to shrink and expand the size of the artworks. You see at the bottom there's a little toolbar, the black boxes represent where the artworks are, and then they have two canvas. So this makes it really easier for content editors to kind of visualize what the tour is going to look like whenever it's done. This right here is the turmoil export tab, hooks, where you can create your own bundle types for, I knew this, and export an entire tour to Amazon's S3 service. But out of the box you can get a bundle in a zip or IOS format. And what that bundle is, is it will pull all of your turmoil and all of your media assets, throw them into a zip file that you can then enclose into your app, in the case of IOS, it also includes language files and that gets imported into hex code. And this is an example of what the turmoil looks like. It's a lot of XML, site building aspects of Drupal. Instead of building custom interfaces to work with turmoil, this is just the managed display page on a Drupal site. Just like any other Drupal site when you create fields, you can change the order of them, change how they display with the templating system. We created a new display mode that is just turmoil XML. And with that then we created four matters for all of your basic Drupal field types. So by selecting that drop down, turmoil knows how to take that text field. Same thing, subtitle becomes an asset, images become assets, and we also have multi-part assets. And there's a few other that I don't really thought. You guys have any questions? One question, why are you so iPhone centric? Big reason is just we have the skill set in-house to work with. Big reason is we had initially started, there just wasn't a lot of it. It's something we've always talked about. I have one there was somebody there that was working on trying to make it. I mean that's the big reason is we have the skill set to do IOS development. That's why it was our solution. Which leads to another question. So then are the websites that you make responsive, do they display nicely on mobile so you can sort of serve that other audience? I'm trying to say that again. Before these museums do they have websites that have responsive, mobile friendly websites so they can serve that audience? So the question is, is it responsive? No, I guess what I'm saying is you have these applications for iPhones and you're not developing for Android, but do you have a solution for Android? It's great and it's tapped into museums, but... That's basically the web app that we have. It's its own individual repository. So we've separated, Torn Oil has its own repository. The CMS site has its own repository. The native application has its own repository as well as the web app. So we've decoupled those so that if anybody wanted to utilize any part of it in CSS. So with that web app... Quick question. Do you have any experience with getting data, a object at the sites or the assets from the museum collection systems? Most of the cases that we've done in-house, we just have a team of content editors that create and curate that content themselves. But for example, we ask them to synchronization. They use Citi. I don't know. That's what their collection data is stored in. So we're able to create a synchronization between CAP and their Citi database to automatically pull in these artworks and make them have access to that artwork. So that ability is definitely... It's not out of the box, but you can write your own synchronizing. So I've done triple sites. Start to finish. How far can I get with this? Or do I have to at some point rely on some more objective seeds? I don't know either of those. So if I've done regular triple installs, so there is there a point... The web app. So I brought up the web app because it can... And it also works perfectly for the 100 acres tours, is that we just have a link on the mobile website that says take the tour. Right now, everything's just a GitHub repository. So that's something I was talking with a fellow earlier with. I have an application on Drupal.org to get this as a project on Drupal.org. Yesterday was the one year anniversary when I created that. So I've been trying to pay. So it won't even be a process of downloading. It'll just go to the tab distribution. And I hear it just like you would Drupal, instead of picking the standard installation, you would pick the tab installation. And something else we've discussed, but it's not on a solid project as we've considered. And if anybody has any input, would like to ask me about this later. We've considered creating just a hosted tab service to make available for people. If that's something that might sound interesting to you, take a source of information to exhibit or show or an open-source project that's, we are what is awesome, it's a little $35 credit size computer. Because there is stuff out there that already exists and it's ridiculously expensive for people tracking inside a museum. So this other side project, we're actually that single is your MAC address. So we've set up a, we're doing a little test pilot right now, Dick, but something that we are trying to address. So utilizing the Drupal media module. So there's nothing particularly fancy about it. Just any feature you get out of music. So in any editions that are available to the media module, you also get out of that. So you can embed books to get some, in that scenario we have the software on because with some of the larger media files, we couldn't just put an instance inside of the network streaming off infrastructure for that. So that requires that we bundle all of the media inside the app. The module is already available at geton.com slash ima museum. That's where we keep all of our open-source projects. So all of the components of TAP are already up there for a download on our ASCII project, which is a scholarly e-reader that we've been working on. It's also available there. It's also where the people traffic are going. Yep, yep, all of them on it. On all the Drupal sites, all of the TAP CMS project, and everything self-contained within that. Sorry, can you say that again? I'm curious about navigation of this. I guess I'll end the patient with that. You can create stop groups that within them embed multiple stops, which is those three. We've done some implementations, like the highway way, and the cluster stop was kind of a neutral cluster. It was representative of the game. That's all I've got. Our is struggling because the resources we have to do these kind of things to say is because this makes the... I mean, it is worth pointing out another part of this whole initiative of TAP and a lot of it. As we've been fortunate enough to have a pretty large team of developers and designers that are all amazingly talented and very good at all the IOS stuff. As we've had this team and been able to create a lot of great software and open source that it doesn't make it available to smaller museums or museums that would not typically have it, that's definitely a big mission within what we do with the IMAs, as far as our technology fleece and where people can... Chris, how many really spearheaded the version 2 in Drupal 6? This implementation was the Drupal 7. When we got to Smithsonian, we had utilizing TAP, Crystal Bridges, the aerospace one would be great. There's been more that I could keep up with. It's actually done pretty well in the... museum.org. We also have a list of some of the key studies that have implemented it. We also have a Google group for discussions for anybody else that's using it or if you need assistance getting it set up. Museums, find out about it. I guess it's just been through work. So that's where a lot of our showing up in museum conferences.