Skip to content

Commit a49e201

Browse files
committed
updating access and eligibility
1 parent d1ca7fd commit a49e201

1 file changed

Lines changed: 9 additions & 33 deletions

File tree

pages/access.md

Lines changed: 9 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,21 @@ Every access request must satisfy the five core ABLeS principles:
2121

2222
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).
2323

24+
## Training events
25+
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).
29+
30+
> **Tip:** Visit the [Event support page](https://www.biocommons.org.au/event-support) to see
31+
> the full range of events Australian BioCommons can support.
32+
2433
### Who can apply?
2534

2635
| User type | Description |
2736
| -------------------- | ----------------------------------------------------------------------------- |
2837
| Research projects | Academic, government, or industry life-science research with defined outcomes |
2938
| Development projects | Bioinformatics tool or workflow development intended for community use |
30-
| Self-paced learning | Independent exploration and learning; no training event required |
3139
| Training projects | Nationally delivered or institutional life-science training activities |
3240

3341
### What does access include? {#quotas}
@@ -47,38 +55,6 @@ For full eligibility criteria, see the [ABLeS eligibility page](https://australi
4755
4856
---
4957

50-
## Your access pathway {#pathways}
51-
52-
Choose the pathway that matches your use case.
53-
54-
### Research, development, and self-paced learning
55-
56-
Apply through [ABLeS](https://australianbiocommons.github.io/ables/eligibility). Your
57-
application should describe your purpose, expected duration, scale of compute needed, and any
58-
data considerations.
59-
60-
[AUTHOR TO SUPPLY — link to BioShell-specific access request form once available]
61-
62-
### Training events
63-
64-
If you are planning a workshop or training event using BioShell, contact the
65-
[BioCommons Training Team](https://www.biocommons.org.au/event-support) or email
66-
[comms@biocommons.org.au](mailto:comms@biocommons.org.au).
67-
68-
BioShell training events must meet Australian BioCommons Co-hosted Event standards, including:
69-
70-
- Open to all suitable Australian life science researchers
71-
- Affiliated with an Australian research organisation or university
72-
- Publicly advertised at least one month before the event
73-
- Delivered by an expert practitioner with clear learning outcomes
74-
- Content reviewed by the Australian BioCommons Training and Communications team
75-
- Adherence to the [Australian BioCommons Code of Conduct](https://zenodo.org/record/4276854)
76-
77-
> **Tip:** Visit the [Event support page](https://www.biocommons.org.au/event-support) to see
78-
> the full range of events Australian BioCommons can support.
79-
80-
---
81-
8258
## Access duration and renewal {#duration}
8359

8460
Research and development project access is granted for 3 months and is renewable. Renewal

0 commit comments

Comments
 (0)