OSF Collections

OSF Collections is a pay-for-service tool designed for funders, journals, societies, communities, organizations, and other groups in need of building and searching related OSF projects.

What is a Collection?

An OSF Collection is a pay-for-service tool designed for funders, journals, societies, communities, organizations, or other groups who desire to create a content specific public repository of projects or components, that have been curated by Collection moderators to promote discoverability and reusability specific to each Collections’ specific content/scope.

Are there requirements for a project/component to be associated with a Collection?

• Only already created projects or components can be added to a collection. 
• The main project or component must be public. However, any sub-components within the project may be private.
  • Private components will not be available in the collection until they are made public.
  • A description will be required when a request to add a project/component to a Collection is made.

General FAQs:

What license will I need?

Various Collections may have different licensing requirements, during the request to add you will have the ability to update your license to a license approved/required by the Collection, but you can update your license at any time. More information on Licensing.

What if I have private components within my project?

Anything within your project/component that is private at the time you add to the Collection will not be included within the Collection. If at a future time you decide to make these components public, they will be automatically updated within the Collection.

How will I know the status of my project or component’s addition to the Collection?

On the project/component page there will be a drop-down section that will show the Collection status, status’ include:

• Pending: after requesting to be added to a Collection, this will be the status until a collection moderator has made a decision to approve or not approve the addition to the collection.
• Included in: indicating a collection moderator has accepted the request to add the project/component. NOTE: this is the only publicly viewable status.
• Rejected from: indicating a collection moderator has not accepted the request to add the project/component. NOTE: requires a justification from collection moderator, which is only viewable by project/component admin contributors.
• Removed from: indicating either A) the collection has removed the project/component and will provide a justification OR B) an admin on the project/component has chosen to remove the project/component from the collection (no justification required).  NOTE: moderator removal from a collection will NOT result in removal from the OSF, moderator removal requires a justification from collection moderator, which is only viewable by project/component admin contributors.
• Justifications from moderators are accessed by the dropdown. NOTE: justifications are only viewable by admins on the project.

How do I remove my project/component from a Collection?

If at any point you decide you no longer wish to be associated with a specific Collection, you can “Remove” your project/component from the Collection, and the Collection Moderator(s) will be informed that your project/component has been removed. 

Can I still make changes to my project or component once it is in a Collection?

Yes, your project/component is a sandbox that is in a constant state of change with additions and updates possible by Contributors on your project/component. This ability to update your project or component will remain after association with a Collection.

Will changes to a project or component require moderation?

No, once a project/component has been associated with a Collection, any updates will not require further moderation.

Can I change the settings on my project or component to private once it has been added to a Collection?

Yes, if for some reason you wish to make your project/component private, you can still do this after association with a Collection. NOTE that making your project/component “Private” will automatically REMOVE the project/component from the Collection. In order to be associated with the Collection again, you will need to go through the Addition process again.

Back to Meetings, Institutions, and Collections Integrations Home Page

This Article Is Licensed Under CCO For Maximum Reuse.

Back to Main Support page