I am looking for general advice regarding an unusual use of FileMaker.
Â
In my work I use FileMaker to track content for museum exhibition design. This is basic stuff: what does the artifact look like, what are its dimensions, what is the text label, what display case does it go in, and other related data. I have experimented with creating a layout that works as a âdigital labelâ in FileMaker Go or in kiosk mode on a touch screen that uses the data collected in the content management database, indeed, they can be the same file.Â
Â
FileMaker makes it easy to have a really great label with swipes, pop-ups, images, everything that a museum visitor would want to learn more about what they are looking at, and I have fashioned a second no-nonsense interface for the curators and museum staff to update, edit, add, and delete records (âlabelsâ) as required. (See attached JPG for a sample âlabelâ layout.)
Â
Now the problem...
Â
A client is interested in this digital label idea, but they want to use it with touchscreens attached to computers rather than on iPads, which means purchasing FileMaker for each display (40 of them!) and, possibly, running FileMaker Server. This project is meant to be an add-on and Iâm not sure if using FileMaker Pro rather than FileMaker Go would be a cost effective way to proceed.
Â
Iâm interested in the communityâs evaluation of the following options. (Please note that I am a low-to-mid level FileMaker user and know nothing of PHP, SQL, or stuff like that, except that they exist and can do some of the stuff I want to do. I can get someone else to do the work if leaving FileMaker is the best option.)
Â
Option 1: FileMaker Server with 40 copies of FileMaker Pro connected to a database on the server. Staff can update the database from their offices and the changes are reflected in the âdigital labelsâ (FileMaker running in kiosk mode on touchscreens) in the exhibition space .
Â
Option 2: FileMaker Pro for staff to edit records and FileMaker Server using custom web publishing (PHP?) with web browsers (or equivalent) acting as digital labels in the exhibition space.
Â
Option 3: Use the original FileMaker database as a source for some other content management system that can be accessed with web browsers (or equivalent), in other words, a completely custom solution.
Â
Iâm not looking for detailed proposals, specs, or anything technical. What I would like are general observations about the strengths or weaknesses of each model, or even a new model, that could be maintained by a small museum with almost no in-house tech staff.
Â
And just a side note, it would be great if FileMaker made a simple FileMaker client for desktop systems, similar to FileMaker Go. This would, I think, be one solution to my problem.
Â
Thanks,
Â
-Robert.
Â