Some ideas:
1) Use Feeds Imagegrabber (http://drupal.org/project/feeds_imagegrabber)
along with Feeds to create nodes that include their enclosures (cover
images) from the RSS feed. Once you have the items as nodes you can use
Views and the plethora of Views carrousel-like modules to display
If you are looking to build an application instead of getting an
existing one, you can use Drupal and several modules to build it.
There are several faceted search modules available (see
http://drupal.org/search/apachesolr_search/faceted%20search?filters=type%3Aproject_project).
For a
Well, I'll quickly run down why we chose Drupal (hence, PHP). I mention
Drupal because to me it's more of a framework which just happens to have
a CMS built on top of it =)
Before Drupal, my team knew PHP. We had PHP books in the library,
students were learning some PHP in classes, etc.
We
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 ...
/2009 06:01 p.m.:
Alejandro Garza Gonzalez wrote:
1) You *can* use GA and some Javascript embedded in your III pages to
log events (as they´re called in GA lingo). The javascript
(depending on your coding wizardry level) could track anything from
hovers over elements, form submission, next page
I see two ways to do this:
1) You *can* use GA and some Javascript embedded in your III pages to
log events (as they´re called in GA lingo). The javascript (depending
on your coding wizardry level) could track anything from hovers over
elements, form submission, next page events, etc.
2)
