Is there a way to view each group of cards as a list? Just like what Airtable or Retable has for example?
Show HN: Sortabase, a collaborative, visual database builder for communities
11–20 of 38 posts
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#12Is there a way to view each group of cards as a list? Just like what Airtable or Retable has for example?
Not at the moment, but I'm very open to adding new views to the UI!
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#13wow this looks amazing. Do you mind shedding some light on how you built this? especially how you organize taxonomy and product metadata for each category I am working on an e-commerce platform that would benefits a lot from your experience here
The taxonomy and metadata, as you put it, is defined by the moderators/community of each database. We just give them drag-and-drop tools to do so :)
ah i meant to ask how it was designed in the backend
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#14Looks super cool. I am working on something similar.
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#15edit: Dumb question. deleted
Do you mind elaborating? I don't get how they're comparable. Vetted.ai uses AI to rank products based on user reviews and check prices across retailers. OP's project is a community-based, collaborative database (almost a fusion of Reddit and Airtable) where anyone can contribute to a database, which also isn't limited to products.
[deleted]
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#16On HN months ago, I made a list [1] on publishing small databases, and I remember that I could not find a good service under "List sharing" (maybe one). Yours fills that slot perfectly.
I have some suggestions: For initiating the DB, offering import (csv/sheets...) would help creators jump in. Then, for collaboration, you could offer the option to add without any account at all (just send the "under review" form to the moderators), or maybe also add more signup alternatives.
As for monetization, I suggest in the future you limit only "private" DBs (= me and other moderators) , so people can still create unlimited public ones (good for spreading the word).
Good luck!
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#17Finally, a good source of penguin repellent. Now I can get rid of the penguins in my basement and get my herring back!
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#18On HN months ago, I made a list [1] on publishing small databases, and I remember that I could not find a good service under "List sharing" (maybe one). Yours fills that slot perfectly. I have some suggestions: For initiating the DB, offering import (csv/sheets...) would help creators jump in. Then, for collaboration, you could offer the option to add without any account at all (just send the "under review" form to t…
Right, maybe Airtable is to Slack as Sortabase is to Discord
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#19On HN months ago, I made a list [1] on publishing small databases, and I remember that I could not find a good service under "List sharing" (maybe one). Yours fills that slot perfectly. I have some suggestions: For initiating the DB, offering import (csv/sheets...) would help creators jump in. Then, for collaboration, you could offer the option to add without any account at all (just send the "under review" form to t…
I remember that post! I had commented on it, back when this project was still very early and using a different name.
I agree with all your suggestions, and we've considered most of them. Importing CSVs presents some challenges, particularly with trying to infer the type and valid values of each column.
Re: Show HN: Sortabase, a collaborative, visual database builder for communities
#20Earlier quoted context omitted.
The taxonomy and metadata, as you put it, is defined by the moderators/community of each database. We just give them drag-and-drop tools to do so :)
ah i meant to ask how it was designed in the backend
I won't get too deep into our architecture, but needless to say letting users dynamically edit/add/remove fields in their databases is not easy. We use Postgres + Prisma as our ORM, and I'm fairly happy with its DX re: handling this level of complexity