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

How to handle presentation files from Annual Meetings #85

Open
gkampmeier opened this issue Jan 29, 2017 · 5 comments
Open

How to handle presentation files from Annual Meetings #85

gkampmeier opened this issue Jan 29, 2017 · 5 comments

Comments

@gkampmeier
Copy link
Collaborator

At the Jan. 2017 TDWG Exec it was agreed that we need a more permanently accessible and secure (cannot be tampered with) repository for presentations (both uploaded files and a backup for iDigBio recordings) from annual meetings, ideally one that might be indexed to make contents discoverable. Ultimately this should probably also be linked to the abstracts, which are currently hosted on OCS at the Missouri Botanical Garden (which should also be backed up). I was asked to contact the Infrastructure Committee for advice on a solution that could take us into the future.

Currently the 2016 meeting files are on Google Drive (not complete, but I have a list of missing presentations, and we can solicit upload of posters). Cyndy has a USB drive with presentations from an earlier meeting (2015?). Earlier meeting files have been uploaded to the main TDWG site under past meetings.

@peterdesmet
Copy link
Member

One option that comes to mind is to upload them to Zenodo: there they are perminanently, with authors, abstracts, a license and a DOI. Plus the can all be grouped under a TDWG community. We already have Darwin Core archived there.

@stanblum
Copy link
Member

Stated more generally, TDWG has a need for:

  • a moderate amount of storage (largest category would be presentations and the videos of presentations [we'll ask what volumes are]),
  • that can be secured (backed up, protected from malicious tampering, maybe human error),
  • configurable read/write security
  • can be web accessible or readable to only a logged-in user with permissions (think document archive for relatively private info, like receipts),
  • cheap, expandable,
  • relatively low read/write volumes.
  • can support a strategy for stable URLs (redirects)

@gkampmeier
Copy link
Collaborator Author

@peterdesmet Would you please provide a link? Appears this name references a game and a whole bunch of other things.

@peterdesmet
Copy link
Member

@gkampmeier yes: https://zenodo.org

Darwin Core example: http://doi.org/10.5281/zenodo.12693

@dkoureas
Copy link
Member

dkoureas commented Jan 31, 2017 via email

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

4 participants