Hi,
I'm presently researching the use of Omeka for possible mobile learning projects. I was very impressed with the Art in the City project but I can't find any recent information about it. Is the project still active?
On a more general note, I would also love to hear about other examples of Omeka being used with mobile devices.
We developed the Art in the City project last summer with a small grant as a prototype to show what was possible to build using Omeka as a backend with mobile style sheets and plugins.
I don't know of anyone else who is using Omeka for mobile site yet, but it is very possible that some folks are still in the development stages.
We are glad to hear you are interested in using Omeka for a mobile project. Please keep us informed!
I realize this is an old post, but I am currently experimenting with Omeka for a mobile project. However, it doesn't appear that any of the exhibit page layouts would work on a phone screen (I want multiple pictures and text blocks to be stacked above each other, not next to each other, like Art in the City but with multiple images per page). (I then want to use the bar code feature to send people to these pages.) I am a very new user of Omeka, so it's very possible I'm just overlooking something or haven't yet figured out how to do this. But is this possible?
You can create an exhibit layout that fits the needs of your project.
What you see in Art in the City isn't an exhibit page, but rather an items/browse page. It consists of a thumbnail, item title, and tags.
You can also design a theme that will display the items in the way that you wish, just like you would if you were creating another website.
Using the QR Code plugin is a great idea to point visitors to an item's page.
Have you looked at the the Cleveland Historical free iPhone app? They used Omeka for the back end, so it might give you some ideas for structuring your mobile site.
http://mobilehistorycleveland.org/
Hi,
I'm working as a research officer in Malaysian Culture and Heritage Digital Bank project. It's been already a year and we have one more year left to finish this project.
I’m using three different areas for this project which is community part (using WordPress + BuddyPress), digital archiving (using ResourceSpace) to manage our own digital Cultural Heritage assets, and Digital Museum or Virtual Museum (using OMEKA) to have a public Cultural Heritage exhibitions and stories.
Since we are talking about taking advantage of using OMEKA to creating Mobile-based Applications, I want to ask what are the best ways to connect and use data stores on OMEKA?
Let’s say I'm an iOS developer and I want to know how you are using OMEKA in Art in the City or Cleveland Historical Apps. Are you having a custom PHP pages to fetch data by GET and POST parameters, or you are using JSON, or it’s an HTTPRequest, or etc.
I think it's so much better to have some parts of OMEKA on the iPhone or iPad even just for preserving Cultural Heritage. However there are lots of opportunities by using mobile devices such as location-aware apps, more realistic storytelling, and even using iOS core image framework to enhance OMEKA with annotation and face detection.
I'd like to start this topic to help others to create and built mobile apps not alone by their own and have a little help from OMEKA specialist and developers.
Best regards,
Maziyar
Somehow yes, it is being used by many users, but this needs to be promoted so it will be known more..
Cheers,
Ethan, of Aimee St. Hill iPad Case Designs
Hi Ethan,
Yes I found a few and built few apps for our projects by integrating them into the Omeka. The last one I did was a location-aware mobile application for cultural tourism and I implemented the Omeka entirely into AWS cloud platform in order to take advantage of its cloud computing, cloud storage (backup), and Route 53.
That was fun and soon will start another project with new Omeka for architectural and historical buildings and I planned to integrate this one as well with iOS devices. I just love to do native apps and avoid as much as possible building cross-platform apps. Better have a killing app on one platform than an average app on few platforms.