The LRS database basically answers the question “Who does What?
These xAPI data can therefore be supplemented by additional databases that can help to deepen the analysis. In particular, other databases can help us learn more about the “Who” and the “What”.
For example, if your solution includes user profiles, you can connect it to your employee directory. Or have a database linking digital learning objects to skills. We then talk about HR data lake, projects that we see emerging internally in several large groups and managed by IT, but which are often difficult to start up because internal IT contacts do not have the knowledge about xAPI and traditional LMS editors do not offer this type of service to their customers.
For the more advanced ones, depending on your ecosystem, you can incorporate user clickstream into your applications, their geolocation data, or even more interestingly cross-reference this learning data with business data (from a CRM or other). Thus it is possible to have the correlation between trained population and increase in turnover for example.
In our current research work at Bealink, we are trying to go even further with regard to digital content (articles, videos, e-learning content, etc.) using Natural Language Processing techniques to automate the generation of the metadata required to enrich the data in the training catalogue.
In short, you have already understood this, and at the risk of repeating ourselves on this stage of processing and enriching digital learning data, it can only be done outside an LMS-type platform.