Feature Request: Filtering/Grouping of Sessions

[GoogleCodeExporter]

For purposes of organization and efficiency it makes sense to great separate 
sessions for directories that are more or less self contained. Particular 
photoshoots/projects, different events, etc. So rather than having a session 
called "pics" I find that I have sessions called personal_xmas_2012, 
work_client1_images, etc.

This is fine for a smaller number of sessions, but I'm in the process of 
putting more or less all of my media under revision control and the session 
list quickly balloons out of control. 

It would be nice to be able to appending some kind of "tag" metadata to 
sessions to be able to quickly filter logical session groups. Like only showing 
sessions with +work, or filtering on multiple tags like +work +2012. At the 
moment I'm overloading the session name to accomplish this, but it would be 
much nicer to do it with a separate metadata attribute that could be easily 
added to the session.json files.

On a related note, it would be nice to be able to specify a session by using a 
partial session name so long as it was unambiguous. So import -v -m "minor 
edits" "photos" "very_long_session_name_blah_blah_blah" could be "very_long*" 
(assuming there was nothing else that started with very_long).

Original issue reported on code.google.com by cryptob...@gmail.com on 15 Jan 2012 at 6:32

[GoogleCodeExporter]

great separate sessions = create separate sessions

Original comment by cryptob...@gmail.com on 15 Jan 2012 at 6:34

[GoogleCodeExporter]

I understand that this might be useful for your usage, but I think it is an 
unusual way to use sessions. Also, you have a reasonable workaround in using 
keywords in the session names. Closing this until there is a popular demand for 
this feature...

Original comment by ekb...@gmail.com on 29 Feb 2012 at 12:53

• Changed state: WontFix

[GoogleCodeExporter]

Yeah, I realize being able to add tags to sessions might be overkill. I was 
tossing that out as a possible solution to the issue. The ultimate issue was 
with regard to the "usability" of the list command for people with very many 
sessions. Typing boar list and getting a gigantic tangle of haphazardly ordered 
sessions is a bit unwieldy. But as you said, there are workarounds piping the 
output into different commands.

That said, any thoughts about the second issue. I should have put it in a 
separate issue, but I was being lazy. Specifically, of being able to pass boar 
partial session names as long as they are unambiguous, so something like `boar 
list "job1"` would work instead of `boar list "job1 super long session name 
with other keywords"`

Regards :)

Original comment by cryptob...@gmail.com on 29 Feb 2012 at 5:23