Skip to content
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

Data upload fixes #1

Open
2 of 4 tasks
oganm opened this issue Nov 1, 2023 · 0 comments
Open
2 of 4 tasks

Data upload fixes #1

oganm opened this issue Nov 1, 2023 · 0 comments

Comments

@oganm
Copy link
Member

oganm commented Nov 1, 2023

  • Normally a data set comes with document, traditionally titled with a some variant of "README", which contains information about your data set, including variable descriptions, licence information and researcher contact information. The library's guide to depositing data (https://researchdata.library.ubc.ca/deposit/dataverse/) has a guide for "Creating a README for Your Dataset" (https://osf.io/aqxw3).

  • I also see that the Github repository mentioned in the abstract (https://github.com/PavlidisLab/regenerationCMap) also contains data/code, etc. I don't know if you're aware of this, but it's possible to set up a Github action to automatically sync your repository with Borealis. You might want to have a look at https://github.com/IQSS/dataverse-uploader

  • The R data files were "identified" by Borealis as being gzip files. I realize that this is technically correct, but if you wanted to you could edit the descipription of the files using Edit Files/Metadata to indicate what is in the individual files. This isn't really necessary if all of the material is listed in the README document.

  • While I realize you have a link to Github in the abstract, you could also place the same link into the "Related material" field of the metadata record. Note that it accepts HTML, so you could add a hyperlink if you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant