Modify collections

Is there any way to look at my collections without starting a new one? For example, Everytime I click on collections it opens up a blank new empty collection to start. But if all I want to do is modify a current one how can I do that without creating a new blank one that I just have to delete.

Find more posts tagged with

Comments

Bruce Dunning

When you open collections you have the option to start a new one or open an existing one. Open the one you want and then you can edit.

Mattillo

https://community.logos.com/discussion/comment/821975#Comment_821975

Thank you sir. What I meant was Everytime I open up collections it automatically starts a new blank one. Is there any way to avoid that?

Jack Caviness

https://community.logos.com/discussion/comment/821979#Comment_821979

Everytime I open up collections it automatically starts a new blank one. Is there any way to avoid that?

It is not really a new collection. It is just ready for you to create a new collection. As long as you don't change the name of click New, it will just be the one Unnamed Collection.

Donnie Hale

https://community.logos.com/discussion/comment/821979#Comment_821979

Thank you sir. What I meant was Everytime I open up collections it automatically starts a new blank one. Is there any way to avoid that?

While Jack is technically correct, I agree with you that the current behavior is unintuitive at first, annoying once you're used to it, and can lead to multiple unnamed collections, e.g. Unnamed Collection (2). My experience with these kinds of tools, applications, or feature interfaces is that they come up where they were when you last used them. I'm thinking of OneNote, Evernote, etc. That seems more intuitive to me. But perhaps Faithlife has telemetry that indicates users create new collections when they open the tool more often than they edit existing collections.

Donnie

JT (alabama24)

https://community.logos.com/discussion/comment/821991#Comment_821991

[Y]

Bruce Dunning

https://community.logos.com/discussion/comment/821991#Comment_821991

Thank you sir. What I meant was Everytime I open up collections it automatically starts a new blank one. Is there any way to avoid that?

While Jack is technically correct, I agree with you that the current behavior is unintuitive at first, annoying once you're used to it, and can lead to multiple unnamed collections, e.g. Unnamed Collection (2). My experience with these kinds of tools, applications, or feature interfaces is that they come up where they were when you last used them. I'm thinking of OneNote, Evernote, etc. That seems more intuitive to me. But perhaps Faithlife has telemetry that indicates users create new collections when they open the tool more often than they edit existing collections.

Donnie

I totally agree with you Donnie. I have mistakenly created a few "Unnamed Collections" in the past as well and your suggestion would not allow that to happen.

MJ. Smith

https://community.logos.com/discussion/comment/821991#Comment_821991

My experience with these kinds of tools, applications, or feature interfaces is that they come up where they were when you last used them. I'm thinking of OneNote, Evernote, etc. That seems more intuitive to me.

I find it equally annoying for them to come up where they were when I last used them - especially if the tool takes time to build. I would prefer that it come up blank - not ready for a new entry, not display the last entry, just a good old blank slate.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/821979#Comment_821979

Thank you sir. What I meant was Everytime I open up collections it automatically starts a new blank one. Is there any way to avoid that?

When a collection is open, can drag tab to create a shortcut. Opening shortcut causes Collection Tool to open a specific collection.

Keep Smiling [:)]

Jack Caviness

https://community.logos.com/discussion/comment/821991#Comment_821991

Thank you sir. What I meant was Everytime I open up collections it automatically starts a new blank one. Is there any way to avoid that?

While Jack is technically correct, I agree with you that the current behavior is unintuitive at first, annoying once you're used to it

I did not say that it was a good idea, because it is not. I just gave an explanation of the way things actually work. I agree that it is quite annoying.

Simon’s Brother

https://community.logos.com/discussion/comment/822005#Comment_822005

It's a very poor design choice. Would much rather see it open to a null state where I have to decide to open an existing collection or create a new one.

Doc B

https://community.logos.com/discussion/comment/821991#Comment_821991

the current behavior is unintuitive at first, annoying once you're used to it, and can lead to multiple unnamed collections, e.g. Unnamed Collection (2)

[y]