Introducing deeply invested administration

Question

I would like to get some ideas on how to correctly represent deeply embedded resources in CRUD operations.

Let's say I have 4 levels of nested resources (resource 1, resource 2, resource 3, resource 4). I would like to introduce to the user an easily roaming, non-confusing interface, to allow them to roam the tree or neighboring resources.

---

Idea 1 (Breadcrump w / Links):

Resource 4:

Resource 1> [resource] - Resource 2> [resource] - Resource 3> [resource]

<.. content of Resource 4 view (index / new / edit / show) ..>

---

Idea 2 (Breadcrump w / Drop Downs):

Resource 4:

Resource 1> [ resource | V ] - Resource 2> [ resource | V ] - Resource 3> [ resource | B ]

<.. content of Resource 4 view (index / new / edit / show) ..>

---

Idea 3 (sidebar trees):

Resource 4:

Resource 1                   <.. content of Resource 4 view (index / new / edit / show) ..>
| __ Resource ..
| __ Resource ..
| __ Resource 2
....... | __ Resource ..
....... | __ Resource ..
....... | __ Resource 3 .

---

How would you do that? Do you have any examples?

Answer 1

( 1 2) ( 3) , . , , . , ( ). , . .

. , , . , , . . , , , - . ( "" ), , , , , , , ,

, . , , , . , , , .

. , , : , . , . , () , . , . , . , , - , .

Bottomline: , , .

1 2, Id 2. , -, , .

- "" , , , . Id . -, . , , . , , (, , , ). , , .

Answer 2

. -, . .

, , TreeView, Windows Explorer .