Skip to main content

Idea behind Lumeer


Most information systems take data, store them, display them, allow the users to modify them and do some reporting. However, information systems are usually highly specialized, doing just one thing. Whenever you need something slightly different, you need another information system. 

Small companies, or even project leads cannot afford this so they frequently tend to use spreadsheets. Spreadsheets are damn old by the way. They originated in sixties. They did not get much significant improvements till today. The most significant risk with spreadsheets is that they do not watch for data integrity. And many sheets suffer from losing this integrity over time. Until their maintainer throws them away and starts from scratch. 

Compared to the traditional information systems that usually makes the user work with the data in the model that is very similar to the underlying database model, the spreadsheet users rarely follow this pattern. In spreadsheets people never create individual tables with entities to later build a report or chart on them. No, they rather start by creating a table that is more similar to a report and combining several types of entities. Something like a contingency table for example. 

With modern technologies we could do much better than what spreadsheets can offer to us. And for much cheaper than highly specialized information systems. We need to allow the users to work with the data in a way that is natural to them but yet store them in a way that is optimal for the database performance, data updates and querying. 

Nevertheless, the user does not need to know about this underlying model. They need to see their data in the form they want. In the form that is most efficient for their use. Also, the users might sometimes need some help with organizing their data. Like an advanced IDE for developers that can underline your suspicious code and suggest a fix or refactoring. We need to be able to notice a bad data design and suggest an automated fix.

Comments

Favorites

How to track tasks for employees?

When multiple employees work on multiple projects, even in a small company it can easily happen that you lose track of who is doing what and on which project. However, it is very important to have quick and easy access to this kind information: you want to know progress on a project to plan for the future release, or you want to see if employees have some spare capacity or are too overwhelmed by the workload. 
Maybe you feel that all that information is being lost in a pile of spreadsheets and emails. They are all there, but to access them means to spend precious minutes or even hours on searching the documents, every time. You wish to have everything in one place, with every question about current status or capacity answered within seconds and with just a few clicks. You want to easily make changes that are smoothly and automatically propagated to relevant people in the company. In this article, we will show you how to achieve this with Lumeer.
After we login into Lumeer, we create …

How to create a comprehensive overview of job postings

Managing information about two or three job postings at your company is easy and can be done even in some simple tool or spreadsheet. However, as the number of postings, candidates and other information grows, it becomes increasingly difficult not to get lost in the data and maintain a clear overview. There are candidates with their names, addresses and positions they are applying for. There are also job postings with salaries and managers who want to hire people for those positions. Those pieces of information are related to each other and we will show you how to effectively manage and view them with Lumeer. As Lumeer allows us to put similar data to collections, we will want to store information about candidates, job postings and company’s employees in separate collections. It’s the most intuitive way because candidates have similar attributes, e.g. name, address, phone number or the date they applied for a job at the company. On the other hand, postings have their names and salaries…

How to effectively search and publish townhall meeting's resolutions

In previous posts, we created invitation to a townhall meeting and added minutes and comments. The collections are now filled with data and we will show you how to search those data and easily export them into publishable form.

After every townhall meeting, the municipality has to publish the resolutions which were approved during the meeting. To achieve that, we first search for the data we need by using Lumeer’s search box. We adjust the filters, hit enter and immediately see all resolutions from particular meeting.

We see the result of the search in table perspective, but we switch it to smart document perspective and produce the list of resolutions in a similar way that we have created the invitation.



Of course, we can choose how we want to export the document. Do we want to print it? Then we use export to PDF. Do we want to publish it on municipality’s website? We can put the PDF there, or, even simpler, we just put there the link to document which points directly to Lumeer, where t…