Skip to content

Structure of the data #40

@NurElHuda

Description

@NurElHuda

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    dataData related changes ( _data folder )

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions