Your first look at Item Type Based Metadata, Geospatial expansion, and more
Thursday, 13 August 2026 | 3:00pm AEST
What’s in this release
Our July release (targeted for 30 July 2026) is a major one — and this webinar is your chance to see it before it lands in your repository. We’ll walk through what’s changing, why it matters, and what your team needs to do to prepare.
Item Type Based Metadata
The most requested framework upgrade is finally here. We’ll cover:
- How tailored metadata by group and item type improves discoverability and researcher experience
- The 29 new stock metadata fields — including journal and supervisor — and how they map to DataCite, Elements, and Crossref
- New admin controls for customizing field labels and guidance text (yes, you can finally rename “description” to “abstract”)
- The refreshed edit-item interface, including the new collapsible Additional Details section
- What migration looks like for existing repositories, and how to get on the queue
Expanded Geospatial Metadata
Geospatial context is no longer limited to individual items. We’ll show how the same rich mapping capabilities now extend to Projects and Collections — so your researchers can report on geographic data at scale, not just item by item.
Smarter Submission Controls for Groups
More precision, less friction. See the new group-level submission settings that let admins control exactly who can upload — from open to all users, to admin-only, to fully archived groups.
Plus: Fixes You’ll Notice
A rundown of the smaller fixes rolling out alongside the big features — from Sherpa Romeo sync issues to Collection keyword publishing and OAI-PMH stability.
Who should attend
- Repository administrators planning their upgrade path
- Institutional teams evaluating the Item Type Based Metadata migration
- Anyone managing groups, submissions, or geospatial data in Figshare
- Developers maintaining custom integrations (we’ll touch on the new V3 API)
Why attend
This release introduces real structural changes — including a new API version and an optional-but-recommended metadata migration. Getting ahead of it now means a smoother transition for your institution later.
