Progress of the database project.

KWA meeting Forchheim 2004

Introduction.

Progress.

Plan of attack.

Details of plan of attack.

Some points for defense

Conclusions

Progress of the database project.

KWA meeting Forchheim 2004

Introduction.

“One of the main goals of our association is the construction of a universal bibliography of all chess books ever published. This is a most ambitious goal, and we can only succeed if we make use of the combined knowledge and talent of as many chess literature addicts as we can get hold of. This means that we need the participation of the members - with whatever contribution they are willing and able to provide.

Every building has to stand on a firm ground; therefore, our first step is to write down a concept, FRBR, for the database. The current version is in the member area.”

Andreas Saremba

FRBR: main part has been conceived by Andreas Saremba

Progress of the database project.

KWA meeting Forchheim 2004

Progress.

Defining the FRBR concept:

(s)low member participation

Jurgen Stigter visited Andreas Saremba

no further progress

Technical points discussed and further actions proposed

by Scutala b.v.

sketch of the current status

plan for continuation of the database project

Technical work (hardware and software) done by Scutala b.v.

(postgresql) database is running under Linux

with part of the catalogue of the LN with corrections

work for acquiring title descriptions by internet

from existing libraries using MARC records (Z39 protocol)

Progress of the database project.

KWA meeting Forchheim 2004

Plan of attack.

1) implement the FRBR concept in the existing postgresql database.

2) get entries from existing libraries of (all) Philidor publications

3) put these into the database, using the FRBR concept

4) build user interface, for experts and normal (member) users

5) let the KWA members improve the resulting Philidor database, using their own copies

6) improve the FRBR concept (and GUI) based on the Philidor experiences.

side effect of plan: to activate the KWA members!

Progress of the database project.

KWA meeting Forchheim 2004

Details of plan of attack (1)

1. Implement the current FRBR concept in the postgresql database

1A.	Implement the FRBR concept in the current database used

(almost) finished – easy to do.

changes in the FRBR concept will be simple to implement, initially

1B. Add (existing) user interface (GUI). This GUI needs to be improved. One of the aims of the plan is to activate the members to take part in defining the user requirements! [Some requirements have been made in November 2003, but no further work was done on these; planning of user requirements and GUI to be added in the next version of this document; also see 4]

1C. Translate the current content (LN data) to the FRBR model and add to the database (as unconfirmed entries). This will be an easy job (as long as one accepts some errors of translation; to be corrected by experts). Please note that the real hierarchical FRBR structure work – expression – manifestation – item will NOT be generated and cannot be generated automatically (see 3B)

Progress of the database project.

KWA meeting Forchheim 2004

Details of plan of attack (2)

2. Get entries from existing libraries of (all) Philidor publications

2A. A programme to obtain data from libraries that have a catalogue of MARC records available, is ready.

2B. Make a list of libraries we want to use; for each of these libraries we must find its IP number, the name of the database, the port number and the relevant query (so as to exclude non-chess entries).

2C. Make a ("flat") table with a column for each separate data field used in the MARC record (each library will have its own table)

2D. Unify the tables for the different tables (differences of the MARC records of different libraries are not expected to be big, due to MARC record standardisation); result will be a unified table.

Progress of the database project.

KWA meeting Forchheim 2004

Details of plan of attack (3)

3.	Put unified MARC records into the database, using the FRBR concept

3A. Transform the unified table into the FRBR database, trivially each entry is transformed into an item and an author.

3B. Add some automated intelligence (structure) to the database by reduction of identical authors to one author, and identical items to one manifestation, one expression and one work

May use the OCLC algorithm
(see http://www.oclc.org/research/projects/frbr/algorithm.htm)

Progress of the database project.

KWA meeting Forchheim 2004

Details of plan of attack (4)

4A.	Make user requirements for user interfaces (GUI).
Need reactions from members;

(proposals from November 2003 not yet reviewed)

4B.	Build expert GUI.

Will take much time,

need interaction with expert users.

Expert user needs to be able to verify, identify, change and confirm,

in particular, check and correct the hierarchical structure

resulting from automated transformation.

4C.	Build normal (member) user GUI.
Normal users can add entries (items from their own library)

and add remarks to entries

[unconfirmed entries, to be cofirmed by an expert]

Progress of the database project.

KWA meeting Forchheim 2004

Details of plan of attack (5)

5.	KWA members improve the resulting Philidor database
using their own copies (“items”).

6.	Improve the FRBR concept (and GUI) based on the Philidor experiences.

Some points for defense

Thesaurus for variants of author names

Controlled vocabularies

Uniform presentation of titles

Record metadata

confirmation state

authority

...

Progress of the database project.

KWA meeting Forchheim 2004

Conclusions

Implement FRBR concept

Get Philidor entries from libraries

Add (G)UI for experts and normal (member) users

Check and improve Philidor database

Improve the FRBR concept

Improve GUI's

We need your participation!!

Jurgen Stigter

2004-09-17T17:12:31