Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I just mean that a collection has no subfolders or other structure. It is simply a list of items like an S3 bucket.


How do you find an item then? I've read numerous research studies that prove people still prefer navigation over search. Ofer Bergman has done a lot of work.


The thought is that collections should be homogeneous so that for most use cases,

* The number of items would be so small that search would not be necessary, e.g. a collection personal projects

* The items would fall naturally into a timeline so you can search trivially by scrolling, e.g. RAW photos grouped together by month

* The items would be easily identified by name, e.g. MP3 files grouped by album (why am I still holding onto these?)

The intention is not to upload 1000s of individual files in a jumble, but instead, a much smaller number of archives. E.g. If you are archiving the previous semester's homework assignments, instead of uploading a bunch of random documents, each item would be an archive of the assignments from a particular class. You could tag each item with 'Fall 2020' if you want to improve the organization. I'm intending to make that an easy process, where you point the program at a directory and it packages, tags and uploads each subfolder.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: