CommunityData:Zenodo

What is this for?

Zenodo is an open access archival repository hosted by CERN that is available to anyone in the world. We are using Zenodo to archive a series of Research Briefs created alongside our Science of Community Dialogues series. We have a CDSC community page within Zenodo that is managed by members of our team.

How should I make it so I can add things?

• (required) Create an account: If you have not done so already, you'll need a Zenodo account to create a new archival upload. You should be able to do this from the main page.
• Join the CDSC Community: Contact Aaron with the email address and/or your Zenodo user name so he can "invite" you to be a member of the group. You should receive a notification of the invitation via the Zenodo "dashboard" for your user account.
• Visit the the CDSC Zenodo "community", of which you should be a member as soon as Aaron (and you) process the invitation.

How should I add a new resource (such as a research brief)?

Please take the following steps (and note that you might adjust them if your uploading/archiving something other than a research brief):

• Start a new upload: From the CDSC Community page, there should be a green button you can click that says "New upload." Go ahead and click this. It will ask you to upload your thing and provide a bunch of metadata.
• Files: Upload your file (probably a PDF).
• Basic information:
  • Digital object identifier (DOI): Assuming the work you're uploading is not published elsewhere and you want to make it cite-able, you should reserve a DOI as part of the "new upload" workflow and add it to your materials before uploading. Please note that you can reserve the DOI before publishing and then add the DOI to the file itself to make it easier for people to cite the work correctly.
  • Resource type: For research briefs, select "Publication/Report".
  • Enter the Title and list Creators (authors). For authors, make sure to add their ORCID if you can.
  • Description: Consider adding an abstract and/or (for a research brief) the key takeaways/summary.
  • License: Research briefs should be Creative Commons Attribution 4.0.
• Recommended information:
  • Keywords and subjects: These seem to be available either via an auto-populated existing set ("EuroSciVoc") of keywords and as free-text entry. Some useful ones from prior briefs in the EuroSciVoc set include: "media and communications", "internet", "computer and information sciences", "World Wide Web", "sociology", and "computer security." YMMV. There are probably many others.
  • Publisher: Write "Community Data Science Collective Research Briefs (No. <#>)" as the publisher. Replace the "<#> with the corresponding number that should be applied to your brief.
• Funding
  • Click add and use the pop-up to select a relevant funder if possible (e.g., "National Science Foundation (US)"). If entering an NSF award, enter the award number in the search box and see if it is available to select (NSF awards do seem to be populated in this system already). If your award/grant/funder is unavailable, you can "add a custom award/grant."
• References
  • The references should be listed on the Research Brief itself, so you can bypass this step.
• Click Save draft and review everything to make sure you're happy with it. If you like, click Preview to take a look at the metadata as it would appear once published along with the system-generated citation.
• Once you're ready, click submit for review or publish (the available option(s) will depend on your user role in the CDSC Zenodo group). NOTE: once something is published you cannot edit it further! So only publish once you're satisfied with how things look and/or check one of the existing CDSC publications in Zenodo for comparison.

There are a lot of other fields to enter information. As long as you have the above fields filled in, you don't need to worry about filling out the others.

Caveat: We haven't used this (much) yet, so we're still resolving some aspects of the workflow. Check back here for more info as we iron out some of the specifics.