Skip to content

Restructure repository to separate scraper and post-processing code #38

Description

@ramonechen

For the sake of making the project simpler to understand for users, I've been thinking of restructuring the project folder hierarchy so that there's a clear separation between scraper and postprocessing code. Right now, it's all mashed together in one flat hierarchy and to an outside user, it might not be immediately clear which scripts are relevant to just the scraping part.

One idea of a new folder structure looks something like this:

src
|__scraper
     |__scraping logic
|__postprocessing
     |__post processing logic

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions