Photo Organizer

It would need a CAPTCHA or the like, to prevent spam..

This way people can easily contact a PO user, without having to publish real contact information.

We already copy over exif metadata to the preview images (#163) but we really need an explicit copyright notice and also a URL.

User would:

* Select some images
* Click on 'add keyword'
[ Window pops up prompting for a keyword ]
* User types in new ketword', clicks 'ok'
[ POST is sent in the background that adds a new keyword ]
* User is happy and sends PO developers lots of money.

It's possible that you might not have a given piece of equipment (eg lens or body) any more, so add a flag to the equipment tables to have them ignore certian rows.

(This is precipitated by one of my lenses being broken in two; I plan to buy an identical replacement, but it'll have a different serial number...)

In effect, this would merge datebook entries with the folder/album hierarchies.

I don't know if this is ultimately a good idea or not, but I've noticed that a majority of folders are keyed off specific date(s).

It has ramifications for the permission system (do we tie folders to clients, or rely on datebook events?)

It would also allow us to sort folders based on "event date" rather than "date added/changed" which is frankly far more useful for my purposes.

It would be nice to know at a glance whether or not we have a model release for a given person in a given photo.

releases are usually obtained in relation to specific events, so this should tie into the datebook.

Users would ahve to explicitly enable "adult" content in order for that to show up in searches, rss feeds, etc etc.

Need to work through use cases of this more carefully.

RE-do the advanced search so it's more useful -- allow any field to be searched, not just title, caption, etc etc... then build the query on the fly. This is going to be complicated, but necessary...

This one probably relates to other search-related Feature Requests. But to be specific.

When I'm displaying my Profile pages, I can see for example how many photos were shot with a specific lens, how many were shot with a certain camera, how many were shot on a particular film. But there is no quick way to display the photos matching the one criterion - it does not need to be a complex search, it should display photos only according to the one condition. It could be accessed by a simple link next to the count of photos (or clicking the count number itself?)

Thanks a lot

Jiri Vasina

Right now, it's:

thumb = raw -> scale -> colorspace (+extras) -> sharpen
prev = raw-> scale -> colorspace (+extras) -> sharpen -> watermark

IT would be REALLY nice if we could create customized processing paths; that is to say:

type_1 = raw -> scale -> b&w -> normalize -> sharpen
type_2 = raw -> scale -> add_border, add_text -> sharpen

This could either be on-demand, or automatic on uploads.

My wife asked for this, actually.

Basically, it would be handy to assign an album to be a "child" of a given folder, instead of having a totally separate hierarchy.

I don't think the converse would be as useful.

I'm very happy to have an automatic slideshow in photoview with the options: interval in seconds (1, 3, 5, 10, 15, 30), start and stop button. The slideshow should start at the current photo after pressing the start-button and automatically stop at the last photo of the current folder/album or by pressing the stop-button.

Right now there are three permissions -- public, private, and "protected", which equates to "public only to all of my clients"

This is pretty lousy; I can certianly envision scenarios where you'd want a client to only see stuff that's specific to that client. To do this now, you have to create separate accounts and mark clients for those specific accounts.

I'd like to see a more generic hierarchical user/group model. Only the photo owner can make changes to their images, but the permission model would break down as follows:

Permissions would be granted on a per-group basis, and individual users can be members of various groups. "Guest" access would just be another group, and would default to assigned.

A permission is inherited; so if "guest" is granted access to the top-level folder, they would be allowed to see everything below it unless a more restrictive permission was specified. This is sort of similar to unix permissions with the "sticky bit" turned on.

This gets a little tricky when talking about folders vs albums, as a user may not be allowed to browse the folder, but the image could be included in a public album. When viewing the image from the folder perspective, it would be disallowed, but from the album perspective, it would be allowed.

EDIT: see http://po.shaftnet.org/new_permission_model

1) Allow per-folder watermarks.
2) When "regenerating thumbnails" on bulk update, allow:
- existing watermark
- remove watermark
- new watermark
3) When performing an image rotation, preserve the existing watermarks.

right now "view counts" are part of the "photo" table.

It might be beneficial to split stats to a separate table.. we can track additional fields (views vs downloads vs ??) and also track it for each photo version etc.

Most database results are being indexed by position in a fixed array, rather than by column name. This may be slightly faster, but is hell to program around, especially when there can be twenty fields being returned.

* Convert all fetch_row() calls to fetch_assoc()

Secondly, using prepared statements would make the code a lot cleaner and eliminate the need to escape strings being passed in to the database. Unfortunately, this may require PHP 5.1 to pull off, depending on the maturity of the postgres bindings for earlier versions.

* Use prepared statements and SQL variables instead of inlined data.

What we have now is a decent start, but it needs a backand (and instructions for making it all click together)

The eventual goal is to let us "search for images like this one" and have it JustWork(tm).

Right now GNU GIFT (http://www.gnu.org/software/gift/) looks like the best bet as a backend; I just need to figure out how to make it all work.

Note that we really need search result caching to make this usable with a large image database.

if all pages are explicit redirects, we can use POSTs everywhere and still have navigability.

I capture the majority of photos on film, process it myself, print or scan it myself. A lot of people my do the same. I would like to see an option to note down the way I developed the film. IMO it would be best done in the following fashion:

have a table with development instructions (could have fields like: "id"?, "name", "developer", "dillution", "time", "agitation", "temperature", "notes"). The editing would be done in a similar way as for locations. This info would than be linked (through the id field?) as a technical informaion for the photo.

If there was the possibility to enter these information, I would not have to have a separate database/excel sheets noting this down.

Thanks a lot

Jiri

A running statistic of most used focal lengths (can be expanded to any EXIF/IPTC property like most used lens, flash usage and so on).

Something like this: http://billigites.blogspot.com/2005/06/focal-length-statistics.html

Invaluable to decide which lens to buy next. :-)

There is no easy way to add/edit the list of film format sizes appart from editing the database (or using a tool like phpPgAdmin). It would be nice and IMO simple to implement a way to add/edit a Film size option.

I think it would be a cool feature to make PO spatial enabled. I mean that it would be possible to use gps data (geolocated images) to search for "photo taken near some point" or "all the photo taken near some street". Or simply to create an interface a la panoramio for look/find for pictures. It should be not to difficult to implement.

Some programs like Raw Therapee creates a file to store all metadata to convert a raw file to a jpg file. To repeat the convert process (with or without slightly differences) it would be nice if I'm able to store such metadata with variants at the side of the original picture.

From other programs that storing data in a database, it would be possible to read out the data from the DB and storing metadata into xml-files and backwards.

It would be great if PO could make use of automated documentation tools such as Doxygen or PHP-Documentor.

It is now a time consuming task to start understanding the inner workings of PO as you need both an overview of the database schema and the logic in the code.

With a bit more documentation about the files and the routines in PO solving bugs or contributing code will become much easier.

http://www.sai.msu.su/~megera/wiki/Tsearch_V2_Readme

It's supposedly been part of the "core contrib" postgresql stuff since v7.4

This would let us perform a search on specific keywords across *all* indexed fields simultaneously.