Halti 2 – New Data Management System for FinELib

Teemu Mattila8.6.2004

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 2

Current Data Management in FinELib

• Existing system, Halti, opened in 2000• Halti was designed for managing

– IP-numbers and payment shares of the consortium members

– Contact information of the members and publishers

– Usable via web browser

• Quite a few tasks are done more or less manually (registration to the resources, usage statistics, key figures..)

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 3

What Do We Want?

• Grant access to the data to the member organizations– Organizations could verify their subscriptions,

payment shares etc. from the system

• Better means for manipulating and managing data– Summary reports, exporting data from the

database, more accurate information, automated processes

• Less manual work

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 4

Why Entirely New System?

• Halti is acceptable system but has its flaws– Halti does not preserve past data– Remote use is not possible– Technically very inflexible and not suited for

some tasks

Easier to build from the scratch than to repair

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 5

Some Key Differences

Database & Application Server

Database Server

Application Server

IP authentication

Authentication

User User

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 6

Detailed Features of Halti 2

• Exporting data– Spreadsheets, (preformatted) web pages

• Summary reports– Yearly usage, payment and key figures

automatically for each organization and sector as well as for entire consortium

– Possibility to convert all currencies to e.g. euros

• IP number reports– Somewhat similar to Halti 1

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 7

Detailed Features of Halti 2

• Registration to the resources– Better checks for valid data and confirmations

• Remote use– Authentication based to the IP address or SSL-

encrypted username/password

• User interface– At least UI for customers must be easy to use

• Maintaining– Documentation and modular structure to help

updating and renewing

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 8

Schedule

• Database and test data by the end of June• User interface (application) in pieces

– Some easy parts, such as contact information, during July

– Entire application ready for testing before the end of August (preferably at the 20th of August)

– “Possible” bug demolishing and actual data insertion during September

– Production usage at the end of September

• Possible glitches might delay the launch

8.6.2004 Halti 2 - Nordic Meeting, Helsinki 9

Technical Jargon

• Database system: Oracle 9i• Web server: Dell PowerEdge

2650 • Operating system: Red Hat Linux Ent.

3.0• HTTP server: Apache 2• Application

programming: PHP 4