Tag Info

New answers tagged

1

Can I ask why you believe using tags for information storage conflicts with 'a more structured and minimalist view about information architecture'? I think there's a good discussion in that alone. Forcing a user to create tags for information storage means it will always be relevant to them and there won't be additional/excess ways of organising their data. ...


0

Always start by asking what users need to do with the data Do they need to go into a specific record to look up info or make edits or bulk edits? Put in easy search & filtering. Determine what are the general context users start with when it comes to finding data. Do they do a specific search (e.g. name, email, phone #) or by ranges? (e.g. by city, ...


0

Basic requirements I'd second everything scunliffe said. Sort and filter are critical. Pagination is once you get past 100 or 1000, depending on the data and speed of your service. You mentioned supporting search and query-building, but it deserves repeating that simple search is a given. On the point of pagination, it might help to think of it in database ...


2

Managing a list of anything... that is over ~50 items is tricky unless you have (or in this case provide) the right tools. Paginate the results - seeing more than ~100 of something on a screen is not very usable (If the user needs to see a larger set/all at once, provide an export option where they can manipulate the data externally) Sorting - provide ...


4

If the user has that large number of entries, I think is a better idea to sit the final user and get the requirements of the task that he is actually trying to do. I don't have all the context but what is he trying to achieve: If the user has to review all entries one by one (for example an accountant needs to review all the balances to see what is not ...



Top 50 recent answers are included