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
Importing CSV data for the Midweek Meeting #64
Comments
I have been working on this feature: Important The text file must be UTF8 + BOM encoded. Supported Delimiters
Column Headings
PartType
School
Sample Data 1The data would be comma (or semi-colon) delimited:
Footnotes
|
Some aspects of the field mappings concept need to be discussed.
Away TalksMSA supports an unlimited number of away talks. So it would be tricky to import using this system. A The CSV-Weekend Meeting importer could be implemented that uses multiple rows. StudentsThe CSV-Midweek Meeting importer is ideal because it uses multiple rows per meeting. So we don't have an inordinate number of columns in the file. We potentially have 9 assignments, per school, making it 27 additional columns. I just don't like it. TeachingMost congregations only have the Teaching role in the main hall and no other classes. In which case we could support it. But MSA technically supports a Teaching assignment in all classes. I am open to suggestions, if you have any. 💡🤔 |
To facilitate the import process, I added extra properties to the JSON mapping file. Example: {
"FieldMapping": [
{
"Field": "Date",
"FieldIndex": 0,
"IncludeField": true,
"Meeting": "Weekend",
"MeetingIndex": 1,
"LinksTo": "Date",
"LinksToIndex": 0
},
{
"Field": "Congregation",
"FieldIndex": 1,
"IncludeField": true,
"Meeting": "Weekend",
"MeetingIndex": 1,
"LinksTo": "Congregation",
"LinksToIndex": 7
},
{
"Field": "PublicSpeaker",
"FieldIndex": 2,
"IncludeField": true,
"Meeting": "Weekend",
"MeetingIndex": 1,
"LinksTo": "Speaker",
"LinksToIndex": 8
},
{
"Field": "OutlineNumber",
"FieldIndex": 3,
"IncludeField": true,
"Meeting": "Weekend",
"MeetingIndex": 1,
"LinksTo": "Talk Number",
"LinksToIndex": 9
},
{
"Field": "OutlineName",
"FieldIndex": 4,
"IncludeField": false
},
{
"Field": "Song",
"FieldIndex": 5,
"IncludeField": true,
"Meeting": "Weekend",
"MeetingIndex": 1,
"LinksTo": "Song",
"LinksToIndex": 6
},
{
"Field": "Confirmed",
"FieldIndex": 6,
"IncludeField": false
},
{
"Field": "Hospitality",
"FieldIndex": 7,
"IncludeField": false
},
{
"Field": "Notes",
"FieldIndex": 8,
"IncludeField": false
}
]
} The importing functionality is now operational, but I still need to incorporate validation checks. Note:
|
Good idea. Those buttons are now set to disabled when you select the CSV radio option: Then, the Check All / Uncheck All buttons get enabled after you have detected the fields: But, the Import button is only enabled when you have a valid field mapping configuration: 🤔 The Date Links to is mandatory, so I need to cater for that. Links ToI have added these items to the Weekend Links To list:
🤔 Should the Open Prayer / Close Prayer assignments be together in the list? ValidationA certain amount of validation is now being performed for each field:
🤔 It is not an exhaustive validation at the moment. For example, it will not confirm:
New betas are on their way to you for testing. |
Not sure what is going on my my commits. They keep closing the ticket! |
I had a bit of a mishap while trying to sort things out—I accidentally lost all my code changes! 😅 But, thankfully, I managed to recover the code. And I opted to switch back to the stable release of GitHub Desktop instead of using the beta version. It seems to be working better now. Validation
It became apparent that the fields in the CSV file I have been testing with (an export from another application) have the fields in a specific order: This works to our advantage because they are in the right order of priority:
This means that we can do some extra validation (as long as the user selects the relevant fields!):
|
Just corrected another issue. You could double-click the Field cell to into edit mode. I have now stopped this behaviour. New betas on their way to you. |
Moved the controls around: 😊 |
This looks good, you've created a progression from left to right. It is more intuitive for all kinds of users. |
Is your feature request related to a problem? Please describe.
Some scheduling applications have the ability to export assignment information in CSV format. Can the Import from Database History feature be extended to support importing of CSV data files?
Describe the solution you'd like
It would be great if the Meeting Editor could populate the schedule (assignees) from the selected CSV files.
Describe alternatives you've considered
At the moment, we have a need to use another scheduling application, I am manually re-inputting the same assignees into MSA. Importing would simplify the process tremendously.
The text was updated successfully, but these errors were encountered: