NEW FEATURE PR- Inclusion of data extraction for both festival dataset 2014-2016 and 2017 - 2019 September #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nsisting of events from 2014-2016 and 2017-2019. Completed the README.md
RattataKing
approved these changes
Jan 7, 2025
There was a problem hiding this comment.
Thanks! File structure looks good to me, need @LindyZh to check if the final cleaned csv format matches with her expectation. NIT: maybe add some words to explain why festival data is grouped into 2014-2016 & 2017-future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related Issue
Closes Festival Section of Issue #2
Summary of Changes
Testing
Checklist