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

[Feature] Added Google Docs Support #37

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Roaster05
Copy link
Contributor

@Roaster05 Roaster05 commented Mar 28, 2024

PR Overview

This issue is linked to the issue #36 and focuses on implementing the functionality to take text_input from the user through the medium of Google Docs, it uses the support of Google Docs API which leverages its functionality to fetch the content from the specified doc.

Implementation Details:

a. Flask App: A Flask application is implemented to handle POST requests and respond with the content fetched from Google Docs.

b. URL Parser: A URL parser is implemented to identify the document ID from the provided Google Docs URL. This ID is essential for accessing the document's content via the Google Docs API.

c. Google Docs API Integration: The Google Docs API is utilized to retrieve the content of the specified document using the obtained document ID.

d. Content Scraping: Once the content is obtained from the Google Docs API, it is scraped to extract the text content. This involves navigating through the document's children nodes to extract relevant text.

e. Data Parsing: The extracted text content is parsed to the required models for further processing which in returns the generated pairs of Question and Answers and are then parsed into a locally set storage.

f. Question-Answer Pair Generation: The parsed text data is used to generate question-answer pairs. This process likely involves using models or algorithms designed for this purpose.

g. Rendering: The generated question-answer pairs are rendered within a model, likely an HTML file named question_generator.html, for user interaction or display.

h. Credentials: Also you will have to place a seperate file service_account_key.json which contains our obtained credentials and the json file can be obtained from the Google developer console after enabling the Docs API.

Current State:

Screencast.from.2024-03-29.13-26-29.webm

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

Successfully merging this pull request may close these issues.

1 participant