Skip to content

Commit a8b2b76

Browse files
MitchobMitchob
committed
update access page
1 parent 9ffeb55 commit a8b2b76

1 file changed

Lines changed: 36 additions & 29 deletions

File tree

‎pages/access.md‎

Lines changed: 36 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -6,61 +6,68 @@ description:
66
environment for the first time.
77
---
88

9-
## Eligibility and acceptable use {#eligibility}
9+
## Eligibility {#eligibility}
1010

11-
BioShell is a national resource funded through NCRIS. Access is governed by the
11+
BioShell is a national resource funded through NCRIS. Access to BioShell for research and development is governed by the
1212
[**ABLeS programme**](https://australianbiocommons.github.io/ables/index) (Australian BioCommons Leadership Share).
1313

14-
Every access request must satisfy the five core ABLeS principles:
14+
ABLeS is available to research groups and bioinformatics communities across **Australia**. Read the criteria below to determine whether your project aligns with the ABLeS core principles and resource criteria. To qualify for access, your project must address the following:
1515

16-
1. Your project must be life-science related and produce data, research, training, or software outcomes.
17-
2. Your team must have sufficient expertise to responsibly use bioinformatics infrastructure.
18-
3. Your resource usage must be planned and proportional — national infrastructure is finite.
19-
4. Your project should support collaboration and sharing of outputs where appropriate.
20-
5. You must comply with all relevant facility policies.
16+
**1. Domain and impact**
2117

22-
For full eligibility criteria, see the [**ABLeS eligibility page**](https://australianbiocommons.github.io/ables/eligibility). By submitting an access request you agree to the [**BioShell acceptable use policy and service terms**](aup).
18+
- Your work must have a molecular life sciences focus.
19+
- Where appropriate, you are willing to openly share your results and outputs, including data, software, and methods.
2320

24-
## Training events
21+
**2. Technical readiness and responsible resource use**
2522

26-
If you are planning a workshop or training event using BioShell, contact the
27-
[**BioCommons Training Team**](https://www.biocommons.org.au/event-support) or email
28-
[**comms@biocommons.org.au**](mailto:comms@biocommons.org.au).
23+
- Your team should have, or be actively building, the "hands-on" bioinformatics skills needed to make use of the environment.
24+
- Your resource usage must be planned and proportional as national infrastructure is finite.
2925

30-
{% include callout.html type="tip" content="Visit the [**Event support page**](https://www.biocommons.org.au/event-support) to see the full range of events Australian BioCommons can support." %}
26+
**3. Governance and leadership**
27+
28+
- You, or someone in your group, is able and willing to act as the project lead and be responsible for all resource usage and adherence to facility policies.
29+
30+
For full eligibility criteria, see the [**ABLeS eligibility page**](https://australianbiocommons.github.io/ables/eligibility). By submitting an access request you agree to the [**BioShell acceptable use policy and service terms**](aup).
3131

32+
{% include callout.html type="tip" content="Check out some [**example ABLeS projects**](https://australianbiocommons.github.io/ables/participants) to see initiatives that align with ABLeS principles and eligibility criteria." %}
3233

33-
### Who can apply?
34+
## What's support?
3435

3536
| User type | Description |
3637
| -------------------- | ----------------------------------------------------------------------------- |
3738
| Research projects | Academic, government, or industry life-science research with defined outcomes |
3839
| Development projects | Bioinformatics tool or workflow development intended for community use |
39-
| Training projects | Nationally delivered or institutional life-science training activities |
40-
4140

4241
### What does access include? {#quotas}
4342

44-
| | Training | Research | Development |
43+
| Research | Development |
4544
|---|---|---|---|
46-
| Data analysis and visualisation | Yes | Yes | Yes |
47-
| Interactive interfaces (JupyterLab, RStudio) | Yes | Yes | Yes |
48-
| SSH CLI access | Yes | Yes | Yes |
49-
| Storage quota | 0 GB | 100 GB | 100 GB |
50-
| Allocation period | Training period | 3 months | 3 months |
51-
| Renewal | Not applicable — event bound | Yes, subject to review | Yes, subject to review |
45+
| Data analysis and visualisation | Yes | Yes |
46+
| Interactive interfaces (JupyterLab, RStudio) | Yes | Yes |
47+
| SSH CLI access | Yes | Yes |
48+
| Storage quota | 100 GB | 100 GB |
49+
| Allocation period | 3 months | 3 months |
50+
| Renewal | Yes, subject to review | Yes, subject to review |
5251

5352

54-
{% include callout.html type="note" content="Storage quotas are enforced at the infrastructure level — it is not possible to exceed your allocation. If you need more storage, contact the BioShell helpdesk. Requests are subject to availability and review and cannot be guaranteed." %}
53+
{% include callout.html type="note" content="Storage quotas are enforced at the infrastructure level, it is not possible to exceed your allocation. If you need more storage, contact the [**BioShell support**](https://docs.google.com/forms/d/e/1FAIpQLSc6Tr2FAponrwYuMXfqspuzcXnssbM5gQ9ChLUqzh5yUxWJuQ/viewform). Requests are subject to availability and review and cannot be guaranteed." %}
5554

5655

57-
## Access duration and renewal {#duration}
56+
### Access duration and renewal {#duration}
5857

59-
Research and development project access is granted for 3 months and is renewable. Renewal
58+
For research and development projects access is granted for 3 months and is renewable. Renewal
6059
requires demonstrated usage and continued progress against the aims stated in your original
61-
application.
60+
application.
61+
62+
Check out the [**project renewal form**](https://docs.google.com/forms/d/e/1FAIpQLSdhQzizqnQ7f5Os7TCDpXviiIVs1nbmtWweDzGH4r0poZlxxw/viewform?usp=header) for more information or to make a request.
63+
64+
## Training events
65+
66+
If you are planning a workshop or training event and wish to use BioShell, contact the
67+
[**BioCommons Training Team**](https://www.biocommons.org.au/event-support) or email
68+
[**training@biocommons.org.au**](mailto:training@biocommons.org.au).
6269

63-
{% include callout.html type="note" content="Training access duration is determined on a case-by-case basis and is coordinated by the BioCommons Training Team. Contact [**comms@biocommons.org.au**](mailto:comms@biocommons.org.au) for details." %}
70+
{% include callout.html type="note" content="BioShell is the goto environment for running command-line training for details about workshops that have been run on BioShell see the **BioShell community and outcomes page**." %}
6471

6572

6673
## Connecting to BioShell {#connecting}

0 commit comments

Comments
 (0)