I chose Collections, Sets as second pick
Queries and Databases are too technical.
Bases, lists catalog, tables, refers to something else in the app in my mind.
Yes, I’m aware that it has been discussed in the past multiple times and in various places—even quite recently in the community chat. I simply wanted to get a more updated canvas of people’s opinion based on how they see Anytype today. In fact, the conversation you linked to seems to point to many users liking the term lists, and yet today, we see nobody liking it. ‘Listbox’ did not seem to gain natural popularity, however we will still consider it internally based on how the feedback goes in this thread. 
Initially, I wanted to choose Database, but preferred Collection as it seems native and unique for Anytype being an early adopter. If it functions as intended, the name will naturally become adaptable to new users.
Yes, that’s strange.
I beg you to add the term “Listbox” into your start post, so that everyone sees it and can take it into account for his vote.
More users will join in here and the discussion will grow, so everyone should see the options in the start post.
– Not everyone will read the whole thread; I expect that it becomes a looong thread …
Ok, it’s added.
I would like to participate, but as I said, I don’t have enough information.
Do you want to introduce linkable databases like in Notion? If so, then call them Databases.
Oh gosh, I really shouldn’t have added Listbox—that caused the entire poll to be reset. I apologise, everybody. From memory, Collections was the leader with 50%+, Databases was second with around ~25%, and some votes on Sets and Queries. In total that was at an accumulative 21 votes—I’ll add them internally later.
I’m very sorry, everybody for the faffing around.
I am speaking only for myself, but it seems clear to me that this is the merger that was already announced between the current Collections and Queries. The question is therefore what term would best unify them.
Btw.: all listed items in the startpost are in plural, except my suggestion.
But if in plural, it would become two characters more.
It would be better if all items are in singular to make a fair comparison.
This decision won’t be a popularity contest from the poll; the discussion here and our internal conversation will have a strong weight as well. I’d also rather not reset the poll again and I’m sure people will not find that inconsistency to be the difference maker.
If I did make an update to the poll, it’d be ‘Listboxes’ in plural—as that’s more commonly how the feature would be referred. And in that case, it makes it less appealing (personal opinion) from a pronunciation standpoint—especially people coming from different languages. ‘Li-st-bo-xes’ is even a little awkward for me as a native speaker.
I am confused that the community is being consulted on matters that should be based on decisions made by project management. I am concerned because such questions reveal uncertainty, which undermines the confidence of both new and existing users in the platform as a whole.
We had Sets turning into Queries, now we are obviously going to have Collections + Queries turning into Lists or something else. It is presumably intended to improve the user experience, but it certainly causes new confusion.
I could not disagree more. I believe proactively soliciting input and feedback from the community in order to power internal decision making is the best way to solve real problems. Consulting the community does not mean executing whatever is being requested by users, there are many steps that exist between asking for feedback and implementation. It’s simply building empathy and understanding between the real people using our product and our decision making process.
I have the opposite perception of somebody who doesn’t ask for feedback, it shows to me that they unlikely deeply understand their users. I see a team that asks for a lot of community feedback as a source of strength and confidence. But I don’t want to derail this conversation, let’s focus on the topic at hand.
Stop me if I start discussing about he emperor’s beard,
but what I think:
- The combined thing would in practice be addressed much more often in singular then in plural.
Users come normally with questions like: “I have a problem: I have a Listbox that shows …” - It’s funny that you, as a native speaker, find it “a little awkward” in plural. Because, although my English is relative weak, it flows absolutely smoothly from my tongue.
Perhaps it is because, as a German speaker, I am used to longer and more syllabic words that are also “harder” to pronounce?
– If that is the reason, then it will apply even more so to Russians and Ukrainians, etc. They are used to even longer and “harder” words.
With that in mind, I don’t believe that people coming from other languages would have problems with the pronunciation.
Sorry @VisualNotes , I’ve accidentally flagged your post. And I can’t take it back. 
What I wanted, was to give your post a dislike reaction (OK, also not so nice from me, I know).
I’m with kaye here: I find it very important that they ask us!
No need to dislike posts, lol. Everybody is welcome to express their thoughts. People operate differently, as long as we can tolerate those differences, we’ll be all good.
RE: singular vs. plural, I think both are important. And I get your vantage point, however I know when I create onboarding materials/tutorials, I will definitely be vocalising the plural version a lot. So maybe it’s my personal bias.
RE: pronunciation: I hear you. Maybe so for European/East Slavic languages, you’d be a better judge than me. But it may not be the case for many others around the world. To be fair, I even find it annoying to say words like ‘specificity’. Hate it. Lol. 
@kaye @Code-Jack
Do you seriously believe that I am against user participation? My criticism is directed at asking users about something for which they do not have enough information.
Why don’t you have enough information?
The start post was clear, wasn’t it? (I know, you’ve seemingly overseen something in it, but now it should be clear)
And as a long term user you should know that they have the combination of Collection and Query in the pipe. The topic was already discussed over and over in the past.
I really can’t understand you here.
I barely never dislike posts and you know that I appreciate you and your work here a lot! But in this case I couldn’t believe my eyes when I saw your post! It deserved a dislike from me very much, because they did here finally what I wish much more often! They asked us instead of simply confronting us with finished “dump decisions”.
Wow, so many reply,I feel like I’m way behind, but no, this is a recent topic!
I don’t have time to read everything and I don’t know when I’ll be able to (especially if it keeps filling up at this rate!).
So, sorry if this has already been said or answered!
Same here (and, in principle, the answer is below ^^).
I suppose it’s the merge between a collection (a set of objects in one place) and a “set” (a list of objects retrieved from across the entire space according to certain criteria… a search, in other words). If this is not the case, my answer will be wrong, and I will correct it later!
I strongly agree with @Regis here : Help with the naming of Anytype's 'List' - #4 by Regis
Except :
- Table is unclear and does not sufficiently differentiate itself from tables (named simple table to limit confusion).
- Database is not accurate, since it would be a view. And well, don’t forget that database is a technical term, and we mustn’t forget that we don’t represent the majority of the population (we = I think that the profile of the people here generally has a higher level of technical/IT knowledge than the population as a whole).
My vote for Collection
@kaye Sorry to ask, because obviously I’m the only one who doesn’t know about the upcoming changes:
So collections, queries, object types and all other “lists” will be merged into one single “list” object that will combine all functions, and therefore a suitable term is being sought? A term for an universal list, so to say?