Version 15 (modified by Dominic König, 10 years ago) ( diff )


UUID conventions


All records in Sahana Eden which shall be shared with other instances or applications must have a universally unique identifier (UUID).

In Sahana Eden, these record UUIDs must be ASCII strings.

Eden automatically generates a UUID for each record according to the specifications in RFC4122:

All record UUIDs generated by Sahana Eden are strings in URN notation:


If a record is imported into Sahana Eden and it already has a UUID, then Eden will retain this UUID as-is (exception: local domain prefix, see below) - without any syntax validation (i.e. no specific UUID schema is required). However, for consistency reasons, we recommend to use URNs.

Some data formats (e.g. PFIF) may require a domain prefix for a UUID, followed by a slash:

Where such a domain prefix is used and it matches the local domain of the importing Sahana instance, it will be removed during import.

URNs instead of UUIDs

Eden has just moved from UUIDs to URNs in order to enhance interoperability in multi-application scenarios like Haiti or Pakistan.

From experience we know that data exchange in the field can involve a variety of applications other than Eden, each implementing their own identifier schemes - and furthermore data sets which instead of application-specific IDs use officially assigned identifiers (e.g. PAHO IDs for health facilities in Haiti). Implementation of URNs will add support for both multiple different identifier schemes, as well as cross-application common namespaces and ID schemas (as favorable e.g. for geolocations or personal data).

In practise, that means:

  • there should be a common namespace for sahana applications, at best "sahana"
  • uuid="" would become something like uuid=""
  • Eden can support other namespaces, by making the namespace a configurable attribute of the "uuidstamp" reusable field


We need an agreed set of UUIDs for GIS Data so that we can share data more easily across systems, such as the current Pakistan data


Note: See TracWiki for help on using the wiki.