Re: [CODE4LIB] Putting several small databases online.
Although it sounds like you're moving in a different direction, I'll put in a plug for Xataface (http://xataface.com/ ) It's a PHP/MySQL framework that doesn't require a lot of development to produce a usable application. So it fits between somewhere between Cake and Drupal -- more turnkey than the former, and more lightweight than the latter. I found it very pleasant to work with when I had to whomp up a CRUD application in a hurry last year. John -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Paul Butler (pbutler3) Sent: June-28-12 11:07 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Putting several small databases online. Hi All, Thank you all for your excellent replies. After sitting down with folks, listening to their current workflow, and future goals, I think we will likely move this type of collection to our existing archive. Short term goals are to have them back up the data on the lone workstation with the DB on it, start moving transcriptions out of MS Word documents to a more sustainable format (likely TEI XML), and use Google Docs as a convenient way to share flat files between themselves and outside researches. As for the other collection, I am still waiting for that meeting. So far it has gotten several stakeholders across campus excited about future projects. Cheers, Paul +-+-+-+-+-+-+-+-+-+-+-+-+ Paul R Butler Assistant Systems Librarian Simpson Library University of Mary Washington 1801 College Avenue Fredericksburg, VA 22401 540.654.1756 libraries.umw.edu Sent from the mighty Dell Vostro 230. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Matthew Zimmerman Sent: Thursday, June 28, 2012 1:37 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Putting several small databases online. Aside from the technical considerations, just be sure you really want to host these and can promise long term support. At a previous job we started hosting databases and as each of us moved on to different institutions there was no one left to maintain the dbs. I still get a call ever six months or so from a professor at an institution I left four years ago when she has a problem ;-) - Original Message - From: "Chad Benjamin Nelson" To: CODE4LIB@LISTSERV.ND.EDU Sent: Wednesday, June 27, 2012 10:41:21 AM Subject: Re: [CODE4LIB] Putting several small databases online. Hi Paul, If you're comfortable with php, which it sounds like you are, I'd recommend the cakephp framework. It's lightweight and fairly easy to get started with. The Tutorial provides a nice introduction to getting started and quickly building a simple CRUD app like you are talking about. It doesn't come with as much built in as Drupal, but it does mean there is a lot less to worry about and so you can get your barebones site up pretty quickly. There are also quite a few plugins available to help you build up a site quickly without writing too much custom code. Hope that helps, Chad Chad Nelson Web Services Programmer University Library Georgia State University e: cnelso...@gsu.edu t: 404 413 2771 My Calendar From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Tomas Saorin [saorinto...@gmail.com] Sent: Wednesday, June 27, 2012 8:33 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Putting several small databases online. Drupal and Views fit for your needings, and it may also work as a framework for php-mysql apps. Enviado desde mi iPad El 27/06/2012, a las 14:03, "Richard, Joel M" escribió: > 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 | richar...@si.edu > > > 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 corr
Re: [CODE4LIB] Putting several small databases online.
Strong argument for some kind of informal hosting or assistance with this type of thing done between the universities. -Wilhelmina On Jun 28, 2012 12:38 PM, "Matthew Zimmerman" wrote: > Aside from the technical considerations, just be sure you really want to > host these and can promise long term support. At a previous job we started > hosting databases and as each of us moved on to different institutions > there was no one left to maintain the dbs. I still get a call ever six > months or so from a professor at an institution I left four years ago when > she has a problem ;-) > > - Original Message - > > From: "Chad Benjamin Nelson" > To: CODE4LIB@LISTSERV.ND.EDU > Sent: Wednesday, June 27, 2012 10:41:21 AM > Subject: Re: [CODE4LIB] Putting several small databases online. > > Hi Paul, > > If you're comfortable with php, which it sounds like you are, I'd > recommend the cakephp framework. It's lightweight and fairly easy to get > started with. The Tutorial provides a nice introduction to getting started > and quickly building a simple CRUD app like you are talking about. > > It doesn't come with as much built in as Drupal, but it does mean there is > a lot less to worry about and so you can get your barebones site up pretty > quickly. There are also quite a few plugins available to help you build up > a site quickly without writing too much custom code. > > Hope that helps, > > Chad > > Chad Nelson > Web Services Programmer > University Library > Georgia State University > > e: cnelso...@gsu.edu > t: 404 413 2771 > My Calendar > > > From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Tomas > Saorin [saorinto...@gmail.com] > Sent: Wednesday, June 27, 2012 8:33 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] Putting several small databases online. > > Drupal and Views fit for your needings, and it may also work as a > framework for php-mysql apps. > > Enviado desde mi iPad > > El 27/06/2012, a las 14:03, "Richard, Joel M" escribió: > > > 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 | richar...@si.edu > > > > > > 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 > supp...@townlife.com immediately. > >> > >>> -Original Message- > >>> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf > Of > >>> Kevin Hawkins > >>> Sent: June 26, 2012 9:13 PM > >>> To: CODE4LIB@L
Re: [CODE4LIB] Putting several small databases online.
Hi All, Thank you all for your excellent replies. After sitting down with folks, listening to their current workflow, and future goals, I think we will likely move this type of collection to our existing archive. Short term goals are to have them back up the data on the lone workstation with the DB on it, start moving transcriptions out of MS Word documents to a more sustainable format (likely TEI XML), and use Google Docs as a convenient way to share flat files between themselves and outside researches. As for the other collection, I am still waiting for that meeting. So far it has gotten several stakeholders across campus excited about future projects. Cheers, Paul +-+-+-+-+-+-+-+-+-+-+-+-+ Paul R Butler Assistant Systems Librarian Simpson Library University of Mary Washington 1801 College Avenue Fredericksburg, VA 22401 540.654.1756 libraries.umw.edu Sent from the mighty Dell Vostro 230. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Matthew Zimmerman Sent: Thursday, June 28, 2012 1:37 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Putting several small databases online. Aside from the technical considerations, just be sure you really want to host these and can promise long term support. At a previous job we started hosting databases and as each of us moved on to different institutions there was no one left to maintain the dbs. I still get a call ever six months or so from a professor at an institution I left four years ago when she has a problem ;-) - Original Message - From: "Chad Benjamin Nelson" To: CODE4LIB@LISTSERV.ND.EDU Sent: Wednesday, June 27, 2012 10:41:21 AM Subject: Re: [CODE4LIB] Putting several small databases online. Hi Paul, If you're comfortable with php, which it sounds like you are, I'd recommend the cakephp framework. It's lightweight and fairly easy to get started with. The Tutorial provides a nice introduction to getting started and quickly building a simple CRUD app like you are talking about. It doesn't come with as much built in as Drupal, but it does mean there is a lot less to worry about and so you can get your barebones site up pretty quickly. There are also quite a few plugins available to help you build up a site quickly without writing too much custom code. Hope that helps, Chad Chad Nelson Web Services Programmer University Library Georgia State University e: cnelso...@gsu.edu t: 404 413 2771 My Calendar From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Tomas Saorin [saorinto...@gmail.com] Sent: Wednesday, June 27, 2012 8:33 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Putting several small databases online. Drupal and Views fit for your needings, and it may also work as a framework for php-mysql apps. Enviado desde mi iPad El 27/06/2012, a las 14:03, "Richard, Joel M" escribió: > 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 | richar...@si.edu > > > 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
Re: [CODE4LIB] Putting several small databases online.
Aside from the technical considerations, just be sure you really want to host these and can promise long term support. At a previous job we started hosting databases and as each of us moved on to different institutions there was no one left to maintain the dbs. I still get a call ever six months or so from a professor at an institution I left four years ago when she has a problem ;-) - Original Message - From: "Chad Benjamin Nelson" To: CODE4LIB@LISTSERV.ND.EDU Sent: Wednesday, June 27, 2012 10:41:21 AM Subject: Re: [CODE4LIB] Putting several small databases online. Hi Paul, If you're comfortable with php, which it sounds like you are, I'd recommend the cakephp framework. It's lightweight and fairly easy to get started with. The Tutorial provides a nice introduction to getting started and quickly building a simple CRUD app like you are talking about. It doesn't come with as much built in as Drupal, but it does mean there is a lot less to worry about and so you can get your barebones site up pretty quickly. There are also quite a few plugins available to help you build up a site quickly without writing too much custom code. Hope that helps, Chad Chad Nelson Web Services Programmer University Library Georgia State University e: cnelso...@gsu.edu t: 404 413 2771 My Calendar From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Tomas Saorin [saorinto...@gmail.com] Sent: Wednesday, June 27, 2012 8:33 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Putting several small databases online. Drupal and Views fit for your needings, and it may also work as a framework for php-mysql apps. Enviado desde mi iPad El 27/06/2012, a las 14:03, "Richard, Joel M" escribió: > 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 | richar...@si.edu > > > 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 supp...@townlife.com >> immediately. >> >>> -Original Message- >>> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of >>> Kevin Hawkins >>> Sent: June 26, 2012 9:13 PM >>> To: CODE4LIB@LISTSERV.ND.EDU >>> 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- >&
Re: [CODE4LIB] Putting several small databases online.
Hi Paul, If you're comfortable with php, which it sounds like you are, I'd recommend the cakephp framework. It's lightweight and fairly easy to get started with. The Tutorial provides a nice introduction to getting started and quickly building a simple CRUD app like you are talking about. It doesn't come with as much built in as Drupal, but it does mean there is a lot less to worry about and so you can get your barebones site up pretty quickly. There are also quite a few plugins available to help you build up a site quickly without writing too much custom code. Hope that helps, Chad Chad Nelson Web Services Programmer University Library Georgia State University e: cnelso...@gsu.edu t: 404 413 2771 My Calendar From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Tomas Saorin [saorinto...@gmail.com] Sent: Wednesday, June 27, 2012 8:33 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Putting several small databases online. Drupal and Views fit for your needings, and it may also work as a framework for php-mysql apps. Enviado desde mi iPad El 27/06/2012, a las 14:03, "Richard, Joel M" escribió: > 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 | richar...@si.edu > > > 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 supp...@townlife.com >> immediately. >> >>> -Original Message- >>> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of >>> Kevin Hawkins >>> Sent: June 26, 2012 9:13 PM >>> To: CODE4LIB@LISTSERV.ND.EDU >>> 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
Re: [CODE4LIB] Putting several small databases online.
Drupal and Views fit for your needings, and it may also work as a framework for php-mysql apps. Enviado desde mi iPad El 27/06/2012, a las 14:03, "Richard, Joel M" escribió: > 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 | richar...@si.edu > > > 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 supp...@townlife.com >> immediately. >> >>> -Original Message- >>> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of >>> Kevin Hawkins >>> Sent: June 26, 2012 9:13 PM >>> To: CODE4LIB@LISTSERV.ND.EDU >>> 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.
Re: [CODE4LIB] Putting several small databases online.
There are tools that let you use Filemaker as a sort of front end to MySQL http://www.filemaker.com/support/technologies/mysql.html You could export the MS Accses into csv then import into Filemaker. Edward Iglesias On Tue, Jun 26, 2012 at 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've had a chance to look at the FileMaker Pro data. Not the worst I have > seen, it needs normalized, but the data itself is fairly uniform and would > map easily enough to Dublin Core. So far just text, though they say > perhaps, someday, they might want images. I have yet to see the MS Access > data. > > I've worked on various personal/school projects using SQL, PHP, HTML, CSS, > and various repositories/CMS. For personal use and fun I've thrown > together a few LAMPs using VMWare, but nothing production. > > 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. > > I am thinking of tossing together a virtualized LAMP, secure it, build the > bones of a site, and then clone the thing and put the data for each project > in its own copy onto a webserver. > > Is there a better/easier way? Am I doomed to a life of pain and suffering > (besides that due to being a librarian)? Have a LAMP distro with a CMS to > suggest? Any suggestions are welcomed. > > Cheers, Paul > +-+-+-+-+-+-+-+-+-+-+-+-+ > Paul R Butler > Assistant Systems Librarian > Simpson Library > University of Mary Washington > 1801 College Avenue > Fredericksburg, VA 22401 > 540.654.1756 > libraries.umw.edu > > Sent from the mighty Dell Vostro 230. >
Re: [CODE4LIB] Putting several small databases online.
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 | richar...@si.edu 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 supp...@townlife.com > immediately. > >> -Original Message- >> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of >> Kevin Hawkins >> Sent: June 26, 2012 9:13 PM >> To: CODE4LIB@LISTSERV.ND.EDU >> 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.
Re: [CODE4LIB] Putting several small databases online.
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 supp...@townlife.com immediately. > -Original Message- > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of > Kevin Hawkins > Sent: June 26, 2012 9:13 PM > To: CODE4LIB@LISTSERV.ND.EDU > 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.
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.
Re: [CODE4LIB] Putting several small databases online.
I guess you made the simple thing complicated. If you have LAMP, which is easy to implement, you would have a decent DBMS, that is MySQL. Then, you probably need mysqladmin or workbench utilities to manage your server. Everything is free. Kelly Zhu -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Paul Butler (pbutler3) Sent: Tuesday, June 26, 2012 4:03 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Putting several small databases online. 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've had a chance to look at the FileMaker Pro data. Not the worst I have seen, it needs normalized, but the data itself is fairly uniform and would map easily enough to Dublin Core. So far just text, though they say perhaps, someday, they might want images. I have yet to see the MS Access data. I've worked on various personal/school projects using SQL, PHP, HTML, CSS, and various repositories/CMS. For personal use and fun I've thrown together a few LAMPs using VMWare, but nothing production. 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. I am thinking of tossing together a virtualized LAMP, secure it, build the bones of a site, and then clone the thing and put the data for each project in its own copy onto a webserver. Is there a better/easier way? Am I doomed to a life of pain and suffering (besides that due to being a librarian)? Have a LAMP distro with a CMS to suggest? Any suggestions are welcomed. Cheers, Paul +-+-+-+-+-+-+-+-+-+-+-+-+ Paul R Butler Assistant Systems Librarian Simpson Library University of Mary Washington 1801 College Avenue Fredericksburg, VA 22401 540.654.1756 libraries.umw.edu Sent from the mighty Dell Vostro 230. **Bronze+Blue=Green** The University of Central Oklahoma is Bronze, Blue, and Green! Please print this e-mail only if absolutely necessary! **CONFIDENTIALITY** This e-mail (including any attachments) may contain confidential, proprietary and privileged information. Any unauthorized disclosure or use of this information is prohibited.
Re: [CODE4LIB] Putting several small databases online.
Drupal is our tool of choice for building CRUD apps. Depending on the data, you can either do an import, or you can connect directly to the data in an external database. Filemaker will likely need to be converted. Modern Access might be able to connect directly through PDO, although I would avoid that. Thanks, Cary On Tue, Jun 26, 2012 at 2: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've had a chance to look at the FileMaker Pro data. Not the worst I have > seen, it needs normalized, but the data itself is fairly uniform and would > map easily enough to Dublin Core. So far just text, though they say perhaps, > someday, they might want images. I have yet to see the MS Access data. > > I've worked on various personal/school projects using SQL, PHP, HTML, CSS, > and various repositories/CMS. For personal use and fun I've thrown together > a few LAMPs using VMWare, but nothing production. > > 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. > > I am thinking of tossing together a virtualized LAMP, secure it, build the > bones of a site, and then clone the thing and put the data for each project > in its own copy onto a webserver. > > Is there a better/easier way? Am I doomed to a life of pain and suffering > (besides that due to being a librarian)? Have a LAMP distro with a CMS to > suggest? Any suggestions are welcomed. > > Cheers, Paul > +-+-+-+-+-+-+-+-+-+-+-+-+ > Paul R Butler > Assistant Systems Librarian > Simpson Library > University of Mary Washington > 1801 College Avenue > Fredericksburg, VA 22401 > 540.654.1756 > libraries.umw.edu > > Sent from the mighty Dell Vostro 230. -- Cary Gordon The Cherry Hill Company http://chillco.com
[CODE4LIB] Putting several small databases online.
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've had a chance to look at the FileMaker Pro data. Not the worst I have seen, it needs normalized, but the data itself is fairly uniform and would map easily enough to Dublin Core. So far just text, though they say perhaps, someday, they might want images. I have yet to see the MS Access data. I've worked on various personal/school projects using SQL, PHP, HTML, CSS, and various repositories/CMS. For personal use and fun I've thrown together a few LAMPs using VMWare, but nothing production. 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. I am thinking of tossing together a virtualized LAMP, secure it, build the bones of a site, and then clone the thing and put the data for each project in its own copy onto a webserver. Is there a better/easier way? Am I doomed to a life of pain and suffering (besides that due to being a librarian)? Have a LAMP distro with a CMS to suggest? Any suggestions are welcomed. Cheers, Paul +-+-+-+-+-+-+-+-+-+-+-+-+ Paul R Butler Assistant Systems Librarian Simpson Library University of Mary Washington 1801 College Avenue Fredericksburg, VA 22401 540.654.1756 libraries.umw.edu Sent from the mighty Dell Vostro 230.
