<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Yet another potentially extremely useful module I didn't even know
existed! <br>
<br>
Can I make suggestion? Can we have a simple, one-page listing of all
Drupal modules, with appropriate tags, to allow for easy navigation and
visualization? Users can sort the list as they want. With a few
additional tags/facets (like core version supported, date, author,
etc..), imagine how fast you can find what's available and start
digging further.<br>
<br>
Here is a test I quickly put together for a subset of modules:
<a class="moz-txt-link-freetext" href="http://geo42.com/sites/drupal-modules.html">http://geo42.com/sites/drupal-modules.html</a> <br>
<br>
<br>
IMO, an automated list like this one is more helpful than any rating
system (almost always fraught with problems) or the current d.o module
lists (page-based, too much information, hard to quickly navigate.)
Ratings systems, blog posts, projects like drupaltoughlove.com, usage
statistics, etc..., are all great but only should be considered as part
of the whole. For me, they simply help direct where to look deeper. A
list like the above would make things simpler, faster.<br>
<br>
<br>
We all know that finding modules to use with Drupal is a difficult
task, one with real consequences. There are no easy answers yet. It's
a task that turns some first time users away from Drupal and continues
to frustrate some current Drupal practitioners. It's especially
frustrating when trying to convince others in your organization (like
the IT department) to go with Drupal; they start to delve into it and
get lost in what can be done practically and securely via Drupal. It's
a great development design but difficult in practice.<br>
<br>
<br>
- John<br>
<pre class="moz-signature" cols="72">**************************************************
John Callahan
Geospatial Application Developer
Delaware Geological Survey, University of Delaware
227 Academy St, Newark DE 19716-7501
Tel: (302) 831-3584
Email: <a class="moz-txt-link-abbreviated" href="mailto:john.callahan@udel.edu">john.callahan@udel.edu</a>
<a class="moz-txt-link-freetext" href="http://www.dgs.udel.edu">http://www.dgs.udel.edu</a>
**************************************************</pre>
<br>
<br>
Justin Gruenberg wrote:
<blockquote
cite="mid:96cd751f0905050031n440bb304t342bd682e21919f0@mail.gmail.com"
type="cite">
<pre wrap="">On Mon, May 4, 2009 at 8:20 AM, John Callahan <a class="moz-txt-link-rfc2396E" href="mailto:john.callahan@udel.edu"><john.callahan@udel.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">1) batch upload, even if only one directory
</pre>
</blockquote>
<pre wrap=""><!---->
<a class="moz-txt-link-freetext" href="http://drupal.org/project/image_fupload">http://drupal.org/project/image_fupload</a>
That module provides a pretty nice way for you to upload images.
Probably not 11k at a time nice, but it does work well and does allow
you to fiddle with some attributes per image when you upload. It
works with ImageField (CCK) and image.module.
If you go the image.module route, theres some other batch upload
modules that can work with a directory on the server.
</pre>
<blockquote type="cite">
<pre wrap="">2) reading EXIF/IPTC image metadata and mapping them to taxonomy terms
and/or CCK fields. 3) syncing attributes (i.e., edits to raw image EXIF/IPTC
can update/reimport the node fields/tags and edits to node fields/tags can
update the EXIF/IPTC metadata.)
</pre>
</blockquote>
<pre wrap=""><!---->
I haven't done anything this complex with image galleries, but I can
say... expect to do a good amount of fiddling and possibly writing
some custom code to get what you want.
</pre>
<blockquote type="cite">
<pre wrap="">I'm using Gallery2 right now (<a class="moz-txt-link-freetext" href="http://gallery.menalto.com/">http://gallery.menalto.com/</a>,
<a class="moz-txt-link-freetext" href="http://drupal.org/project/gallery">http://drupal.org/project/gallery</a>) and it does some (item #1 and partially
#2) of what I need. It even integrates nicely with Drupal for users and
display of images and albums. However, I use Drupal for many other sites
(and I'd like to use views, lightbox, tags, etc...) and wondering if I can
bypass Gallery altogether. Any thoughts or experiences out there? Thanks.
</pre>
</blockquote>
<pre wrap=""><!---->
I'd say if gallery2 works for you, stay with it. That's a package
thats built for hosting images. If you're not afraid of getting your
hands dirty, drupal might meet your needs closer.
--
[ Drupal support list | <a class="moz-txt-link-freetext" href="http://lists.drupal.org/">http://lists.drupal.org/</a> ]
</pre>
</blockquote>
</body>
</html>