Open Science Framework¶
The following introduction is based on the OSF Guides.
osfclient is a Python module and command-line program for executing commands in OSF, such as uploading and downloading files and folders.
UBC is an OSF Institution, which means researchers can affiliate their OSF account and projects with UBC and log into OSF is possible using their university credentials.
Public projects affiliated with UBC appear in the institutional portal: https://osf.openscience.ubc.ca/.
To find out how to connect your OSF account to UBC, visit the OSF FAQ page of the Open Science @ UBC website.
Storage and Backup¶
OSF uses Google Cloud for active and archival storage and Amazon Glacier as a backup location.
OSF is maintained and developed by the Center for Open Science, which has established a $250,000 preservation fund in the event that COS closes down. This fund can preserve and maintain read access to hosted data for more than 50 years.
OSF is free due to the support of COS sponsors.
The U.S. is OSF’s default storage location. A variety of storage locations are available, including Canada (Montreal). The global (default) storage location can be changed and will be applied to new projects and components. Each project and component can also have its own storage location.
There is no limit on storage per project and no cap on the amount of OSF Storage per user. Direct upload of individual files to OSF Storage has a 5GB limit.
Third-party add-ons like Dropbox can be used to integrate different services already in use and connect them to OSF to allow access to existing data/materials. There is no limit for the amount of storage used across add-ons.
If data needed for a project already exists in one of the services below, it can be connected to OSF rather than transferring it. This feature is also useful if a file exceeds the 5GB limit for upload.
This page provides a list of available storage add-ons in OSF, which includes platforms like Amazon S3, ownCloud, Dataverse, GitHub, Bitbucket and GitLab.
OSF does not store or back up content within an add-on. Ensure that each individual add-on being used complies with UBC’s Information Security Standard #03: Transmission and Sharing og UBC Electronic Information.
Within a lab¶
OSF projects and components are private by default. Members of the lab can be added as “Contributors” to projects. There are two types of contributors:
- Bibliographic (displayed in contributor list and in project citations)
Each component within a project can have its own set of contributors.
A contributor can be given three levels of permissions:
- Read + Write
- Read only
Each contributor can be granted different levels of permissions across components.
OSF has a checkout feature that prevents multiple contributors from editing the same file at once.
Researchers can request access to both private and public projects, which means they can be added as a contributor and given a level of permission.
For peer review, presentations, or data sharing, a view-only link can be created for a project. The contributor list can be anonymized for blind peer review and only selected components will be visible via the link.
A single file can be shared independently from a project using the Quick File feature, which allows files to be publicly searchable and accessible on the profile page.
DOIs can be created for projects but OSF does not currently support DOI versioning.
OSF generates citations (APA, MLA, Chicago, or custom) automatically for every project and component.
A license can be added to a project either by choosing from a list provided by OSF or uploading your own. Components will have the same license as the top-level project by default but they can also be licensed individually.
OSF has built-in version control and provides access to previous versions of files, including those stored on add-ons.
A registration is a time-stamped copy of an OSF project that cannot be edited or deleted. This feature is useful for archiving and to capture and preserve significant moments in the research process (i.e. before submission for peer review, etc.).
A registration can be withdrawn, which means the project contents will be removed but its basic metadata will be maintained. All registrations will be made public, which can be done immediately or embargoed for up to 4 years.