Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving finding items in large collections #1876

Closed
dur41d opened this issue Nov 13, 2018 · 4 comments
Closed

Improving finding items in large collections #1876

dur41d opened this issue Nov 13, 2018 · 4 comments

Comments

@dur41d
Copy link

dur41d commented Nov 13, 2018

Is your feature request related to a problem? Please describe.

I have a blog like site that has thousands of articles. The articles are organized by categories or sections. The current admin UI only shows a flat list of the article titles. It's not possible to see the sections of each article without opening the article. Also, it's not possible to see the articles of a particular section.

Describe the solution you'd like

I would like the ability to filter and group the collection items by their sections so that I can manage large collections more easily.

@erquhart
Copy link
Contributor

You can use filter for that.

@dur41d
Copy link
Author

dur41d commented Nov 21, 2018

Thanks @erquhart. that would work. The only problem is that you have to re-define with all the fields for each category. But it's not that bad.

In any case, I found that the admin interface is very lacking. For example the articles are sorted by create date in ascending order and it cannot be changed. The admin interface seems to be designed for simple sites with few items and not large collections and relationships.

@erquhart
Copy link
Contributor

Yeah, it's not as simple as it seems - sorting the contents of a directory which may or may not be paginated requires a sorting API in the host (GitHub, GitLab, etc) or else downloading of the entire directory of contents up front to sort by. Here's an issue with our latest thoughts: #54 (comment)

@dur41d
Copy link
Author

dur41d commented Nov 22, 2018

Not simple indeed. One solution I can think of is to build an index that is only modified with the git diff for each commit. i.e. it's built incrementally to avoid downloading the whole content.

However, the main issue here is solved so I'll close it. Thanks.

@dur41d dur41d closed this as completed Nov 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants