Software architecture, design, implementation, and process patterns for research software engineering in HASS and Indigenous research contexts.
An architectural pattern and two implementation options for delegating authentication and license-based authorization outside research applications.
See the pattern definition guide for the required pattern content and the pattern typology for classification and ID conventions.
These are suggestions for future patterns, not yet documented patterns. Each should be grounded in recurring needs and evidence from research projects.
| Candidate | Type | Why it complements the current collection |
|---|---|---|
| Research data packaging and portable metadata (for example, RO-Crate) | Implementation | Makes data and its license, provenance, and reuse conditions travel together. |
| Community-governed access policy and consent lifecycle | Process | Describes how communities set, review, and change access conditions over time. |
| Secure analysis environment for data that must not be distributed | Architectural | Covers the complementary case where licensing alone cannot control disclosure risk. |
| Research software reproducibility and provenance | Implementation | Supports traceability of software, data, and computational outputs. |
| Sustainable service handover and end-of-funding transition | Process | Addresses continuity, custody, and maintenance beyond a funded project. |
Use the pattern typology to classify new candidates and keep technology-specific guidance separate from architecture and human process.