You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think setting up the Google API authentication is one of the hardest parts of using this repo. Chris just asked me if I knew for sure that the sheet was protected, and if it is, whether it needed to be.
The text was updated successfully, but these errors were encountered:
(Note that this does give an error when trying to open it in Excel on my computer.)
We could add this as something to do as part of #17. I'm not too concerned about the usability of sheet2linkml for now, since it's only really intended for us on the Tools team to use.
One other thing that might help with the usability in the long term is if we create a Google App ID for sheet2linkml -- if we do this right, I think users will only need to do the final step of the authentication process (i.e. clicking on the presented link and then pasting the generated authentication code back into the command line too). However, I'm not sure what this requires, and what it will cost, and if Google would need to vet sheet2linkml to make this happen. So maybe we should look into this once we've separated sheet2linkml into its own repo (#100)? Even then, I don't think it's a very high CCDH priority for now.
I think setting up the Google API authentication is one of the hardest parts of using this repo. Chris just asked me if I knew for sure that the sheet was protected, and if it is, whether it needed to be.
The text was updated successfully, but these errors were encountered: