-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
why are csv_dd and flmd templates in xlsx format? #3
Comments
Good point, @tvelliquette, are you OK with me switching the .xlsx data dictionary files over to CSVs? |
@robcrystalornelas @regnans Switching to CSV is fine. This will be the case for any other .xlsx files that users will need to complete. I don't know if this will result in any changes to the documentation/instructions. |
@tvelliquette I've got the data dictionary uploaded as a CSV. Are you OK with me deleting the excel file from the repository? If we're OK with removing that excel file, my next to-do will be:
|
@tvelliquette I went through and made sure all links to the template within the repo now point to the CSV version of the data dictionary instead of Excel. Going to close this issue. |
Reopening this issue as the template files are now xlsx again. |
Thanks for bringing this up @regnans! In the rounds of revisions for the FLMD reporting format this fall, we decided that because xlsx are generally easier to download via the GitHub interface compared to CSV we would stick with Excel files in this repository. But I think there are some ways we can re-incorporate CSV files (see notes below). Just so we are all on the same page, I added in a few screenshots of the interfaces. Excel file with download button: CSV file without download button: We did try to stress in FLMD instructions that anyone using a template should convert from Excel to CSV. But I think we have a couple other options we can consider:
|
ah, I forgot about the download issue. That's not one of GitHub's best features! Thanks for your response, that makes sense to have excel for download. I'll close this again. |
👍 Sounds good, Kim! |
Submitter:
I suggest the following changes: it seems that csv would be fine here, and would prevent users from uploading xlsx
The text was updated successfully, but these errors were encountered: