Jim, children are great collectors. I just think it is wise to try interfaces with varying numbers of items before concluding that one or another mode is "too complicated". If you'd like to try an interface that has tunable complexity, you might like to get a copy of the readerware trial. I can supply a database with around a thousand books as a sample (my daughter's old elementary school was incredibly generous with a book drive!).<br> <br><div class="gmail_quote">On Tue, May 5, 2009 at 2:12 PM, James Simmons <span dir="ltr"><<a href="mailto:jim.simmons@walgreens.com" target="_blank">jim.simmons@walgreens.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Aleksey,<br> <br> It isn't clear to me what a "cloud of tags" is. Is there a familiar application that does something like this?<br> <br> I understand that users can tag things to suit themselves, but still I'd want to impose some kind of structure on the views. When I started visiting libraries they had card catalogs for Author, Title, and Subject. It was a good system, and every library used it. You could create a lot of other indexes but they wouldn't get much use. In the Calibre screenshot we had File Size, Publisher, Date, Series, and I could easily do without any of them.<br> <br> Considering that most users of Sugar are going to be children enforcing a minimum structure couldn't hurt.<div><br> <br> James Simmons<br> <br> Aleksey Lim wrote:<br> </div><div><div></div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Well, in my mind the best solution is let user choose the right way :)<br> <br> So Library will have several tags views<br> * cloud of tags<br> * tree of tags<br> * plane list of objects i.e. w/o any tags<br> <br> <br> </blockquote> <br> <br> </div></div></blockquote></div><br>