Biomedical Engineering Reference
In-Depth Information
a lot of our research data are stored together in one database so for that
piece RDF might not be appropriate at the moment. The large amounts
of publicly available external data that scientists use in their daily work,
on the other hand, are good candidates for linking via RDF [44]. In order
to continue to follow the one-system strategy, we are looking to display
these linked external data sources in LSP alongside the internal data so
the scientists can freely link to the external world or our in-house data.
With the new cloud-based possibilities for large-scale data storage and
number crunching [45], a very likely future improvement to LSP will be
use of a cloud-based setup for property calculations. In such a setup the
scientists would submit the job and LSP would load the work to the
cloud in an asynchronous way and return when the cloud calculator is
done. The fi rst cloud-based pilot projects have been initiated to better
understand what the best future setup would look like.
Another new area to move into could be high-level management
overview data. As all information is in one place, it would not be diffi cult
to add more management-type views on the data. If overall research/
discovery projects have meta-data like indication, risk, phase added, we
could then deliver portfolio-like overviews, which management currently
produce by hand in Powerpoint. Chapter 17 by Harland and colleagues
is relevant here, using semantic MediaWiki in managing disease and
target knowledge and providing an overview to management. We also
know how many compounds have been produced for the individual
projects in what time period, by whom working for which partner and
located at which site. This could give the project teams and management
quick access to data about turnaround time and other effi ciency metrics
at the same front-end at which they can dive into raw data.
Lundbeck Research Informatics is participating in the Innovative
Medicines Initiative (IMI) OpenPhacts project [46]. Our main
contribution to the project is likely to be the front-end, which basically
will be a scaled-down version of LSP, which we can further develop to fi t
the needs of the IMI project. The data in the project will be based on RDF
and a triple store (Figure 1.6), so we will hopefully be able to improve the
way LSP handles this type of data by means of the project and use that
experience for our internal RDF data handling.
As true believers in open source software development, we feel obliged
to give something back to the community. We therefore plan to open
source the LSP platform development, under the name LSP4All, so others
can download it and use it for data management in their labs, but
naturally also because we thereby hope that others will join the team and
help develop LSP further to the benefi t of all future LSP users.
Search WWH ::
Custom Search