If you added a collection column to library view, we could group resources by collection which could be a very useful way of accessing resources, particularly when tagging is so painfully slow.
+1[Y] Yes please!!!!!!!!!
+1
That is an excellent suggestion.
yes, this is a better solution than my use of mytags for organizing the library
ABSOLUTELY. I don't know how many times I've needed this function.
A resource can be in more than one collection, though. For example, I might have a collection of commentaries on John's Gospel, and another collection of commentaries in general. So if there were a collection column, are you suggesting it should list all the collections in which this resource is found? How then would you be able to group by collection in a meaningful way? It's possible that some resource (a) might be in collections A and B, another (b) might be in collections B and C, and another (c) might be in collections A and C. If you group by collection, then you can't simultaneously have all the resources that are in collection A grouped together while also having all the resources that are in collection B grouped together and all the resources that are in collection C grouped together.
I know this is a sort of contrived example, and most people will only put each book in one collection (Dictionaries, Commentaries, etc.) or at most two collections where one of them is entirely a subset of the other (Commentaries, and Commentaries on John). But theoretically someone might also have a collection for some independent feature of resources (theological stance, for example) and this might cross the boundaries of other collections rather than being entirely contained within one.
particularly when tagging is so painfully slow.
What is so slow on tagging? It works really fast. You can tag a 1000 books in a second. Well, in a few seconds [:)]
What is so slow on tagging? It works really fast. You can tag a 1000 books in a second. Well, in a few seconds
Perhaps that was a bit of an exaggeration. But because the tagging information is stored per book, if you tag 1,000 books it has to write 1,000 rows to the database (which takes several seconds) and more importantly it then has to sync 1,000 books to the server which takes... well a very long time.
Plus you can't mass remove one tag whilst leaving other tags intact.
Then every time you get more resources you have to remember to tag them... which sometimes takes weeks!
(By the way, if you want to experiment by tagging all your books with the same tag to see how long it takes. Make sure you don't need to use your computer for the next 10 minutes or so...)
A resource can be in more than one collection, though.
I imagine it would work just like sorting by subject, ie it would appear under both collections. Remember you can have multiple mytags as well
A resource can be in more than one collection, though. I imagine it would work just like sorting by subject, ie it would appear under both collections. Remember you can have multiple mytags as well
Oh, right. Good point.
Superb suggestion. I agree completely. [Y]
Agree. I just visited another thread and suggested this http://community.logos.com/forums/t/6727.aspx
Yes, I thought about that here http://community.logos.com/forums/t/6727.aspx ==>
[quote]It just needs a Collections column and suddenly your Library has shrunk to a manageable size (it would operate the way the Series column works).
It needs a few more bells and whistles to be truly effective:-
Properly implemented nested collections will allow a number of different views of your Library and they can be collapsed and expanded all the way down to the resource level.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
