Re: [CODE4LIB] yaoss4ll
I second John Fereira's comment re: putting this information into a CMS =) For instance it'd be awesome to browse by language... And, Drupal actually has a series of library-related modules out there; you already mention the MARC module in http://infomotions.com/tmp/oss/discovery.html ... here are two lists for more library-related modules: http://drupalib.interoperating.info/library_modules http://groups.drupal.org/node/14062 _alejandro John Fereira said the following on 22/12/2009 12:25 p.m.: Jonathan Rochkind wrote: Putting it on a wiki anyone can edit makes it, perhaps, somewhat more likely that it ends up maintained longer, making it easier for other people to get involved in maintaining it without technological barriers or proprietary feelings getting in the way. I was thinking of something more along the lines of putting it into a CMS (i.e. Drupal) so that voting/ranking/tagging tools could be used to allow the community to rate the viability and discovery of each item. I may actually need to do something like this but for a different domain on a project that I'll be working on over the next year. -- _ ___ _ _ _ _ _ _ _ *Ing. Alejandro Garza González* Coordinación de proyectos y desarrollo de sistemas Centro in...@te, Centro para la Innovación en Tecnología y Educación Tecnológico de Monterrey Tel. +52 [81] 8358.2000, Ext. 6751 Enlace intercampus: 80.689.6751, 80.788.6106 http://www.itesm.mx/innovate/ El contenido de este mensaje de datos no se considera oferta, propuesta o acuerdo, sino hasta que sea confirmado en documento por escrito que contenga la firma autógrafa del apoderado legal del ITESM. El contenido de este mensaje de datos es confidencial y se entiende dirigido y para uso exclusivo del destinatario, por lo que no podrá distribuirse y/o difundirse por ningún medio sin la previa autorización del emisor original. Si usted no es el destinatario, se le prohíbe su utilización total o parcial para cualquier fin. The content of this data transmission must not be considered an offer, proposal, understanding or agreement unless it is confirmed in a document signed by a legal representative of ITESM. The content of this data transmission is confidential and is intended to be delivered only to the addressees. Therefore, it shall not be distributed and/or disclosed through any means without the authorization of the original sender. If you are not the addressee, you are forbidden from using it, either totally or partially, for any purpose.
Re: [CODE4LIB] yaoss4ll [cms]
On Jan 4, 2010, at 10:54 AM, Alejandro Garza Gonzalez wrote: I second John Fereira's comment re: putting this information into a CMS =) For instance it'd be awesome to browse by language... For the past week or so I have been trying to evaluate content management systems (CMS). Boy, there are bunches of them out there! Lot's of choice. The market is so much more mature in this area compared to librayr-specific open source applications. (Ironically, MyLibrary is/was sort of like a CMS in that it was intended to create certain types of Web pages based on the content of a database. No HTML knowledge required.) But the real question I want to ask is, To what degree do existing CMS applications force a sort of vendor lock-in? The vast majority of the applications I've looked, briefly, are PHP/MySQL combinations. This means some relational database is created, complete with application-specific tables, records, and fields. The PHP code then does I/O against the database to create and maintain website content. Cool. Suppose I invested my time and energy into one of these systems? For a long time it does what it is expected to do. Suppose then it breaks, becomes no longer supported, or a newer/cooler application comes along. How am I expected to get my content out of the first CMS and into second application? At least in Library Land we have MARC records (ick) to allow for some sort of migration path. I'm a bit hesitant when it comes to CMS application. Should I rely on the community at this point to come up with a solution? Yea, I can read the underlying database, create a cross-walk, do some magic, port from one system to anther, and hope to retain the better part of my functionality, but some things always get lost in translation. To what degree should website administrators be concerned with such things? Back-end content creators might simply see the easy-of-use of creating content. Geeky people, like me, might see a severe problem for the future. Y'alls input would be greatly appreciated. -- Eric Lease Morgan
Re: [CODE4LIB] yaoss4ll [cms]
Eric, What's great about some of these systems is that there are modules written to do exactly what you are talking about. For example there is a Drupal module that will allow to export your Wordpress site and import it into Drupal. Most of the PHP/MySQL CMSs I've played with have an underlying framework that makes this much easier than messing with the database tables natively. Also, many of these systems are looking to expose their data in structured ways which can be accessed by other systems. So web services are becoming a big part of these systems. I believe that Silverstripe has web services natively and there are several web sevice modules for Drupal. In terms of vendor lock in, I just don't see it that way. Because Wordpress and Drupal are open source, support can be provided from a variety of vendors. Many Drupal vendors contribute modules and other code. Because of this variety you aren't reliant on a single provider to chose to continue to support a particular product. If an open source CMS does go away then many, many community members will be doing migration and it is VERY likily that migraiton scripts/modules will get written and shared with the community. Certainly I saw this when huge numbers of blogs migrated from Movable Type to Wordpress. Hope this helps. Karen On Mon, Jan 4, 2010 at 10:17 AM, Eric Lease Morgan eric_mor...@infomotions.com wrote: On Jan 4, 2010, at 10:54 AM, Alejandro Garza Gonzalez wrote: I second John Fereira's comment re: putting this information into a CMS =) For instance it'd be awesome to browse by language... For the past week or so I have been trying to evaluate content management systems (CMS). Boy, there are bunches of them out there! Lot's of choice. The market is so much more mature in this area compared to librayr-specific open source applications. (Ironically, MyLibrary is/was sort of like a CMS in that it was intended to create certain types of Web pages based on the content of a database. No HTML knowledge required.) But the real question I want to ask is, To what degree do existing CMS applications force a sort of vendor lock-in? The vast majority of the applications I've looked, briefly, are PHP/MySQL combinations. This means some relational database is created, complete with application-specific tables, records, and fields. The PHP code then does I/O against the database to create and maintain website content. Cool. Suppose I invested my time and energy into one of these systems? For a long time it does what it is expected to do. Suppose then it breaks, becomes no longer supported, or a newer/cooler application comes along. How am I expected to get my content out of the first CMS and into second application? At least in Library Land we have MARC records (ick) to allow for some sort of migration path. I'm a bit hesitant when it comes to CMS application. Should I rely on the community at this point to come up with a solution? Yea, I can read the underlying database, create a cross-walk, do some magic, port from one system to anther, and hope to retain the better part of my functionality, but some things always get lost in translation. To what degree should website administrators be concerned with such things? Back-end content creators might simply see the easy-of-use of creating content. Geeky people, like me, might see a severe problem for the future. Y'alls input would be greatly appreciated. -- Eric Lease Morgan
Re: [CODE4LIB] yaoss4ll [cms]
On Jan 4, 2010, at 12:06 PM, Karen Coombs wrote: What's great about some of these systems is that there are modules written to do exactly what you are talking about... Hope this helps. Yes, this makes sense. Thank you for elaborating. I think the next time we do the website redesign thang we may very well go the CMS route. -- Eric Lease Morgan
Re: [CODE4LIB] yaoss4ll
On Dec 21, 2009, at 2:59 PM, John Fereira wrote: Any thoughts on making this list something more dynamic, web 2.0ish?... There certainly seems to be a demand for a more up-to-date list of library-related open source software, and as alluded to previously, such a thing has been attempted a number of times. Creating and maintaining such a list for the long haul -- no matter what technology is used -- would have to be a labor of love. -- Eric Morgan
Re: [CODE4LIB] yaoss4ll
Putting it on a wiki anyone can edit makes it, perhaps, somewhat more likely that it ends up maintained longer, making it easier for other people to get involved in maintaining it without technological barriers or proprietary feelings getting in the way. Jonathan Eric Lease Morgan wrote: On Dec 21, 2009, at 2:59 PM, John Fereira wrote: Any thoughts on making this list something more dynamic, web 2.0ish?... There certainly seems to be a demand for a more up-to-date list of library-related open source software, and as alluded to previously, such a thing has been attempted a number of times. Creating and maintaining such a list for the long haul -- no matter what technology is used -- would have to be a labor of love.
Re: [CODE4LIB] yaoss4ll
Jonathan Rochkind wrote: Putting it on a wiki anyone can edit makes it, perhaps, somewhat more likely that it ends up maintained longer, making it easier for other people to get involved in maintaining it without technological barriers or proprietary feelings getting in the way. I was thinking of something more along the lines of putting it into a CMS (i.e. Drupal) so that voting/ranking/tagging tools could be used to allow the community to rate the viability and discovery of each item. I may actually need to do something like this but for a different domain on a project that I'll be working on over the next year. -- John Fereira Cornell University Twitter: @john_fereira Google Wave: fere...@googlewave.com
Re: [CODE4LIB] yaoss4ll
How about putting the data into freebase? http://www.freebase.com/ That would combine the write-access of a wiki with the structure of a database. I was getting ready to compile a very similar dataset myself, so I'd be happy to do some of the requisite munging to get the data into freebase, if the idea appeals to anyone. On 12/22/2009 1:25 PM, John Fereira wrote: Jonathan Rochkind wrote: Putting it on a wiki anyone can edit makes it, perhaps, somewhat more likely that it ends up maintained longer, making it easier for other people to get involved in maintaining it without technological barriers or proprietary feelings getting in the way. I was thinking of something more along the lines of putting it into a CMS (i.e. Drupal) so that voting/ranking/tagging tools could be used to allow the community to rate the viability and discovery of each item. I may actually need to do something like this but for a different domain on a project that I'll be working on over the next year. attachment: rockliff.vcf
Re: [CODE4LIB] yaoss4ll
I would definitely nominate the Qubit Toolkit and the PKP software suite as candidates for this list: http://qubit-toolkit.org/ http://pkp.sfu.ca/ Qubit is somewhat nascent, but is actively being developed and is fairly well-supported (by the ICA, UNESCO, LAC, among others), and the PKP suite (most known for Open Journal Systems) is very well-established in the academic library world internationally. Roughly, I'd say that Qubit fits under archival record manager/editor (similar to Archon) and the PKP OAI harvester in particular fits somewhere under discovery system or similar (as an OAI aggregator). MJ On 2009-12-21, at 12:49 PM, Eric Lease Morgan wrote: I am in the process of creating YAOSS4LL (Yet Another Open Source Software For Libraries List), and I'm hoping to garner the expertise of our communities. More specifically, I would like to create a (more or less) comprehensive list of library-related open source software in the following areas: * content management systems (CMS) * discovery systems * electronic resource management (ERM) * institutional repositories (IR) * integrated library systems (ILS) * resource sharing/interlibrary loan (ILL) Unfortunately, I am being challenged when it comes to ERMs and resource sharing/ILL applications. The other areas seem well-developed. You can see what I've done so far at the following (temporary) link: http://infomotions.com/tmp/oss/ Do you have any suggestions or additions? Is your (favorite) library-related OSS application missing from my list? -- Eric (Lease) Morgan
Re: [CODE4LIB] yaoss4ll
On Dec 21, 2009, at 12:55 PM, MJ Suhonos wrote: I would definitely nominate the Qubit Toolkit and the PKP software suite as candidates for this list: http://qubit-toolkit.org/ http://pkp.sfu.ca/ Perfecto! Added locally. Thank you. -- Eric Morgan
Re: [CODE4LIB] yaoss4ll
Eric, Archivists' Toolkit (www.archiviststoolkit.org) is conspicuously absent from your list of library OS CMS systems. As you probably know, integration of AT and Archon is impending, a point you might want to draw attention to in your list. Cheers, Brad Westbrook AT Project Manager -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Eric Lease Morgan Sent: Monday, December 21, 2009 9:50 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] yaoss4ll I am in the process of creating YAOSS4LL (Yet Another Open Source Software For Libraries List), and I'm hoping to garner the expertise of our communities. More specifically, I would like to create a (more or less) comprehensive list of library-related open source software in the following areas: * content management systems (CMS) * discovery systems * electronic resource management (ERM) * institutional repositories (IR) * integrated library systems (ILS) * resource sharing/interlibrary loan (ILL) Unfortunately, I am being challenged when it comes to ERMs and resource sharing/ILL applications. The other areas seem well-developed. You can see what I've done so far at the following (temporary) link: http://infomotions.com/tmp/oss/ Do you have any suggestions or additions? Is your (favorite) library-related OSS application missing from my list? -- Eric (Lease) Morgan
Re: [CODE4LIB] yaoss4ll
On Dec 21, 2009, at 1:27 PM, Westbrook, Bradley wrote: Archivists' Toolkit (www.archiviststoolkit.org) is conspicuously absent from your list of library OS CMS systems. As you probably know, integration of AT and Archon is impending, a point you might want to draw attention to in your list. -- Brad Westbrook AT Project Manager Easily added. Thank you very much. -- Eric This Is Working Morgan
Re: [CODE4LIB] yaoss4ll
On Dec 21, 2009, at 12:49 PM, Eric Lease Morgan wrote: http://infomotions.com/tmp/oss/ Thank you for the suggestions both on and off list. With your help I was able to increase my list of viable OSS projects by just less than twenty items. The 'Net really works. If you have other suggestions, then please don't hesitate to pass them along. -- Eric Lease Morgan
Re: [CODE4LIB] yaoss4ll
Any thoughts on making this list something more dynamic, web 2.0ish? I think the list could be even more useful if one could do some sort of faceted search on the information. Looking at the not-viable list it seems that many of the entries were considered not viable due to lack of support. It might be more useful if some sort of level of support ranking could be used rather than just deem some of the tools as not viable. If a particular open source app is really useful, but lacks support, it *could* be viable if someone discovers it, and finds it useful enough that they're willing to start support it. John Fereira Cornell University Twitter: @john_fereira Google Wave: fere...@googlewave.com
Re: [CODE4LIB] yaoss4ll
Parts of one were started awhile back here: http://wiki.code4lib.org/index.php/OSS_Directory Ryan Wick -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of John Fereira Sent: Monday, December 21, 2009 11:59 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] yaoss4ll Any thoughts on making this list something more dynamic, web 2.0ish? I think the list could be even more useful if one could do some sort of faceted search on the information. Looking at the not-viable list it seems that many of the entries were considered not viable due to lack of support. It might be more useful if some sort of level of support ranking could be used rather than just deem some of the tools as not viable. If a particular open source app is really useful, but lacks support, it *could* be viable if someone discovers it, and finds it useful enough that they're willing to start support it. John Fereira Cornell University Twitter: @john_fereira Google Wave: fere...@googlewave.com
Re: [CODE4LIB] yaoss4ll
Eric, the Kete project is another one you might want to add to your list. It's intended to let libraries and archives create 'community repositories' with user-generated content, and it was started by the Horowhenua Library Trust, the same organisation that sponsored Koha. The URL is: http://kete.net.nz/ Brenda Chawner On Tue, Dec 22, 2009 at 6:49 AM, Eric Lease Morgan eric_mor...@infomotions.com wrote: I am in the process of creating YAOSS4LL (Yet Another Open Source Software For Libraries List), and I'm hoping to garner the expertise of our communities. More specifically, I would like to create a (more or less) comprehensive list of library-related open source software in the following areas: * content management systems (CMS) * discovery systems * electronic resource management (ERM) * institutional repositories (IR) * integrated library systems (ILS) * resource sharing/interlibrary loan (ILL) Unfortunately, I am being challenged when it comes to ERMs and resource sharing/ILL applications. The other areas seem well-developed. You can see what I've done so far at the following (temporary) link: http://infomotions.com/tmp/oss/ Do you have any suggestions or additions? Is your (favorite) library-related OSS application missing from my list? -- Eric (Lease) Morgan
Re: [CODE4LIB] yaoss4ll
Hi Eric, I don't see CDS Invenio listed [1]. It's an institutional repository system developed at CERN. It's an impressive piece of software, but for one reason or another doesn't seem to get much attention. I intend to give a lightning talk on it in Asheville in February. --jay [1] http://cdsware.cern.ch/invenio/index.html On Mon, Dec 21, 2009 at 12:49 PM, Eric Lease Morgan eric_mor...@infomotions.com wrote: I am in the process of creating YAOSS4LL (Yet Another Open Source Software For Libraries List), and I'm hoping to garner the expertise of our communities. More specifically, I would like to create a (more or less) comprehensive list of library-related open source software in the following areas: * content management systems (CMS) * discovery systems * electronic resource management (ERM) * institutional repositories (IR) * integrated library systems (ILS) * resource sharing/interlibrary loan (ILL) Unfortunately, I am being challenged when it comes to ERMs and resource sharing/ILL applications. The other areas seem well-developed. You can see what I've done so far at the following (temporary) link: http://infomotions.com/tmp/oss/ Do you have any suggestions or additions? Is your (favorite) library-related OSS application missing from my list? -- Eric (Lease) Morgan
