|
8 | Feature Request | Low | Backend / Core | Better permission hierarchy | Assigned | Devel |
Task Description
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 |
|
397 | Feature Request | Medium | Import | Import of metadata from programs like Raw Therapee | Unconfirmed | 2.36 |
Task Description
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. |
|
390 | Feature Request | Low | Backend / Core | gps data in a spatial enabled database? | Unconfirmed | 2.36 |
Task Description
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. |
|
184 | Feature Request | Low | User Interface | Format (film size) editing | Unconfirmed | 2.33 |
Task Description
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. |
|
11 | Feature Request | Low | Backend / Core | Clean up database conventions | Assigned | Devel |
Task Description
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. |
|
180 | Feature Request | Low | Database | Break out the statistics data | New | 2.33 |
Task Description
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. |
|
160 | Feature Request | Low | Import | better watermarking | New | Stable |
Task Description
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. |
|
89 | Feature Request | Low | Backend / Core | allow advanced search on any database field | Assigned | Devel |
Task Description
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... |
|
175 | Feature Request | Low | User Interface | show defined keywords in suplemental category | Unconfirmed | 2.33 |
Task Description
it would ease handling, if one could see the yet defined keywords: useless creation according to misspelling (landscape versus landscapes) or different words for the same meaning. |
|
244 | Feature Request | Low | Backend / Core | Allow for custom rendering paths | New | 2.33 |
Task Description
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. |
|
358 | Feature Request | Low | User Interface | Add a 'fast tagging' UI to the listing pages. | New | 2.35 |
Task Description
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. |
|
245 | Feature Request | Low | Database | Move 'access' and 'original' rights into 'files' table. | New | Devel |
Task Description
This way individual versions and scaled resolutions can be given appropriate rights; If we have the individual files with fine-grained permissions, then we can do away with the 'original' field altogether, and the 'access' field can be inferred from these settings (via a DB stored procedure) The original can be granted to be 'private' or 'protected', for example, while the watermarked preview is 'public', the non-watermarked preview is 'protected', and the thumbnail is 'public'. If we have the individual files with fine-grained permissions, then we can do away with the 'original' field altogether. If the viewer can access the thumbnails, then they can see the image on the browser list. If the viewer can access *any* of the preview images, the thumb links to the best-quality preview image. (ie resolution &| watermarking..). While looking at the preview, if they have access to the original, let them have it. |
|
185 | Feature Request | Low | Backend / Core | Development / printing information | Unconfirmed | 2.33 |
Task Description
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 |
|
420 | Bug Report | Low | User Interface | Really Minor Login Page Prob | Unconfirmed | 2.36 |
Task Description
It doesn't do any harm, it just bugs if it happens. If you fill in user name and password and then realize, you don't want the preset language... Switching to another language clears out user name and password and you have to write them again. Of course, this won't happen often to a new user because it trains to look first after the language, but... I would still call it a bug, even if not really major. Rock on Eckhard |
|
381 | Feature Request | Low | User Interface | 'last X photos' | Unconfirmed | 2.36 |
Task Description
> 'last X photos' could easily be implemented as a wrapper in include/site.php, much like the site_display_random_photos() function already is. |
|
239 | Feature Request | Low | Backend / Core | Integrate full-text search | New | Devel |
Task Description
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. |
|
327 | Feature Request | Low | Backend / Core | Focal length statistics | Unconfirmed | 2.34 |
Task Description
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. :-) |
|
100 | Feature Request | Low | Backend / Core | Content-based searching that works. :) | New | Devel |
Task Description
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. |
|
285 | Feature Request | Low | User Interface | Automatic slideshow | Unconfirmed | Devel |
Task Description
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. |
|
316 | Feature Request | Low | Backend / Core | Allow for sub-albums on the folder listing pages. | New | 2.34 |
Task Description
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. |
|
393 | Feature Request | Low | Backend / Core | Use GPS timestamp when importing, if present. | New | 2.36 |
Task Description
If we have a GPS tag, the odds are its timestamp is going to be more accurate than what the camera thinks. Unfortunately, the GPS timestamp is reported in UTC. All dates in PO are stored sans timezone, but the odds are that you're not in GMT. So we'd need to add some sort of local time zone setting and convert the date/times as appropriate. |
|
442 | Feature Request | Low | User Interface | UI Enhancements | Assigned | 2.37 |
Task Description
This will be a placeholder for the various ideas I have for reworking parts or all of PO's UI. Ideas that are fleshed out can be moved into their own tickets for actual implementation. * AJAX-ish tabs on the photo page - instead of a separate page reload for each tab, load all tab info at once and let the UI manage paging. * Client-side sorting of all tabular data - eg folder/album listings * Dynamic client-side pagination of the slide view - "dump" all slides at once, and let client-side manage their pagination? - Probably can't sort this way though * Lightbox-esque view of photos - Intended for guest access, hiding details of photos. - Slideshow capabilities - Easy navigation (eg using left/right arrows) * Replace ad-hoc toolbars with more coherent ones * Replace hackish button/checkbox theming script with something saner. * Replace wz_tooltips and js_calendar with better integrated stuff. * Modal login/password form - pops up on top of current page - Can force current page to reload afterwards - What to do about 401/403 errors? * Replace all "confirmation" pages with modal dialogs. I'm leaning towards Query and jQueryUI for actual implementations. Initial implementation will probably require current themes to be taken out back and shot. |
|
214 | Feature Request | Low | User Interface | Switch to DHTML "tabs" on main photo page. | New | 2.33 |
Task Description
To avoid having to do a page load/refresh for each of the sub-photo tabs (ie overview, technical, ratings, etc) Eventually, I'd love to see the various sub-pages (eg rating.add/del/edit) also become "tabs" of the same master page; the majority of the code (and markup) on each page is duplicated. This may require us to use AJAX-type techniques however. I'd still prefer basic photo navigation to be okay without javascript enabled. |
|
6 | Feature Request | Low | Backend / Core | Specify/store RAW image parameters | New | Devel |
Task Description
Currently the RAW settings are shared across all images. It would be nice if each image would contain with it the settings used to process the image. The problem is that the decoder often has defaults which change over time, and re-generating the same image can result in differences. |
|
162 | Feature Request | Low | Import | PTLens/clens support | New | 2.33 |
Task Description
Adding support for PTLens would be really nice -- we could automagically correct lens distortion etc as part of the image generation workflow. PTLens needs the camera and lens model and the focal length to work properly. I think it can use EXIF data directly. |
|
411 | Feature Request | Low | Backend / Core | OpenID support | New | 2.36 | |
|
297 | Feature Request | Low | Documentation | In code documentation for PHP-Documentor or Doxygen | New | 2.33 | |
|
315 | Feature Request | Low | Backend / Core | Allow filtering/finding photos matching criteria in Pro... | Unconfirmed | 2.34 | |
|
464 | Feature Request | Low | Backend / Core | Add support for "adult" filters | New | 2.37 | |
|
407 | Feature Request | Low | Backend / Core | Add a 'start/end date' to folder/albums | New | 2.36 | |
|
200 | Feature Request | Low | Import | Add a 'copyright notice' and 'Original URL' to thumbnai... | New | Devel | |
|
307 | Feature Request | Low | Backend / Core | Add a 'contact this user' form. | New | Devel | |
|
125 | Feature Request | Low | Backend / Core | XML export should include "human-readable" values. | New | Stable | |
|
443 | Bug Report | Low | Backend / Core | Wrong user name displayed | Unconfirmed | 2.37 | |
|
216 | Feature Request | Low | Backend / Core | show disk usage in folder/album stats. | New | Devel | |
|
440 | Bug Report | Medium | Backend / Core | Possible to set an album/folder's parent to itself. | New | 2.37 | |
|
446 | Bug Report | Low | Backend / Core | location search always return nothing in Advanced Searc... | Unconfirmed | 2.37 | |
|
395 | Feature Request | Low | Backend / Core | Convert more pages to a POST/REDIRECT/GET output. | New | 2.36 | |
|
213 | Feature Request | Low | Backend / Core | add mechanism for tracking models &| model releases | New | 2.33 | |
|
369 | Bug Report | Low | Backend / Core | add a 'ignore' field to profile items | New | 2.35 | |