imageserver

Graphic Apps

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

0
Score 50.0%
Description:

ImageServer is a software for maintaining archives of images. There's much software available to manually view, categorize and search images. ImageServer was designed to solve a different problem:

Imagine being a photographer or photo agency: You have a lot of images in many formats, all stored in a directory structure - your archive.

This creates at least two problems:

- The archive may contain different images with the same name. What do you do when a customer orders "flowers.tif" and this name exists in twenty different subfolders in your archive?

- The customer doesn't need your original 22megapixel 16-bit tiff file for his powerpoint presentation or layouting, he wants a small jpeg instead.

The first problem can be managed by assigning unique names to images every time an image is put into the archive.

The second problem is a little more difficult. You'll have to convert the requested images to smaller JPEGs. After doing that for too many times, you start caching the small JPEGs so you won't have to convert again for the next customer asking for that image. But then, you edit the original image and forget to update the JPEGs. Furthermore, its not enough to keep these resized jpegs for presentations, your customer's graphics department also wants correctly downsampled eps images for layouting advertisements in QuarkXPress. So you start having two slaveArchives - one with JPEG and one with EPS images - and spend half of your day trying to synchronize the three.

ImageServer solves both problems automatically. It is a program with a nice GUI, configured to watch your masterArchive. As soon as images are put into any subfolder, they'll be assigned unique names if necessary. Afterwards, each image is read, and for each defined slaveArchive, a preview is created and saved. The same happens when an image in the masterArchive is altered. All this works completely automatically, there's nothing you'll have to do; the GUI is just for being able to watch what's happening.

I know that there's probably not many people interested in using this, as its very specialized. But please, tell me below what you think!
Last changelog:

14 years ago

Added a WorkQueue manager
Added possibility to remove single events and all events from workqueue
Now using KDE ListViews for alternative row background color, increasing readability
ImageServer is now a KApplication (using nice icons etc.)
Now using KDE icons from the KDE dir, instead of copying them
Its possible to arrange the UI to your personal preference using a swappable and rotatable slider

northerndigitals

14 years ago

I'm on SUSE 10.0 - how do I install this?

Report

HabIB

14 years ago

I didn't test your app yet but this sounds like a very good idea. This could be a killer app not only for photography agencies but also for every webshob owner. We own a webshop and have to manage thousands of product pictures in different sizes and formats.

I think using a normal directory as an archive is a bad idea. As many people work on pictures everybody has to mount the archive via NFS for central administration. This is not always possible and unix permissions do not allow a very fine granularity of access. Another problem is that you do not really have version control with a plain filesystem directory.

Here is my personal wishlist for such a program:

- WebDAV support (instead of using a directory as archive) for network wide access, version control and access permissions.
- ability to assign and search for properties (i.e. description, date, vendor, product, color,..) of a picture.
- template support to predefine often used picture formats, sizes, output paths,... for easier conversion.

Greets,
HabIB

Report

C

kernelpanic

14 years ago

Hi!

Well, you can of course share the master- and slaveArchives via http, samba, nfs, ftp or whatever else you want. As long as imageserver runs on that server, it'll be notified of filesystem events no matter how you access those files. I don't know of an operating system that cannot use at least one of these options.

I think Unix-permissions are not a problem if you use samba, nfs or ftp, since ACLs should work fine with them?!

About versioning: You're right. This is why imageserver automatically creates new names for files not matching the folder's naming scheme. But real versioning would be really great!

Unfortunately, I couldn't find ANY docs on how to use webdav and its versioning features. Can you point me to a document or howto?

Then again, we have thousands images that regularly exceed 60 megabytes. Versioning-instead-of-overwriting-old-versions means we'd probably have even more data to cope with...

I'm almost done creating an(other) advanced HTML/PHP frontend which can be used to classify, search, browse, order, and download images and set their permissions for users and groups. It works very nicely, especially together with imageserver :)

Report

HabIB

14 years ago

> I think Unix-permissions are not a problem if you use samba, nfs or ftp, since ACLs should work fine with them?!

Yes, you're right - ACLs should work but they are a pain in the ass :)

> Unfortunately, I couldn't find ANY docs on how to use webdav and its versioning features. Can you point me to a document or howto?

Unfortunately there are no real Howtos for WebDav as it is a relatively new protocol. The only real documentation is RFC 2518.
http://asg.web.cmu.edu/rfc/rfc2518.html

But there a many good articles on http://www.webdav.org/. You can also find DAV client implementations and links to other resources on this site. You might be able to use the KDE DAV ioslave, too. It would be great if you could implement DAV support as you also have the ability to assign attributes to resources (=files) and search for them. DAV could do a lot of the dirty work your program has to do now.

> Then again, we have thousands images that regularly exceed 60 megabytes. Versioning-instead-of-overwriting-old-versions means we'd probably have even more data to cope with...

Well, in a photo agency you might have images of this size. Our raw images are only about 3-6 MB. Besides I think that disk space is no longer a problem these days.

Greets,
HabIB

Report

14 years ago

Added a WorkQueue manager
Added possibility to remove single events and all events from workqueue
Now using KDE ListViews for alternative row background color, increasing readability
ImageServer is now a KApplication (using nice icons etc.)
Now using KDE icons from the KDE dir, instead of copying them
Its possible to arrange the UI to your personal preference using a swappable and rotatable slider

12345678910
product-maker Base: 4 x 5.0 Ratings
File (click to download) Version Description PackagetypeArchitectureRelease Channel Downloads Date Filesize DL OCS-Install MD5SUM
*Needs pling-store or ocs-url to install things
Pling
0 Affiliates
Details
license
version
0.5
updated May 20 2005
added Feb 15 2005
downloads 24h
0
mediaviews 24h 0
pageviews 24h 1
System Tags app software