BUG: Unnamed Collection

This has to be a BUG in the RC 2 version of Logos with regard to Unnamed Collection....

1. I open Tools/Collections.... it will come up with Unnamed Collection. 2. If you Open the list of Collections, there is now a Collection called Unnamed Collection in the list.

3. If you Click open and select another existing Collection to Open, you now have Unnamed Collection permanently in your list of Collections.

3. OR, if you click on New, it is called Unnamed Collection (2), as you now have two of them.

4. There is no way to Open Tools/Collections and NOT see "Unnamed Collection in your list!

I don't want "Unnamed Collections" in my list of Collections unless I put something in them!!! Why oh why did this have to be changed in version 4.2?

I so wish this had never been tampered with.... [:@]

Find more posts tagged with

Comments

Dave Hooton

I so wish this had never been tampered with....

You can have a Collections tab in your layout and it will be preserved without this imposition. But if I open Collections from the menu (not that I need to!) I get a blank, Unnamed Collection!!

NetworkGeek

https://community.logos.com/discussion/comment/198369#Comment_198369

But if I open Collections from the menu (not that I need to!) I get a blank, Unnamed Collection!!

I do this all time time to open other collections. I hate having this unnamed collection hanging around. It's the silliest UI innovation ever, it makes no sense. Ugh.

Jerry M

4. There is no way to Open Tools/Collections and NOT see "Unnamed Collection in your list!

Dominick, if you open collections from tools and then click open and go to the bottom of the list and right click on "unnamed collection" and delete it, then you can open your favorite collection and then go up to the collection tab and drag collections into your favorites. Now you can drag your collections from there to the shortcut bar and it will be saved under whatever collection you saved it in. Now when you open it from your shortcut bar "unnamed collection" will not appear anywhere. I didn't know if you knew this or not, but I understand your frustration.

tom

This has to be a BUG in the RC 2 version of Logos with regard to Unnamed Collection....

1. I open Tools/Collections.... it will come up with Unnamed Collection. 2. If you Open the list of Collections, there is now a Collection called Unnamed Collection in the list.

3. If you Click open and select another existing Collection to Open, you now have Unnamed Collection permanently in your list of Collections.

3. OR, if you click on New, it is called Unnamed Collection (2), as you now have two of them.

4. There is no way to Open Tools/Collections and NOT see "Unnamed Collection in your list!

I don't want "Unnamed Collections" in my list of Collections unless I put something in them!!! Why oh why did this have to be changed in version 4.2?

I so wish this had never been tampered with....

I agree,

it gets old deleting these "unnamed collections"

NetworkGeek

https://community.logos.com/discussion/comment/200592#Comment_200592

I agree,

it gets old deleting these "unnamed collections"

Not much noise on this issue, either people don't care about it or don't realize it's happening. I think it's poor programming design to insert something before a user actually desires to do anything with it, on top of that not deleting it if it's never used in that session. I have never seen that done before and I have been programming for 36 years.

NetworkGeek

https://community.logos.com/discussion/comment/200769#Comment_200769

I know what this reminds me of....when you start Word, it comes up as Document1 as a new document. This is like if Microsoft saved Document1 on your disk as soon as you started Word. Obviously they don't do that nor would anyone like it if they did.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/200771#Comment_200771

I know what this reminds me of....when you start Word, it comes up as Document1 as a new document. This is like if Microsoft saved Document1 on your disk as soon as you started Word. Obviously they don't do that nor would anyone like it if they did.

Great analogy--"Unnamed Collection" is exactly like Document1. (And "Unnamed Collection (2)" is just like "Document2".)

It's easy to see that "Unnamed Collection" isn't getting saved (and thus there's no need to "delete" it); just go to anywhere else in the app that shows collections (e.g., "Entire Library" drop-down list in Basic Search) and it's not listed (because it was never saved).

Rich DeRuiter

https://community.logos.com/discussion/comment/200769#Comment_200769

Not much noise on this issue, either people don't care about it or don't realize it's happening. I think it's poor programming design to insert something before a user actually desires to do anything with it, on top of that not deleting it if it's never used in that session. I have never seen that done before and I have been programming for 36 years.

I don't use the collections interface much, unless I'm setting one up. I search by them, but don't open them for searching. I just created a few today, and renamed them as soon as "Unnamed" opened. They renamed easily.

So, it's not a function I'm playing around with much and when I do, I'm usually creating a collection anyway.

I do try to create collections that I update dynamically, by title, type or "mytag." I particularly like the "mytag" option, since when I get a resource I can easily put it in a collection (or 2) by just tagging it.

tom

https://community.logos.com/discussion/comment/200774#Comment_200774

It's easy to see that "Unnamed Collection" isn't getting saved (and thus there's no need to "delete" it); just go to anywhere else in the app that shows collections (e.g., "Entire Library" drop-down list in Basic Search) and it's not listed (because it was never saved).

This is not 100% true. I have seen "Unnamed Collection". I then went back to my collections and it opened up to "Unnamed Collection (2)" and I then I deleted an empty "Unnamed Collection."

Because I just did this for the second time, there are times when the "Unnamed Collection" is being saved.

George Somsel

https://community.logos.com/discussion/comment/219095#Comment_219095

It's easy to see that "Unnamed Collection" isn't getting saved (and thus there's no need to "delete" it); just go to anywhere else in the app that shows collections (e.g., "Entire Library" drop-down list in Basic Search) and it's not listed (because it was never saved).

This is not 100% true. I have seen "Unnamed Collection". I then went back to my collections and it opened up to "Unnamed Collection (2)" and I then I deleted an empty "Unnamed Collection."

Because I just did this for the second time, there are times when the "Unnamed Collection" is being saved.

I think you are correct that the "Unnamed Collection" is being saved. While this may be a minor annoyance, I would rather have it do that than to open up a good collection which I then proceed to rename rather than simply open the collection I wanted or to have the entire collection get trashed. I can live with a roque "Unnamed Collection."

Melissa Snyder

https://community.logos.com/discussion/comment/219111#Comment_219111

I think you are correct that the "Unnamed Collection" is being saved. While this may be a minor annoyance, I would rather have it do that than to open up a good collection which I then proceed to rename rather than simply open the collection I wanted or to have the entire collection get trashed. I can live with a roque "Unnamed Collection."

Any collections named "Unnamed Collection" that are saved would be ones that had a change made to it, whether purposefully or accidentally, but the Collection was not renamed. However, the "Unnamed Collection" that now comes up when you open the Collections panel, if no changes are made to it, will not be saved.

MJ. Smith

https://community.logos.com/discussion/comment/219298#Comment_219298

if no changes are made to it, will not be saved.

Are you sure? It appears to me that if I modify other collections then add a new collection - forgetting that there already is an unnamed collection - the new collection comes up as "unnamed collection (2)" and the first one is saved. I've not retested it today as I'm in a rush but that's my recollection from last week.

Rosie Perera

https://community.logos.com/discussion/comment/219327#Comment_219327

if no changes are made to it, will not be saved.

Are you sure? It appears to me that if I modify other collections then add a new collection - forgetting that there already is an unnamed collection - the new collection comes up as "unnamed collection (2)" and the first one is saved. I've not retested it today as I'm in a rush but that's my recollection from last week.

Martha's recollection is right. And it is indeed a "re-collection" [:)] It results in an "Unnamed Collection (2)" even if you had not modified the default Unnamed Collection. Melissa is also partially right though, as that first Unnamed Collection is still not saved, and still comes up as the default next time.

The subtle difference of whether that collection is "saved" or not is probably lost on most users, though, since it shows up in the collection "Open" menu. I think some work needs to be done to make this collection never show up in that list unless it has been saved (Just like Document1 never shows up in the Word Switch Windows menu once you've opened another document). One could dither over whether to make "Unnamed Collection" be the default that comes up when you click "New" if it hasn't been saved yet. Word does create a Document2 even if the Document1 is no longer open. But I'd argue this isn't the greatest behavior for Logos to model itself after. There should really never be any legitimate need for an "Unnamed Collection (2)" unless the user has edited the Unnamed Collection and forgot to rename it.