 |
 |
I agree with Clinton. Above all else, security is important and you want something that handles credentials properly. Chances are, your sites are getting "scanned" by potential hackers every day and you may not know it. They don't try to hack in because of who you are, only because you are there. I also second the idea of using Drupal to do this. It comes out of the box with a lot of the features you listed, plus some. Besides, I'll bet you a pint of your favorite beer that once this data is online, your users will want to do more with it. Having a flexible foundation is not a bad thing. :) --Joel Joel Richard Lead Web Developer, Web Services Department Smithsonian Institution Libraries | http://library.si.edu/ (202) 633-1706 | [log in to unmask] On Jun 26, 2012, at 11:50 PM, Clinton Boyda wrote: > There are other methods of putting data online, like Google's spreadsheet etc. > > I just wanted to point out, the "simplicity" of putting a small database online can require a professional skill set. Security permissions need to be set correctly, and a database is very rarely store on the same server as a webpage because of these reasons. It might really be time to call a programmer just so that all your project works as you expected :) > > > -- > Clinton Boyda > > Econolution Inc. > Helping Rural Communities Diversify, Grow & Prosper. > www.townlife.com Community Powered Websites! > > Please consider the environment before printing this email. > > Confidentiality: The information contained in this transmission is privileged and confidential. It is intended only for the use of the individuals or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that you are not authorized to review the following information or attachments, and that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication please notify [log in to unmask] immediately. > >> -----Original Message----- >> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of >> Kevin Hawkins >> Sent: June 26, 2012 9:13 PM >> To: [log in to unmask] >> Subject: Re: [CODE4LIB] Putting several small databases online. >> >> If these are working databases used by just a handful of people, not things >> you're trying to preserve for the long run, then for the FileMaker one I would >> consider using FileMaker Pro's built-in "instant web publishing" feature. More >> on this and other options are at: >> >> http://help.filemaker.com/app/answers/detail/a_id/7466/~/publishing- >> databases-on-the-web-with-filemaker-pro-and-filemaker-server >> >> I believe MS Access has something similar for using MS SQL Server. >> >> --Kevin >> >> On 6/26/12 5:03 PM, Paul Butler (pbutler3) wrote: >>> Hi All, In the last week the library has been approached by two >>> different departments across campus that have small databases, one >>> FileMaker Pro and one MS Access, that they would like to make >>> available online. The interfaces would be nothing fancy, with a >>> backend that allows for adding/updating/deleting resources. >> >> [. . .] >> >>> I would prefer not to build too much from scratch. I don't think I >>> want/need a full blown repository for either (though I help admin ours >>> and it is due for a complete hardware/software overhaul later this >>> summer< http://archive.umw.edu/>. I am thinking of transitioning it to >>> more of an IR with disparate content.) >>> >>> So, what would you do or have you done? I want something nimble. I >>> would love to build it once and then duplicate it. I get the sense >>> once I start helping folks other departments will come forward.