ResourceSpace Labs is our innovation programme, giving customers early access to the latest features and improvements before they're officially released.

Customers on our Business Cloud package or above can opt in to have their UAT (User Acceptance Testing) instance track our development branch. This means you'll be able to:

Labs gives you the opportunity to experiment in a safe environment — your production system remains stable, while your UAT system stays at the cutting edge.

How to Join

If you're on Business Cloud or higher, just contact our Customer Success team to opt in. We'll switch your UAT instance to track the trunk and you'll be among the first to try out what's next for ResourceSpace.

The Latest Features from our Development Team

r27302 2025-08-22 dhuby Remove antiword support - that utility has not been updated since 2005
r27300 2025-08-22 dhuby Hide API key by default on admin user page also
r27299 2025-08-22 dhuby Hide API key in user profile area until a button is clicked
r27282 2025-08-21 dhuby Language regeneration following changes to consent/license plugins

Development q12909: Consent and License plugin improvements
  • Ability to Configure fields, per customer, on the consent plugin - and decide which fields should be visible to which user groups.

  • Ability for Consent expiry dates to be changed/ moved on.

  • Ability for admin to be informed when consent expiry is approaching (set period of time) and have a system similar to Action Dates to archive all resources associated with that consent form automatically when the expiry date is reached.

  • Ability to apply multiple consent expires where multiple people are featured in an image. The resource is archived each time a date is reached. The resource can be moved back to active as normal if consent is re-obtained but the image is un-usable as soon as one person's consent is permanently expired.

  • Ability to link resources to consent on upload

  • Ability to view all related resources in a results set

  • Ability to set permissions to allow different user groups to create consent records

  • Ability for Consent expiry dates to be shown on the linked resource

  • Ability to product consent report - showing consents and dates
r27274 2025-08-20 dhuby Language update
r27267 2025-08-19 dhuby Additional translation text
r27262 2025-08-19 dhuby Language translation tool handles arrays so will now process month names and the true/false array.
r27261 2025-08-19 cevans Consent and License plugin improvements

Development q12909: Consent and License plugin improvements
  • Ability to Configure fields, per customer, on the consent plugin - and decide which fields should be visible to which user groups.

  • Ability for Consent expiry dates to be changed/ moved on.

  • Ability for admin to be informed when consent expiry is approaching (set period of time) and have a system similar to Action Dates to archive all resources associated with that consent form automatically when the expiry date is reached.

  • Ability to apply multiple consent expires where multiple people are featured in an image. The resource is archived each time a date is reached. The resource can be moved back to active as normal if consent is re-obtained but the image is un-usable as soon as one person's consent is permanently expired.

  • Ability to link resources to consent on upload

  • Ability to view all related resources in a results set

  • Ability to set permissions to allow different user groups to create consent records

  • Ability for Consent expiry dates to be shown on the linked resource

  • Ability to product consent report - showing consents and dates
r27260 2025-08-19 dhuby Added Belarusian language.
r27258 2025-08-19 dhuby Language update
r27252 2025-08-18 cevans script for updating extracted text for supported file types
r27216 2025-08-07 dhuby Add return types to save_user() and new_user() API bindings. Fix formatting issue with PHPDoc
r27180 2025-08-04 cevans allow empty config.php file to be used with Docker mapping and allow boot.php and setup.php to recognise it
r27179 2025-08-04 dhuby Exposing new_user() and save_user() via the API
r27169 2025-08-01 acota Allow files that have mismatching MIME types detected (ext vs content) and are considered safe. Binary files will be rejected
r27163 2025-07-31 nbraddy Add support for optional $whisper_model_dir to be used by whisper plugin

Development q13444: Whisper: Automatic creation of indexable transcripts for video and audio files
Using the Whisper library locally to transcode audio and video files.

https://github.com/openai/whisper
r27156 2025-07-30 acota Added a sanitise_url() to help escape untrusted URLs
r27153 2025-07-30 tpiechowicz Require required fields to be completed before moving resource to most archive states.

Development q12902: Required fields to be completed before changing archive state
When users are entering metadata with autosave on they can change the status of the resource (to Pending Review probably), fail to complete all of the metadata fields, including some that are mandatory, navigate away from the page and the resource will move to Pending Review.

With autosave off they must click the blue 'Save' button and at this point the system will flag the missing mandatory metadata fields and the resource can't be moved to Pending Review until these are completed.

It would be nice to have a system where all mandatory fields must be completed and resources can't be moved to Pending Review until they are.

-----

When a user retrospectively edits a resource but misses out a required field, it gives the user an error message.

If the user does nothing with the error message and skips the page, the data is still applied even though there was an error message.
r27138 2025-07-28 nbraddy Alter staticsync.php to use filemtime instead of filectime
r27135 2025-07-25 dhuby Merge of blurhash into trunk

Development q13499: BlurHash for better previews before the thumbnails load
See https://blurha.sh

Uses fast-blurhash which is very minimal and 70% faster than the stock library. Serverside there is a PHP implementation.

The hash is stored on the resource table and used to render the preview where a blurhash is available, otherwise it falls back to the existing average colour preview.

A new cron task creates a blurhash for resources that don't have them. The preview creation code will also be updated so that new resources get a blurhash automatically.