Generating hierarchic URI's based on taxonomy I was wondering whether it is possible to have a taxonomy whose URL's are based on taxonomy.
Example: I have a taxonomy list called 'Gallery type' which exists of the following items in which 'Pictures' and 'Movies' are higher in the hierarchy than the subitems:

pictures


pictures-2009
pictures-2010
pictures-2011
pictures-2012


movies


movies-2009
movies-2010
movies-2011
movies-2012


I also have a (gallery) content type in which it is obliged to select an item from the taxonomy list (actually a submitter should select two items: one main item and one subitem (e.g. 'pictures' AND 'pictures-2012'). Then I have made a view for every item in the taxonomy list so that every taxonomy term is a page that contains links to the pages that are created with the term as obliged option (I know that this is hard to follow, but please bear with me)

Example: I create a new gallery named 'Animals' and select the options 'pictures' and 'pictures-2012'. This gallery 'Animals' will be visible on the corresponding views, i.e. /pictures AND /pictures-2012. The page its URI however will be /content/animals. My question is then if it is possible to make the URI follow the hierarchy posed in the taxonomy. In this case it would be: /pictures/pictures-2012/animals

If anything is not clear, please do tell me! English is not my mother tongue, so forgive me if it contains a lot of syntactic and/or grammatical errors!
From the comments, this is one way how I would do this:


create a taxonomy vocabulary called gallery type.
create a taxonomy vocabulary called year.
populate them with the appropriate terms.


Then I'd create a view:


filter it on gallery type (or whatever content types are tagged by the above vocabs)
also filter it on all nodes that are published


In arguments (d6) or contextual filters (d7) I'd put in two arguments.  They would be taxonomy terms and you can select them from the dropdown list from taxonomy:


For the first, select taxonomy term and then in validation, select taxonomy and term again and restrict it to the gallery type vocabulary. 
For the second select taxonomy term and then in validation, select taxonomy and term again restrict it to the year vocabulary.


Then, in the Fields, select whatever fields you want displayed.  For ease here, just select node title, but once in production I'd imagine they'd be title, a picture or image or two, a description, etc.

Now, create a page display in the view, and in the path enter

myfirstview/%/%

Change myfirstview to whatever makes sense on your website's hierachy.  What the two %'s do is substitute in the taxonomy terms above.

Save everything.

Now you have created a View that does all that hierarchy for you.  So, if someone goes to...

www.yourhost.com/myfirstview/movies/2009

...Views will create the page for you and display the title of whatever content has been tagged with both movies and 2009 (views takes the hardcoded myfirstview and substitutes in the movies and 2009 and then matches them against what content is tagged with those terms) and if they went to...

www.yourhost.com/myfirstview/pictures/2012

...Views would create a page of all pictures from 2012 doing the same logic.

What is nice is that you can then create a views that filter on only one of the vocabularies, eg,

www.yourhost.com/mysecondview/pictures

that would list all pictures

or

www.yourshost.com/mythirdview/2012

that would list all content from 2012

As you get more comfortable with Views you can then add all kinds of different sortings, eg, sort by posting or last edit date, sort alphabetically by title, etc, but this should get you on your way.  Just play around with the settings and hit Preview a lot.  You'd be amazed how simple it is once you get past the up front daunting nature of all the various options you have.