Data GUIDs enable you to mint globally unique identifiers for data in a scalable distributed architecture.Learn more
Supports trillions of GUIDs across a distributed set of commons. Never worry about too many GUIDs again!
The platform is open for modification and inspection. Pull requests welcome.
Lookups are free and minting is free. Always.
Unopinionated namespaces allowing for distributed lookups and global uniqueness.
Crafted with extreme care for the Data Biosphere.
Use the Data Object Service API to resolve your GUIDs today.
Turn your Data GUID into information you can use!
Data GUIDs are are the way to go for identifying your data objects. I love the prefixes feature, which helps you resolve the location of the data object given the GUID. With the global uniqueness and the prefixes, these data GUIDs are also FAIR compliant.
A very common problem for programmers is describing data in such a way that does not assume its location. Data GUIDs provide an easy-to-use and extensible namespace for describing data that gives programmers confidence their data can be later reused, or retracted. By decoupling data representation from data access, Data GUIDs allow a ground up representation of uniqueness that can span most cloud and on-premises service architectures. That means that software written around Data GUIDs will be easier to migrate from one platform to another, and that strong guarantees can be given that two parties are computing on the same data.
It was always a burden when my identifiers were only unique within a database. Merging databases? Pulling data objects from multiple locations for analysis? What a headache! But with globally-unique identifiers for my data, I can analyze without worrying about identifiers being duplicated and my analysis being sullied. Well, at least being sullied by duplicate IDs. Thanks dataguids.org!
As a software architect, I appreciate that the GUIDs keep my end users happy. My software mints globally unique identifiers in multiple data commons or other storage solutions–GUIDs for files, for datasets, or even for collections of datasets–and then my users can search multiple data commons, know the data’s “home” database, and then do their analysis. They can even build apps on top of my software to automate much of the process. And when my users are happy, I’m happy.