E2606 - Finish ImportExport Module - backend implementation #316
Open
kamatmihir2002 wants to merge 87 commits intoexpertiza:mainfrom
Open
E2606 - Finish ImportExport Module - backend implementation #316kamatmihir2002 wants to merge 87 commits intoexpertiza:mainfrom
kamatmihir2002 wants to merge 87 commits intoexpertiza:mainfrom
Conversation
- app/helpers/importable_exportable_helper.rb - app/helpers/duplicated_action_helper.rb - app/services/export.rb - app/services/import.rb - app/services/field_mapping.rb - app/controllers/export_controller.rb - app/controllers/import_controller.rb Note: I've added some filler code so GitHub doesn't throw "Cannot upload empty files" error when commited.
Added new folders and files
…stly implemented external classes for creation as well.
…elating to the Questionnaire Item and Question Advice example.
… duplicate records in the try_import_records method. This method should be extracted to the service.
…r, everywhere kept refering to the question_id. This wouldn't work for importing, so I changed the schema to use item_id rather than question_id and changed all the references I found to use item_id as well.
Update question id to item
- Added script to export AssignmentTeam records filtered by assignment_id - Included team members, emails, and member counts in detailed export - Improved export process explanation and cleaned up runner command usage - Ensured compatibility even without parent association by resolving assignment names manually
… the export controller to be able to send stuff to the frontend for export and index
# Conflicts: # app/helpers/importable_exportable_helper.rb
Import and Export Functionality
fixing leftover vscode diff printed into schema
Generated by 🚫 Danger |
…cheme for csv table. Passed and made use of assignment_id to help scope the specific assignment an import/export operation is occuring on. Specs were also changed to match this new format.
…wing-up ported over importable/exportable mixin into project_topic
…ating-correctly Kdnadkar/fixing teams not populating correctly
kamatmihir2002
changed the title
Integrate graph export into export with switch
reset database yml username passwd
updating schema to newest per migrations
Author
|
PR summary: Single model export was changed to graph export for models dependent on exported models. (Questionnaires + questionadvice + item) |
Add mandatory fields of external class to import-export mandatory fields
Mskamat/final changes
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Problem statement overview:
In the current project, the import feature should be redesigned to support multiple entity types in a clean and scalable way. For each entity, we should clearly define which fields are mandatory, which are optional, and which are system-managed. Only the necessary and user-editable fields should be displayed in the UI. Duplicate handling rules should be defined separately for each entity type, with a short and clear explanation for each rule. This will make the system easier to use, reduce confusion, improve data quality, and allow future expansion without major rework.
You should write code to import users, teams, topics, and questionnaires with their associated “advice.”
You should write code to export assignment grades, author-feedback grades, teammate-review grades, users, teams, topics, and questionnaires with their associated “advice.”