lablog

  • Increase font size
  • Default font size
  • Decrease font size
Start News
The News

Current state

E-mail Print PDF

A long time since the last entry... This, however, does not mean that nothing was done.

Done:

  • We improved the database layout at several points.
  • Finished the migration of the old version to the new one, which was quite a bit of work.

In progress:

  • We started, and this is almost done, to use Hibernate for database communication which, hopefully saves lots of work in the future...
  • Adaptation of the GUI to the new database layout
  • Automatic import of odml - metadata.
Last Updated on Friday, 07 May 2010 21:21
 

New Website online

E-mail Print PDF

The times of the quite old-fashioned website are over ;-) It was time for some more modern style... Some night shifts later the new version is online. The old docbook manual is also gone and the articles in the "features" section will take over this part. In the FAQs you may now find help for problems encountered...

Last Updated on Thursday, 19 November 2009 14:33
 

What's going on

E-mail Print PDF

Well, "news" might be a little too much... However, here is some information about the things that go on with the LabLog or are on the list.

Metadata:

One thing that, at the moment, consumes most of my programming time is the development of a format to transport metadata between data acquisition, data management and analysis tools. So far there exist a whole bunch of proprietary formats for writing down metadata but none, at least as far as I know, is open and flexible and simple(!) enough. Thus, together with Jan Benda (RELACS) and supported by the G-Node we set out to create a new one and quite some things have been done in the last months.

This format is of direct importance for the LabLog since semi-automatic import of metainformation is depending on it to converge to a first acceptable version.

Current development :

As indicated above implementing the import of metadata is on top of the list.

Furthermore, I started to reimplement large parts of the Journal which, besides ugly code, was simply not flexible enough.

These things will keep me quite busy for the next time. However, if you find bugs in the current version please let me know...

On the list:

  • Easier data retrieval capabilities so users, in most cases, do not need write SQL queries.
  • Better report that really includes all the information stored about a project. Maybe it will have the ability to create pdfs?!
  • Printer support
  • Administator options to adapt the table structure to current needs.
  • Documentation...
Last Updated on Wednesday, 11 November 2009 22:56