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

Break up NetKAN and CKAN-meta folders into subfolders #1625

Closed
politas opened this issue Mar 8, 2016 · 5 comments
Closed

Break up NetKAN and CKAN-meta folders into subfolders #1625

politas opened this issue Mar 8, 2016 · 5 comments

Comments

@politas
Copy link
Member

politas commented Mar 8, 2016

The NetKAN/NetKAN folder says this:

Sorry, we had to truncate this directory to 1,000 files. 89 entries were omitted from the list.

While CKAN is more like:

Sorry, we had to truncate this directory to 1,000 files. 278 entries were omitted from the list.

This can be a hurdle for new contributors unfamiliar with Github/Git. Can we think about breaking the list up into subfolders, say alphabetical?

@politas politas changed the title Preak up NetKAN and CKAN-meta folders into subfolders Break up NetKAN and CKAN-meta folders into subfolders Mar 8, 2016
@politas politas added Netkan Issues affecting the netkan data Discussion needed Metadata Issues specific for our metadata ★☆☆ labels Mar 8, 2016
@KSPjohnFX
Copy link

My thought is that separate alphabetical (a,b,c) folders would be easiest to code although an adaptive folder structure that would add extra subfolders, again alphabetically (aa,ab,ac) when needed as they fill would have more future proofing. Either would negate the issue of full folders although there tend to be clusters of mods starting with the same letters (k for example) so an alphabetical sorting would fill up unevenly.

@plague006
Copy link
Contributor

I think there are benefits to being able to see all files locally (not having subfolders) in order to quickly skim through them, but I also see the benefit of not having files truncated to those just using the web UI. With that in mind, how about a simple 2-folder split with A-L and M-Z?

Yes a time could come where that's not sufficient, but with that split no folder would be above 661 items and considering 1,000 is the threshold, it will not be truncated in the foreseeable future.

@Dazpoet
Copy link
Member

Dazpoet commented Mar 16, 2016

Seeing as identifiera can now start with Numbers I think the A-L folder should rather be 0-9+A-L seeing as I do not forsee it being a big amount added by doing so.

@politas
Copy link
Member Author

politas commented Mar 16, 2016

Well, it'll be none to start with.

@politas politas removed Discussion needed Metadata Issues specific for our metadata Netkan Issues affecting the netkan data ★☆☆ labels Jul 25, 2016
@politas
Copy link
Member Author

politas commented Jul 25, 2016

On further thought, I think the "find files" feature makes this sufficiently unnecessary, and the headaches it will introduce sufficient to say wont-fix.

@politas politas closed this as completed Jul 25, 2016
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

4 participants