Global IDs

Updated 3 weeks ago by Tilo Mathes

Global IDs in RSpace

To ensure all research objects are uniquely identifiable and accessible, RSpace uses a global identifier system that assigns a persistent identifier to every object within the platform.

What are Global IDs?

In RSpace, a global ID is a unique identifier assigned to every object in the system. These IDs serve as permanent references that remain consistent throughout an object's lifecycle, regardless of whether it is moved, renamed, or otherwise modified. The global ID of an object can be typically found in the info panel of an object Info Panel.

Objects with Global IDs

Global IDs are assigned to all types of objects in RSpace, including:

ELN documents
Notebooks
Folders
Templates
Forms
Files in the Gallery
Samples
Containers (see also here)
Other resources such as users and groups. If the unique ID is not immediately visible on the page, you can usually determine it in the page URL or it may appear in the audit trail.

Global ID Format

Each global ID in RSpace follows a consistent format that consists of:

A prefix that indicates the object type (e.g., "GL" for gallery objects, "SA" for samples)
A unique number

For example:

GL12345 - A gallery object
SA53256 - A sample
SD78901 - A document

Resolver

RSpace features a resolver that translates global IDs into accessible links. The resolver URL has the format:

https://[instance-url]/globalId/[ID]

For example:

https://community.researchspace.com/globalId/SD53256

While the global ID itself is unique within a specific RSpace instance, combining it with the instance-specific resolver URL creates a globally unique identifier, similar to a DOI (Digital Object Identifier).

Benefits and Use Cases

Searchability and Reference

Global IDs provide a simple, reliable way for researchers to:

Search for specific objects within RSpace
Uniquely reference objects in external communications
Build links between related research objects

Persistence

A key benefit of global IDs is their persistence. Once assigned, an ID remains with its object permanently, even if:

The object is moved to a different folder
The object is renamed
The object is archived
The metadata associated with the object changes

Difference to PIDs

In contrast to globally unique PIDs, such as DOIs, IGSNs, ePIC, etc., which are provided as globally managed services, the persistence of the RSpace global IDs relies on the management of the individual RSpace instance. As long as an RSpace instance is maintained and accessible, the global IDs remain resolvable.

Permissions and Access Control

When accessing objects via their global IDs, RSpace's permission system remains in effect. This means:

Users can only resolve objects they have permission to access
Sharing a global ID or a link including the resolver URL does not override established access permissions
If you try to use a globalID to access a resource, but RSpace tells you that you do not have permisison to see it, try asking your PI or the system admin for more information about the current owner and location.

Practical Examples

While some researchers actively use global IDs in their workflows, many benefit from them "under the hood" without needing to interact with them directly.

Example 1: Referencing Samples in Lab Notebooks

A researcher can reference a specific sample in their lab notebook, providing a direct link to the sample's complete information.

Example 2: Organizing Local Files

Some researchers include RSpace global IDs in their local file naming schemes, making it easy to connect local files with their corresponding RSpace entries.

Conclusion

Global IDs in RSpace provide a robust foundation for research data management, ensuring that all research objects remain uniquely identifiable, searchable, and accessible throughout their lifecycle. Whether used actively in research workflows or operating behind the scenes, the global ID system is a key component of RSpace's research data management capabilities. RSpace also supports the use of external solutions for unique research objects identifiers, such as the IGSN sample identifier (see also Add IGSN IDs to your Inventory Items 🧪).