-
Notifications
You must be signed in to change notification settings - Fork 4
Create a new spreadsheet template
marton-balazs-kovacs edited this page Sep 11, 2020
·
1 revision
The spreadsheet to be flexible, easy to understand for end-users, and easy to check upon upload.
- support several first and last authors https://github.com/marton-balazs-kovacs/tenzing/issues/34
- make the template extendable (new columns can be easily added in the future without breaking the app) https://github.com/marton-balazs-kovacs/tenzing/issues/33
- Two columns that already came up as possible addition ORCID id https://github.com/marton-balazs-kovacs/tenzing/issues/38 and funding information (see link in previous bullet point)
- input spreadsheet as URL https://github.com/marton-balazs-kovacs/tenzing/issues/30
- more than two affiliations possible https://github.com/marton-balazs-kovacs/tenzing/issues/31
- we should try to keep the users as much in our app as we can and even if they use the google sheet they should now that it belongs to our app
- in certain columns where possible information can be provided authors can write more than one information by using YAML syntax
- basically writing more information in the cell and divide them by "-" and enter
- on the backend part we should read it as text and accept all new lines, just "-" and both of them as more entries
- create a default minimal infosheet template with only the absolutely necessary columns (what should be these columns?)
- allow users to add more columns if they need it
- we should also provide a premade list of extra columns to choose from
- on the backend part, we require users to include the default columns, otherwise, the app returns an error
- we can have a list of "official" column names that are tested in addition if added but do not throw an error just a warning (e.g. duplicated values in email addresses)
- change the color of the google sheet template to match the app color scheme
- provide an option in the app where users can create their infosheet template by choosing extra columns whatsoever and download it locally
- this way the downloaded template will match our requirements and the user can decide where to share it
- add the option to create the template using Julien's app
- we need to refer to columns by name and not index
- preferably using one list of columns names all over the app to be consistent and avoid changes at multiple places (e.g. internal datafile)
- reading columns with possible multiple values in one cell as text and then transforming the content
- as currently there is no Rmd template for all the outputs that we create I would not change any output to be YAML based but change the background framework from df to list
- it would be easy to transform list to YAML or JSON later on