[CODE4LIB] friendly reminder - eco4r-workshop 11./12.Nov. Cologne: Exposition and reuse of multipart publications from living repositories
*** Apologize for cross-posting *** Dear colleagues, we would like to draw your attention again to the eco4r workshop. The eco4r project (http://www.eco4r.org) aims to be a proof of existing concepts and standards (e.g. OAI-ORE, METS) for the exposure, exchangeability and reusability of compound objects within living repository systems. The eco4r team organizes a workshop to discuss early results with experts that are familiar and experienced in one or more of the fields of modeling compound objects, metadata standards and repository systems. We are very pleased to invite you to attend the workshop which is planned to take place on Nov. 11th and 12th 2010 at the Library Service Center in Cologne. You can also find the agenda and the registration form at the project web-site: http://www.eco4r.org/workshop2010. Sincerely, Jochen Schirrwagen, Anouar Boulal
[CODE4LIB] vufind, ead files, harvesting content, and text mining
I have written a couple of blog postings as well as bunches o' hacks surrounding VUFind, EAD files, harvesting content, and text mining that may be of interest to us coders: 1. EAD files - The first posting and set of Perl scripts describes how I am currently indexing MARC records, but more importantly, EAD files in VUFind. The process involves harvesting EAD files from remote locations, transforming them into HTML, indexing them at the container level, and providing access to the index. [1, 2] 2. Internet Archive content - The second posting describes how I mirrored content from the Internet archive, munged the mirrored MARC records, indexed them, and provided a rudimentary text mining interface against the locally cached full text. [3, 4] There are lots of cool (as well as kewl) possibilities here. [1] indexing EAD in VUFind - http://bit.ly/cIu0lG [2] EAD record in VUFind - http://bit.ly/9Z7GUg [3] Internet Archive content - http://bit.ly/dbzYyX [4] harvested record with text mining - http://bit.ly/ahjLf2 -- Eric @isitfriday Morgan
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
I use Python and Django extensively, and think they're both great. That said, also great is the very funny keynote by former flickr engineer Cal Henderson at DjangoCon 2008, titled Why I Hate Django, which is on YouTube: http://www.youtube.com/watch?v=i6Fr65PFqfk When he showed the slide I had to admit that the statement -.join(array) is kind of a goofy way to do that, though maybe not unforgivable. Whenever I use join() now I chuckle a little in my mind. It's good to step back and re-evaluate your favorite tools from time-to-time. If nothing else, the ability to analyze a platform for its suitability to a need is key. Will On Oct 28, 2010, at 9:38 AM, Thomas Bennett wrote: Having used Zope (python based) as our WEB server of choice since 1998 I am urged to express my opinion that if you do choose to use python in your projects then use a service designed for python use such as Zope, Django, et al. Zope is normally run in front of Apache as a virtual host. If you are going to use python then Zope is an excellent choice for interacting with databases and using python to massage/manipulate results if you need complex results from the database data. I like that you can write sql queries just like you might use on the command line and save it as an individual object for use by any number of other objects. What may be a simple example to some is a tutorial quiz I wrote for the WEB. There are categories and each category has any number of questions along with the answers in the database. In the management portion, the administrator can choose which categories are active and how many questions out of the total available to pull from each category individually. When the quiz page is generated the correct number of questions are pulled randomly from the total active questions for each category, some questions can be set as inactive. There are database connectors for PostgreSQL, MySQL, Oracle, odbc, and others so you can choose any popular db or write your own connector. And there are python libraries written for these databases which prove very useful. The main thing I like about python is that the syntax pretty much forces your code to be readable by others because indention is part of the syntax rather than semicolons, parens, etc. I don't know PHP in detail but am learning more quickly because the University is forcing all departments to move to Drupal and we will be running our site on Drupal within a year probably although some administrative tasks will still be running on our Zope server. Thomas ps: remember my point is that IF you choose to use python this supports its use with databases and scripting. On Wednesday 27 October 2010 20:49:06 you wrote: Olá, como vai? Luciano Ramalho luci...@ramalho.org wrote: Actually, Python is a general purpose programming language. It was not created specifically for server side scripting like PHP was. But it is very suitable to that task. I'm not sure talking about what something used to be is as interesting as talking about what it is. Both Pyhton and PHP can share whatever moniker we choose (scripting-language, programming language, real-time, half-time, bytecoded, virtual, etc.). Not seen any scientific packages, but I've seen a few ray-tracers, although they're all demo apps and fun toys (although I think that applies to Python, too). No, that does not apply to Python. Python is widely used for hardcore scientific computing. I was referring to the ray-tracing part. It is also the most important scripting language in large scale CGI settings Yes, Python is widely used for scripting up interfaces into other more complex systems. But rarely is the core of the thing written entirely in Python. Maybe your Google-foo is weak. :) Or maybe he's just realizing that outside of server side web scripting, PHP is just not so widely used. Absolutely, and fair enough. Having used both languages, I discovered that Python is easier for most tasks, and one reason is that the libraries that come with Python are extremely robust, well tested and consistent. Hmm. PHP is extremely robust and well-tested, but yes, it's not all that consistent, especially not before version 5.2+. However, things have moved on, and with release 6 around the corner things will be tighter still. Just like the first versions of Python were interesting, so was PHP's, but where the biggest problem with the evolution of PHP was the very fact that it was the most popular language for rapid web development by far. PHP is very practical for server-side web scripting, but it's libraries are unfortunately full of gotchas, traps and unexpected behaviour. There's gotchas in every language, even Python. A key reason for that is the fact that Python has always had an exception-handling mechanism while PHP has grown something like that only a few
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
I think the significant attributes of most programming languages are adequately summarized here: http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html From: Code for Libraries [code4...@listserv.nd.edu] on behalf of William Sexton [will.sex...@duke.edu] Sent: Friday, October 29, 2010 7:24 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] PHP vs. Python [was: Re: Django] I use Python and Django extensively, and think they're both great. That said, also great is the very funny keynote by former flickr engineer Cal Henderson at DjangoCon 2008, titled Why I Hate Django, which is on YouTube: http://www.youtube.com/watch?v=i6Fr65PFqfk When he showed the slide I had to admit that the statement -.join(array) is kind of a goofy way to do that, though maybe not unforgivable. Whenever I use join() now I chuckle a little in my mind. It's good to step back and re-evaluate your favorite tools from time-to-time. If nothing else, the ability to analyze a platform for its suitability to a need is key. Will On Oct 28, 2010, at 9:38 AM, Thomas Bennett wrote: Having used Zope (python based) as our WEB server of choice since 1998 I am urged to express my opinion that if you do choose to use python in your projects then use a service designed for python use such as Zope, Django, et al. Zope is normally run in front of Apache as a virtual host. If you are going to use python then Zope is an excellent choice for interacting with databases and using python to massage/manipulate results if you need complex results from the database data. I like that you can write sql queries just like you might use on the command line and save it as an individual object for use by any number of other objects. What may be a simple example to some is a tutorial quiz I wrote for the WEB. There are categories and each category has any number of questions along with the answers in the database. In the management portion, the administrator can choose which categories are active and how many questions out of the total available to pull from each category individually. When the quiz page is generated the correct number of questions are pulled randomly from the total active questions for each category, some questions can be set as inactive. There are database connectors for PostgreSQL, MySQL, Oracle, odbc, and others so you can choose any popular db or write your own connector. And there are python libraries written for these databases which prove very useful. The main thing I like about python is that the syntax pretty much forces your code to be readable by others because indention is part of the syntax rather than semicolons, parens, etc. I don't know PHP in detail but am learning more quickly because the University is forcing all departments to move to Drupal and we will be running our site on Drupal within a year probably although some administrative tasks will still be running on our Zope server. Thomas ps: remember my point is that IF you choose to use python this supports its use with databases and scripting. On Wednesday 27 October 2010 20:49:06 you wrote: Olá, como vai? Luciano Ramalho luci...@ramalho.org wrote: Actually, Python is a general purpose programming language. It was not created specifically for server side scripting like PHP was. But it is very suitable to that task. I'm not sure talking about what something used to be is as interesting as talking about what it is. Both Pyhton and PHP can share whatever moniker we choose (scripting-language, programming language, real-time, half-time, bytecoded, virtual, etc.). Not seen any scientific packages, but I've seen a few ray-tracers, although they're all demo apps and fun toys (although I think that applies to Python, too). No, that does not apply to Python. Python is widely used for hardcore scientific computing. I was referring to the ray-tracing part. It is also the most important scripting language in large scale CGI settings Yes, Python is widely used for scripting up interfaces into other more complex systems. But rarely is the core of the thing written entirely in Python. Maybe your Google-foo is weak. :) Or maybe he's just realizing that outside of server side web scripting, PHP is just not so widely used. Absolutely, and fair enough. Having used both languages, I discovered that Python is easier for most tasks, and one reason is that the libraries that come with Python are extremely robust, well tested and consistent. Hmm. PHP is extremely robust and well-tested, but yes, it's not all that consistent, especially not before version 5.2+. However, things have moved on, and with release 6 around the corner things will be tighter still. Just like the first versions of Python were interesting, so was PHP's, but where the biggest problem with the evolution of PHP was the very fact that it was the most popular
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
Have people found Django fairly usable without using its ORM features? I'm not a big ORM fan, and it seems that so many Python frameworks sort of fall over if you try to get around the ORM. It's a bit of a shame, because I like Python. I wish Bottle and Flask were a little easier to work with. It feels a little weird having to configure WSGI for each application. I love their minimalist approach to templating, though. Mark On Oct 29, 2010, at 4:14 PM, Genny Engel wrote: I think the significant attributes of most programming languages are adequately summarized here: http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html From: Code for Libraries [code4...@listserv.nd.edu] on behalf of William Sexton [will.sex...@duke.edu] Sent: Friday, October 29, 2010 7:24 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] PHP vs. Python [was: Re: Django] I use Python and Django extensively, and think they're both great. That said, also great is the very funny keynote by former flickr engineer Cal Henderson at DjangoCon 2008, titled Why I Hate Django, which is on YouTube: http://www.youtube.com/watch?v=i6Fr65PFqfk When he showed the slide I had to admit that the statement -.join(array) is kind of a goofy way to do that, though maybe not unforgivable. Whenever I use join() now I chuckle a little in my mind. It's good to step back and re-evaluate your favorite tools from time- to-time. If nothing else, the ability to analyze a platform for its suitability to a need is key. Will On Oct 28, 2010, at 9:38 AM, Thomas Bennett wrote: Having used Zope (python based) as our WEB server of choice since 1998 I am urged to express my opinion that if you do choose to use python in your projects then use a service designed for python use such as Zope, Django, et al. Zope is normally run in front of Apache as a virtual host. If you are going to use python then Zope is an excellent choice for interacting with databases and using python to massage/manipulate results if you need complex results from the database data. I like that you can write sql queries just like you might use on the command line and save it as an individual object for use by any number of other objects. What may be a simple example to some is a tutorial quiz I wrote for the WEB. There are categories and each category has any number of questions along with the answers in the database. In the management portion, the administrator can choose which categories are active and how many questions out of the total available to pull from each category individually. When the quiz page is generated the correct number of questions are pulled randomly from the total active questions for each category, some questions can be set as inactive. There are database connectors for PostgreSQL, MySQL, Oracle, odbc, and others so you can choose any popular db or write your own connector. And there are python libraries written for these databases which prove very useful. The main thing I like about python is that the syntax pretty much forces your code to be readable by others because indention is part of the syntax rather than semicolons, parens, etc. I don't know PHP in detail but am learning more quickly because the University is forcing all departments to move to Drupal and we will be running our site on Drupal within a year probably although some administrative tasks will still be running on our Zope server. Thomas ps: remember my point is that IF you choose to use python this supports its use with databases and scripting. On Wednesday 27 October 2010 20:49:06 you wrote: Olá, como vai? Luciano Ramalho luci...@ramalho.org wrote: Actually, Python is a general purpose programming language. It was not created specifically for server side scripting like PHP was. But it is very suitable to that task. I'm not sure talking about what something used to be is as interesting as talking about what it is. Both Pyhton and PHP can share whatever moniker we choose (scripting-language, programming language, real-time, half-time, bytecoded, virtual, etc.). Not seen any scientific packages, but I've seen a few ray-tracers, although they're all demo apps and fun toys (although I think that applies to Python, too). No, that does not apply to Python. Python is widely used for hardcore scientific computing. I was referring to the ray-tracing part. It is also the most important scripting language in large scale CGI settings Yes, Python is widely used for scripting up interfaces into other more complex systems. But rarely is the core of the thing written entirely in Python. Maybe your Google-foo is weak. :) Or maybe he's just realizing that outside of server side web scripting, PHP is just not so widely used. Absolutely, and fair enough. Having used both languages, I discovered that Python is
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
Mark- I would highly recommend looking at Tornado (http://www.tornadoweb.org) as an alternative to using Django without the ORM. It provides URL dispatch and templating capabilities without commitment to a particular storage model, and is fast in standalone use, without requiring extra scaffolding like WSGI. It has been an extremely productive framework for me. - BPA Bradley P. Allen http://bradleypallen.org On Fri, Oct 29, 2010 at 1:30 PM, Mark Tomko mark.to...@simmons.edu wrote: Have people found Django fairly usable without using its ORM features? I'm not a big ORM fan, and it seems that so many Python frameworks sort of fall over if you try to get around the ORM. It's a bit of a shame, because I like Python. I wish Bottle and Flask were a little easier to work with. It feels a little weird having to configure WSGI for each application. I love their minimalist approach to templating, though. Mark On Oct 29, 2010, at 4:14 PM, Genny Engel wrote: I think the significant attributes of most programming languages are adequately summarized here: http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html From: Code for Libraries [code4...@listserv.nd.edu] on behalf of William Sexton [will.sex...@duke.edu] Sent: Friday, October 29, 2010 7:24 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] PHP vs. Python [was: Re: Django] I use Python and Django extensively, and think they're both great. That said, also great is the very funny keynote by former flickr engineer Cal Henderson at DjangoCon 2008, titled Why I Hate Django, which is on YouTube: http://www.youtube.com/watch?v=i6Fr65PFqfk When he showed the slide I had to admit that the statement -.join(array) is kind of a goofy way to do that, though maybe not unforgivable. Whenever I use join() now I chuckle a little in my mind. It's good to step back and re-evaluate your favorite tools from time-to-time. If nothing else, the ability to analyze a platform for its suitability to a need is key. Will On Oct 28, 2010, at 9:38 AM, Thomas Bennett wrote: Having used Zope (python based) as our WEB server of choice since 1998 I am urged to express my opinion that if you do choose to use python in your projects then use a service designed for python use such as Zope, Django, et al. Zope is normally run in front of Apache as a virtual host. If you are going to use python then Zope is an excellent choice for interacting with databases and using python to massage/manipulate results if you need complex results from the database data. I like that you can write sql queries just like you might use on the command line and save it as an individual object for use by any number of other objects. What may be a simple example to some is a tutorial quiz I wrote for the WEB. There are categories and each category has any number of questions along with the answers in the database. In the management portion, the administrator can choose which categories are active and how many questions out of the total available to pull from each category individually. When the quiz page is generated the correct number of questions are pulled randomly from the total active questions for each category, some questions can be set as inactive. There are database connectors for PostgreSQL, MySQL, Oracle, odbc, and others so you can choose any popular db or write your own connector. And there are python libraries written for these databases which prove very useful. The main thing I like about python is that the syntax pretty much forces your code to be readable by others because indention is part of the syntax rather than semicolons, parens, etc. I don't know PHP in detail but am learning more quickly because the University is forcing all departments to move to Drupal and we will be running our site on Drupal within a year probably although some administrative tasks will still be running on our Zope server. Thomas ps: remember my point is that IF you choose to use python this supports its use with databases and scripting. On Wednesday 27 October 2010 20:49:06 you wrote: Olá, como vai? Luciano Ramalho luci...@ramalho.org wrote: Actually, Python is a general purpose programming language. It was not created specifically for server side scripting like PHP was. But it is very suitable to that task. I'm not sure talking about what something used to be is as interesting as talking about what it is. Both Pyhton and PHP can share whatever moniker we choose (scripting-language, programming language, real-time, half-time, bytecoded, virtual, etc.). Not seen any scientific packages, but I've seen a few ray-tracers, although they're all demo apps and fun toys (although I think that applies to Python, too). No, that does not apply to Python. Python is widely used for hardcore scientific computing. I was referring to the
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
On Sat, Oct 30, 2010 at 7:49 AM, Bradley Allen bradley.p.al...@gmail.com wrote: Mark- I would highly recommend looking at Tornado (http://www.tornadoweb.org) as an alternative to using Django without the ORM. I'd second that one. Has used it for a couple of projects, and it seriously cut down on prerequisite clutter and is super fast. Alex -- Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps --- http://shelter.nu/blog/ -- -- http://www.google.com/profiles/alexander.johannesen ---
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
Thanks to you both - that looks promising! Mark On Oct 29, 2010, at 4:57 PM, Alexander Johannesen wrote: On Sat, Oct 30, 2010 at 7:49 AM, Bradley Allen bradley.p.al...@gmail.com wrote: Mark- I would highly recommend looking at Tornado (http://www.tornadoweb.org) as an alternative to using Django without the ORM. I'd second that one. Has used it for a couple of projects, and it seriously cut down on prerequisite clutter and is super fast. Alex -- Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps --- http://shelter.nu/blog/ -- -- http://www.google.com/profiles/ alexander.johannesen ---
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
What's wrong with the library world developing its own domain language? From scratch. I mean not something like MARC that is just a static container for stuff, but a language that actually does something such as manipulating semantic maps or some such? It's not like things like PHP or Python or Django were handed down to us chiseled in stone tablets. All languages are arbitrary things anyway, and it doesn't matter how they are implemented. The point is to keep the layers of abstraction well defined. But otherwise, break down those walls. Peter Schlumpf www.avantilibrarysystems.com -Original Message- From: Mark Tomko mark.to...@simmons.edu Sent: Oct 29, 2010 3:30 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] PHP vs. Python [was: Re: Django] Have people found Django fairly usable without using its ORM features? I'm not a big ORM fan, and it seems that so many Python frameworks sort of fall over if you try to get around the ORM. It's a bit of a shame, because I like Python. I wish Bottle and Flask were a little easier to work with. It feels a little weird having to configure WSGI for each application. I love their minimalist approach to templating, though. Mark On Oct 29, 2010, at 4:14 PM, Genny Engel wrote: I think the significant attributes of most programming languages are adequately summarized here: http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html From: Code for Libraries [code4...@listserv.nd.edu] on behalf of William Sexton [will.sex...@duke.edu] Sent: Friday, October 29, 2010 7:24 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] PHP vs. Python [was: Re: Django] I use Python and Django extensively, and think they're both great. That said, also great is the very funny keynote by former flickr engineer Cal Henderson at DjangoCon 2008, titled Why I Hate Django, which is on YouTube: http://www.youtube.com/watch?v=i6Fr65PFqfk When he showed the slide I had to admit that the statement -.join(array) is kind of a goofy way to do that, though maybe not unforgivable. Whenever I use join() now I chuckle a little in my mind. It's good to step back and re-evaluate your favorite tools from time- to-time. If nothing else, the ability to analyze a platform for its suitability to a need is key. Will On Oct 28, 2010, at 9:38 AM, Thomas Bennett wrote: Having used Zope (python based) as our WEB server of choice since 1998 I am urged to express my opinion that if you do choose to use python in your projects then use a service designed for python use such as Zope, Django, et al. Zope is normally run in front of Apache as a virtual host. If you are going to use python then Zope is an excellent choice for interacting with databases and using python to massage/manipulate results if you need complex results from the database data. I like that you can write sql queries just like you might use on the command line and save it as an individual object for use by any number of other objects. What may be a simple example to some is a tutorial quiz I wrote for the WEB. There are categories and each category has any number of questions along with the answers in the database. In the management portion, the administrator can choose which categories are active and how many questions out of the total available to pull from each category individually. When the quiz page is generated the correct number of questions are pulled randomly from the total active questions for each category, some questions can be set as inactive. There are database connectors for PostgreSQL, MySQL, Oracle, odbc, and others so you can choose any popular db or write your own connector. And there are python libraries written for these databases which prove very useful. The main thing I like about python is that the syntax pretty much forces your code to be readable by others because indention is part of the syntax rather than semicolons, parens, etc. I don't know PHP in detail but am learning more quickly because the University is forcing all departments to move to Drupal and we will be running our site on Drupal within a year probably although some administrative tasks will still be running on our Zope server. Thomas ps: remember my point is that IF you choose to use python this supports its use with databases and scripting. On Wednesday 27 October 2010 20:49:06 you wrote: Olá, como vai? Luciano Ramalho luci...@ramalho.org wrote: Actually, Python is a general purpose programming language. It was not created specifically for server side scripting like PHP was. But it is very suitable to that task. I'm not sure talking about what something used to be is as interesting as talking about what it is. Both Pyhton and PHP can share whatever moniker we choose
[CODE4LIB] Semanic Web Journal Issue on Semantic Web and Reasoning for Cultural Heritage and Digital Libraries
(Apologies for cross postings) * Call for Papers* * * * Semantic Web Journal * * (URL: http://www.semantic-web-journal.net/) * * * * Special Issue on * * Semantic Web and Reasoning for Cultural Heritage and Digital Libraries* * * URL: http://www.semantic-web-journal.net/blog/special-issue-semantic-web-and-reasoning-cultural-heritage-and-digital-libraries Short URL: http://bit.ly/a6HmTk === Description === During the past few years, great and continually increasing scientific interest has been paid towards the efficient dissemination and management of the world's cultural assets on the Web. As more and more cultural heritage institutions tend to exploit World Wide Web's technologies in order to render their collections globally available, integrated access to this vast amount of content has become an imperative need. Traditionally, the main requisite for integrating diverse resources has been syntactic interoperability. However, in the more knowledge-intensive world of the Semantic Web a number of powerful techniques are offering the promise of knowledge-based management and retrieval instead of mere syntactic data exchange. In particular, techniques for obtaining semantic interoperability and reasoning over metadata and ontologies have been proven powerful tools towards this direction. In the cultural heritage field, significant efforts have been initiated for achieving semantic-aware data integration, but many issues are still under discussion and problems remain unsolved. Hundreds of existing digital libraries and repository systems, responsible for gathering and disseminating digital objects originating from cultural assets, still lack common standards and best practices for properly ingesting and publishing knowledge. The community is looking for powerful semantic search and navigation mechanisms able to efficiently retrieve and interlink distributed, heterogeneous knowledge about cultural heritage. In addition, it is not clear what might be the most suitable evaluation techniques for analyzing the suggested methods and tools. == Topics == This special issue solicits contributions to the open problems of publishing cultural content on the Semantic Web, such as innovative techniques, tools, case studies, comparisons, and theoretical advances. The papers should consider and present contributions towards representing semantic aspects of cultural heritage information in the web environment, i.e. aspects of modeling, creating, aggregating, managing, publishing, and using content on the Semantic Web in the cultural heritage field. In particular, topics of interest include, but are not limited to, the following: - Semantic-enabled search and recommending - Reasoning over cultural heritage information - Semantic content creation and annotation - Semantic integration of heterogeneous and contradicting information - Ontologies and vocabularies for cultural heritage - Linked heritage data and its applications - Semantic aging and ontology evolution - Evaluation of semantic techniques and systems - Web 2.0, collaborative systems, tagging, and user feedback - Semantic and mental maps of interlinked cultural content - Visualization techniques and paradigms - Success reports of in-use applications and projects === Submissions === High-quality papers containing original research results on the above and related topics are solicited. Extended versions of papers previously published in
Re: [CODE4LIB] PHP vs. Python [was: Re: Django]
On Fri, Oct 29, 2010 at 6:28 PM, Peter Schlumpf pschlu...@earthlink.netwrote: What's wrong with the library world developing its own domain language? EVERYTHING!!! We're already in a world of pain because we have our own data formats and ways of dealing with them, all of which have basically stood idle while 30 years of advances computer science and information architecture have whizzed by us with a giant WHOOSHing sound. Having a bunch of non-experts design and implement a language that's destined from the outset to be stuck in a tiny little ghetto of the programming world is a guaranteed way to live with half- or un-supported code, no decent libraries, and yet another legacy of pain we'd have to support. I'm not picking on programming in particular. It's a dumb-ass move EVERY time a library is presented with a problem for which there are experts and decades of research literature, and it choses to ignore all of that and decide to throw a committee of librarians (or whomever else happens to be in the building at the time) at it based on the vague idea that librarians are just that much smarter (or cheaper) than everyone else (I'm looking at you, usability...) -Bill- -- Bill Dueber Library Systems Programmer University of Michigan Library
