Object Store
How OneIS stores information
OneIS uses an Object Store to store data, rather than a traditional relational database.
When designing OneIS, we started by looking at the information our users needed to store, find, create and share. The “one size fits all” approach of a traditional database table can’t represent this information without severe compromise.
This meant that we had to start again, working from first principles. As Information and IT professionals working closely together, we had an opportunity to create great technology which handled information properly.
We were insistent that users should be able to enter information as they found it, and the system should make sense of it. A user shouldn’t have to work out how to store information, but just enter what they know.
We looked at the kind of information handled in the real world, and modeled our internal database around it. By working with the structure of information as it exists in the real world, we found we could store, find and process information without compromise. And, importantly, we found we could make the system much easier to use than traditional tools.
Objects in OneIS
Everything in OneIS is an Object, whether a record of a contact, a book, an organisation or a file. To match the real world, we impose as few limitations on entering information as possible, while organising it properly behind the scenes.
An Object is simply a list of facts, which we call attributes, about the thing being described. Attributes are much like the fields in a traditional database. But there are important differences. Every attribute can have multiple values, and there are no constraints on what type of data can be stored. The only requirement is that the object has a name, and is marked as a particular type of thing.
This truly reflects the information our users will be dealing with, and by removing constraints we avoid users entering bad data just to get around the system.
OneIS’ object store works effectively with this mass of data. If little information is given, it will make the most of it. But as more details are added and the relationships between objects are described, OneIS knows more and can find information more effectively.
We’ve taken the best ideas from concepts like the Semantic Web and standards like Dublin Core, and combined them into a pragmatic system designed to make information easy to manage.
» Technical details on how OneIS stores information
Good for users
Because OneIS represents information naturally, users just have to “fill in the form”. Even easier, OneIS uses the same style of form for every item entered, whether a file or a contact. A single way of entering all types of information makes it easier to learn how to use OneIS.
OneIS’ simple and unified way of storing all information makes it easier to configure and quick to get started with. We provide a carefully designed default setup with a schema and taxonomy suitable for most businesses.
The setup can be configured to precisely match your organisation. We can do this configuration for you or help you to do it. And, because it’s truly flexible, you won’t come up against unnecessary limitations and restrictions.
Future proof
We’ve also been very careful to avoid making any configuration decision impossible to undo later. As your needs evolve, the system can evolve with them. All the data within the system continues to work, without conversion!