Date: Tue, 19 Mar 2024 00:38:30 -0400 (EDT) Message-ID: <1237292196.143.1710823110950@si-atlasprod02.si.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_142_533760764.1710823110947" ------=_Part_142_533760764.1710823110947 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Definition
"Projects" are collaborative spaces used for on= going work.
:warning: Projects are the best solution when:
You can give people outside the Institution access to review and c= ontribute data by inviting them to your project - all they will need is a (= standard, free) figshare account.
There are two types of projects, differentiated by how storage is alloca= ted - "individual (storage)" and "group (storage)" projects.
If most of the people in your project are permanent Smithsonian staff, o= r the collaboration is is a "one off" you probably want to create an "Indiv= idual" project.
If the project is large, long-term, and/or involves many collaborators f= rom outside the Institution, but we are responsible for the long-term m= anagement of the data you should create a "Group" project.
Individua= l Projects |
Group Pro= jects |
Everyone us= es their own quota and account storage. |
Storage is = allocated from the project owner's group's (unit's) quota, i.e., whatever g= roup/subgroup the project owner belongs to determines the total storage quo= ta allocation. This group allocation must be shared amon= g all group projects that fall under that unit/group*. |
People have= full control of their items, even if they leave the project, i.e., they ca= n remove their item from the project space. |
All work re= mains within the project (institutional storage) space if people leave. Project owners can transfer control of any item on the pro= ject to themselves by removing the original uploader from the project membe= r's list. |
Items are c= reated using the metadata schema of the submitter. |
Contributor= s must adopt the metadata schema of the project owner, including custom fie= lds. |
Items also = appear in the subgroup of the uploader. |
Items appea= r only under the subgroup that the project owner is a member of, regardless= of submitter's affiliation. |
Items publi= shed by users from outside the organization don=E2=80=99t have to go throug= h review (if review is turned on for the group).* |
Items publi= shed by users from outside the organization have to go through review (if r= eview is turned on for the group).** |
*note: if a project is created, a certain amount of storage - usually 10= GB - is set aside from the overall unit allocation even if the pr= oject has no or even one or two small files in it
**currently review is NOT turned on for any SI group
Projects can be a mix of both published (public) and unpublished (= private) datasets. Anyone that is a member of a project - both viewers and = collaborators - can view and download private datasets.
Private Projects
<= /span>If a project is not published, it will only be visible to the proj= ect members on their "projects" tab. It will not have a landing page.
:warning: this assumes that you are the owner of or a collaborator= on the project
New dataset:
Select Add a new item, which takes you to th=
e metadata form. Once you=E2=80=99ve saved the item, it will appear in the =
home page of the project. As a collaborator, you can comment on individual =
items within the project or on the project as a whole.
Existing dataset:
You can also move your existing data to a project by cli=
cking the checkbox to the left of the item you want to move in =
My data, clicking on Actions, selecting Move to/from project, =
;and selecting the project you want to move the data =
to/from.
:warning:To make the project public, you must first make = at least one item public within the project.