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

Structure of the data #40

Open
NurElHuda opened this issue Jan 9, 2022 Discussed in #39 · 0 comments
Open

Structure of the data #40

NurElHuda opened this issue Jan 9, 2022 Discussed in #39 · 0 comments
Labels
data Data related changes ( _data folder )

Comments

@NurElHuda
Copy link
Contributor

Discussed in #39

Originally posted by NurElHuda January 9, 2022
@ZibanPirate @Fcmam5

I was wondering why the structure of the data is set as a tree of directories with info.json leaf instead of one main JSON file that contains all data.

  1. The overhead of traversing a JSON object compared to opening nested directories files to extract data is negligible.
  2. The name of the directories of the department does not make sense, the acronyms for the faculties are set by the universities and somewhat distinguishable, but once you dive into the departments you get lost.
  3. What is more important, is search. I can't think of an efficient way to search for, let's say, all the departments of geology amidst all the data.
  4. The moment the data is stored into one main JSON file will make automating, scraping, and extracting the data from the internet much faster.

So.. what do you guys say? I am happy to convert the available data into a JSON file, than continue with the rest.

Or is there other reasons for why the data is stored like this that I am missing?

@NurElHuda NurElHuda added the data Data related changes ( _data folder ) label Jan 9, 2022
@ZibanPirate ZibanPirate moved this to Backlog in DzCode i/o Feb 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Data related changes ( _data folder )
Projects
Status: Backlog
Development

No branches or pull requests

1 participant