CRAN v0.1.0

[villegar]

dsROCrate 0.1.0

New Features

• Added check_permissions() support for backend connections, allowing users to verify whether a connection has sufficient privileges to run safe_* auditing functions before execution (Function to check permissions for safe_* methods and guide for configuration #15).
• Permission validation now provides actionable feedback, including guidance on how to configure Opal users and roles when required permissions are missing (Function to check permissions for safe_* methods and guide for configuration #15).
• Added Opal version validation during backend checks to ensure compatibility with APIs required for auditing and permission verification workflows (Add Opal version validation helper when checking backend connections #22).

Improvements

• Refactored backend validation into an extensible S3 framework, providing a cleaner architecture for supporting additional backends in future releases (Refactor backend validation helpers into extensible S3 methods #23).
• Introduced a unified backend validation workflow that standardises connection, version and permission checks across auditing functions (Refactor backend validation helpers into extensible S3 methods #23).
• Replaced use of opalr::opal.datasources() with opalr::opal.projects(), reducing the permissions required for metadata extraction and improving compatibility with auditor accounts (Replace opalr::opal.datasources() with opalr::opal.projects() #21).
• Updated auditing workflows to support Opal's Audit System role, reducing the need for administrator-level accounts when generating RO-Crates and audit reports (Update documentation for user requirements #20).

Bug Fixes

• Fixed generation of orphaned permission entities in RO-Crates by excluding administrator and auditor permissions from dataset permission records where corresponding user entities are not included (Exclude admin/audit users' permissions #19).
• Improved consistency between safe_data() and safe_people() permission handling (Exclude admin/audit users' permissions #19).

Documentation

• Updated deployment vignette to reference the FederatedMethods-maintained DataSHIELD Docker deployment resources and repository structure (Update vignette to reference new docker-compose.yml location within FederatedMethods organisation #16).
• Updated user documentation to reflect support for Opal's Audit System role and revised permission requirements (Update documentation for user requirements #20).
• Reviewed documentation for internal helper functions and adjusted visibility of internal APIs where appropriate (Should we remove {roxygen2} documentation for internal functions #17).
• Added documentation and examples for backend permission validation workflows (Function to check permissions for safe_* methods and guide for configuration #15).

Internal Changes

• Improved separation of concerns between connection validation, backend capability checks and permission validation (Add Opal version validation helper when checking backend connections #22, Refactor backend validation helpers into extensible S3 methods #23).
• Refined internal validation infrastructure to simplify future backend integrations.
• General maintenance, testing and documentation updates.