- Status Closed
- Percent Complete
- Task Type Feature Request
- Category Backend / Core
-
Assigned To
pizza - Operating System All
- Severity Low
- Priority Very Low
- Reported Version Devel
- Due in Version 2.36
-
Due Date
Undecided
- Votes
- Private
FS#76 - create an album from search results
When you go through a search, allow the user to create a new album with these results!
Closed by pizza
2008-01-28 17:21
Reason for closing: Implemented
Additional comments about closing: Okay, the ability to create an album from the spool set is committed and will be in 2.35.
2008-01-28 17:21
Reason for closing: Implemented
Additional comments about closing: Okay, the ability to create an album from the spool set is committed and will be in 2.35.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Is this strictly necessary? I mean, rightnow you can do this by adding all the images you want to the spool, creating a new album, and then moving the images from the spool to the album.
So perhaps the right thing to do is to add na option to the album create page that uses the spool for the image set?
album_content.identifier (and its sequence) needs to go away. There's absolutely no point to it, as we never look stuff up this way. The true primary key is the (album, photo, version) tuple.
This is post-2.35 material -- While we technically can mangle the db at this point, I'd prefer not to.
the album add page should only prompt the user if there are images in the spool.
I have all of this implemented; I'll commit it as soon as 2.35 is forked off to -stable.