Collections in Library question

I wonder about the implementation of this feature. Why was it decided to create a way to see collections in Library in the manner we now have? Why wasn't a Collections field added to the columns we can display?

In the current implementation i really don't see the purpose. Is this just the first step in a larger development? If someone else sees it, please chime in.

If collections were a field that we could display, at least one advantage would be to select resources by tags and then check to see if the resulting collections listed for the resources were what we wanted. Another would be we could see the resources that were not assigned to collections.

Find more posts tagged with

Comments

Todd Phillips

This is the way I've been wanting it.

This way I can semi-permanently filter the library by collection. THEN I can sort the books in that collection anyway I want. If it were only a column, then that wouldn't be possible

I also agree that a collections column would be useful. But since books aren't individually tagged with the collections, I'm guessing there is a performance consideration with calculating the total list of collections for each book in the entire library.

JT (alabama24)

https://community.logos.com/discussion/comment/405458#Comment_405458

This is the way I've been wanting it.

It's a good start.

Mark Smith

https://community.logos.com/discussion/comment/405458#Comment_405458

This way I can semi-permanently filter the library by collection. THEN I can sort the books in that collection anyway I want. If it were only a column, then that wouldn't be possible

I see the point. Thanks.

Graham Criddle

https://community.logos.com/discussion/comment/405468#Comment_405468

This is a really useful improvement.

Good work.

Mark Barnes

https://community.logos.com/discussion/comment/405458#Comment_405458

This is the way I've been wanting it.

Me too. The only thing missing is that the selection doesn't stick when you close the tab.

I also agree that a collections column would be useful. But since books aren't individually tagged with the collections, I'm guessing there is a performance consideration with calculating the total list of collections for each book in the entire library.

Yes, it's hard to see how this could be programmed efficiently without redesigning how collections work.

Jack Caviness

https://community.logos.com/discussion/comment/405529#Comment_405529

Me too. The only thing missing is that the selection doesn't stick when you close the tab.

Also, the list always opens at the top, like Collections did formerly. Would recommend having it open at the selected collection as Collections does now.

Changing the content of a collection does not change the Library display. The collection must be deselected and reselected to display the change (The collections feature works the same way).

Mark Barnes

https://community.logos.com/discussion/comment/405570#Comment_405570

Also, the list always opens at the top, like Collections did formerly. Would recommend having it open at the selected collection as Collections does now.

Another problem: the "Open Resources" section has no real relevance in the library view, (although "All Open Resources" is quite handy).

Jack Caviness

https://community.logos.com/discussion/comment/405572#Comment_405572

Another problem: the "Open Resources" section has no real relevance in the library view

Agree. Looks like a simple copy of the Search and Cited by option lists.

although "All Open Resources" is quite handy

Very useful option.

Mark Smith

https://community.logos.com/discussion/comment/405529#Comment_405529

Yes, it's hard to see how this could be programmed efficiently without redesigning how collections work.

Add a metatag to each resource. Logos could figure out how to add that when a resource is added to a collection. (They have the resource-collection connection data already stored, so there ought to be a way.)

Mark Barnes

https://community.logos.com/discussion/comment/405587#Comment_405587

(They have the resource-collection connection data already stored, so there ought to be a way.)

This data isn't stored, it's calculated every time a collection is needed. So it's easy to find out what resources are in a collection, but much harder to find out which collections a resource is in.

Add a metatag to each resource. Logos could figure out how to add that when a resource is added to a collection

The problem is that resources can be added to collections in all kinds of ways: resource meta updates, library edits (tag/title changes), resources being added/hidden (i.e. not necessarily when the collections panel is open). It would be possible to store the list of resources in a collection, then when the collection is calculated, that list to be compared to the current results, and then a 'tag' added to any new resources, and removed from any resources no longer in the collection. But that would add significant overhead, and collections are calculated quite frequently.

Mark Smith

https://community.logos.com/discussion/comment/405601#Comment_405601

Agreed that dynamic collections can change. But this is a computer, and what I am suggesting isn't esoteric programming. Would it add a second to load time to calculate the current Library's collection data? Two seconds? How long to refresh when a specific collection changes? Logos has definitely programed more difficult operations.

We are missing the L3 capability to see our whole Library and what resources are assigned to what collections. That was a report in L3 but there is nothing like it in L4. There could be in L5.

Bohuslav Wojnar

I wonder about the implementation of this feature. Why was it decided to create a way to see collections in Library in the manner we now have? Why wasn't a Collections field added to the columns we can display?

In the current implementation i really don't see the purpose. Is this just the first step in a larger development? If someone else sees it, please chime in.

If collections were a field that we could display, at least one advantage would be to select resources by tags and then check to see if the resulting collections listed for the resources were what we wanted. Another would be we could see the resources that were not assigned to collections.

I see it as a very useful addition to manage library. It is not the same as having a column. You can use the bigger view option (it is broken for now, see http://community.logos.com/forums/t/56463.aspx) and still have a list of desired books in the library.

And yes, you can filter this way also by tags.

Great feature IMHO.

Ben Torell

https://community.logos.com/discussion/comment/405572#Comment_405572

Another problem: the "Open Resources" section has no real relevance in the library view, (although "All Open Resources" is quite handy).

Thanks for reporting this. The "Open Resources" section has been removed for the next release, but the "All Open Resources" option will remain.

Dave Hooton

https://community.logos.com/discussion/comment/405615#Comment_405615

We are missing the L3 capability to see our whole Library and what resources are assigned to what collections

It would be more useful then seeing a lot of community tags and unions of our tags! But you don't have to view any column unless you want to; so the overhead in providing the data is incidental to its utility.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/405529#Comment_405529

I also agree that a collections column would be useful. But since books aren't individually tagged with the collections, I'm guessing there is a performance consideration with calculating the total list of collections for each book in the entire library.

Yes, it's hard to see how this could be programmed efficiently without redesigning how collections work.

Concur about programming challenge, but would greatly appreciate a collections column in the Logos Library so could see collection(s) for every resource.

Managing content of a collections column is similar to MyTag management requested by a number of users (especially removing one tag while leaving others intact), perhaps could reuse code to implement both.

Keep Smiling [:)]

Mark Barnes

https://community.logos.com/discussion/comment/406345#Comment_406345

Managing content of a collections column is similar to MyTag management requested by a number of users (especially removing one tag while leaving others intact), perhaps could reuse code to implement both.

The fundamental difference between tags and collections is that tags are applied individually to a resource, whereas collections are generated dynamically. It's that dynamism that creates the challenge, and prevents any reuse of code.