haber16 10 97
TRANSCRIPT
-
8/14/2019 haber16 10 97
1/17
Cornelia Haber- 1The MeDoc-Project: Meta Data13.10.97
The MeDoc Project:
Meta Data
Cornelia Haber, Universit t Oldenburg
-
8/14/2019 haber16 10 97
2/17
Cornelia Haber- 2The MeDoc-Project: Meta Data13.10.97
Project Partners
Project Aims
Motivation, Goals, ...
MeDoc Service
Architecture, Components, ...
Full Text ServerRequirements, Functionality, ...
Document Model
Attributes supported, Document Structure, ...Meta Data Administration
Scripts, ...
Conclusion
Contents
-
8/14/2019 haber16 10 97
3/17
Cornelia Haber- 3The MeDoc-Project: Meta Data13.10.97
Project Partners
FU Berlin
Uni Bonn
Uni Dortmund
FernUni Hagen
FIZ Karlsruhe
TU M nchen
OFFIS Oldenburg
Springer-Verlag
Consortium:
GI (German Computer Science Society)
Fachinformationszentrum Karlsruhe
Springer- Verlag
Development Team:
With the help of:12 Publishing Houses
23 Pilot User Institutions
-
8/14/2019 haber16 10 97
4/17
Cornelia Haber- 4The MeDoc-Project: Meta Data13.10.97
Motivation
State of the art
Information needs
finding information
choosing relevant information
Information flooding
exponential growth of scientific literature publications
information distribution over the Internet
CONTRADICTION
-
8/14/2019 haber16 10 97
5/17
Cornelia Haber- 5The MeDoc-Project: Meta Data13.10.97
Project Aims
To offer
a critical mass of high quality computer science literature
in form of electronic documents
as full-texts
over the Internet
Development and evaluation ofuser-oriented tools
economical forms to acquire, provide and use electronic documents
Conception of an information brokering service for
heterogeneous
distributed databases
-
8/14/2019 haber16 10 97
6/17
Cornelia Haber- 6The MeDoc-Project: Meta Data13.10.97
MeDoc-Service: Architecture
Accessing the MeDoc-Library:
1. Provider Registration
2. User Query
3. Provider Selection
4. User Query5. Document References
6. Browse Order
7. Document
Client Client
Broker
Provider Agent Provider Agent
Database Database
User Agent User Agent
1
3
4 56 7
2
-
8/14/2019 haber16 10 97
7/17
Cornelia Haber- 7The MeDoc-Project: Meta Data13.10.97
Requirements on FTS
Full Text Server is special Provider Agent
Functionality to be supported by the Full Text Server:
Delivery of Meta Data ( Broker)
Meta Data:
BibTeX attributes objecttype (type of document, e.g. book, journal, ...)
keywords
classification (ACM)
Meta Data is description of all documents of a providerMeta Data is calculated as
sum of the weights of a word over all documents
number of documents
-
8/14/2019 haber16 10 97
8/17
Cornelia Haber- 8The MeDoc-Project: Meta Data13.10.97
Requirements on FTS
Searching
Query in MeDoc-Query-Language
(Attributes linked with AND, OR, WSUM)
MeDoc attributes
Document Delivery
physical / logical document structureNavigation
hierarchy within the attributes
hierarchy within a document
navigation according to attributes
Document Model
-
8/14/2019 haber16 10 97
9/17
Cornelia Haber- 9The MeDoc-Project: Meta Data13.10.97
Document Model
The document model contains
bibliographic and content description attributes
information about document module full text
sample
abstract
table of context
index
glossary
...
information about document hierarchy
logical document structure
physical document structure
-
8/14/2019 haber16 10 97
10/17
Cornelia Haber- 10The MeDoc-Project: Meta Data13.10.97
Document Model
Textfragment
Structured Text
Journal
Literary Item
Volume Issue
Collection Subchapter
Proceedings
Book Subchapter
Series
Misc
Chapter
Article
-
8/14/2019 haber16 10 97
11/17
Cornelia Haber- 11The MeDoc-Project: Meta Data13.10.97
Administration
Inserting new documents
batch oriented
LitiScript contains bibliographic and structural data
Changing existing documents
only simple changes otherwise:delete and insert
-
8/14/2019 haber16 10 97
12/17
Cornelia Haber- 12The MeDoc-Project: Meta Data13.10.97
Liti Script (1)* Zuerst die Textfragmente */
@fragment{appelrathbuch,
file="Books/appelrath/Skriptum.Informatik.html",
file="Books/appelrath/0.0_Vorwort.html",
file="Books/appelrath/chars/*.gif",
sub={sample,
sub={titel,
file="Books/appelrath/Skriptum.Informatik.html",
file="Books/appelrath/Skriptum.Informatik.anc.gif",
file="Books/appelrath/chars/topg.gif",
file="Books/appelrath/chars/next.gif",
file="Books/appelrath/chars/inhalt.gif",file="Books/appelrath/chars/index.gif",
file="Books/appelrath/chars/prevg.gif"
},
sub={inhalt,
file="Books/appelrath/SkriptumTOC.doc.html"
},
/* Anhang */
file="Books/appelrath/A.1_Anhang_A_Mathematik.html",
file="Books/appelrath/A.2_Anhang_B_Syntax*.html",
/* Literatur */
file="Books/appelrath/A.3_Literatur.html",
/* Abkuerzungsverzeichnis */
file="Books/appelrath/A.4_Abkuerzungen.html",
/* index */
file="Books/appelrath/SkriptumIX.doc.html",
/* Die Kapitel */
sub={chapter1,
file="Books/appelrath/1.1_Grundlagen.html",
file="Books/appelrath/1*.html",
file="Books/appelrath/1*.gif",
-
8/14/2019 haber16 10 97
13/17
Cornelia Haber- 13The MeDoc-Project: Meta Data13.10.97
Liti Script (2)/* Die Literary Items */
@item{buch,
type="book",
author="Hans-Juergen Appelrath",author="Jochen Ludewig",
title="Skriptum Informatik - eine konventionelleEinfuehrung",
date="95-01-01",
publishedby="Teubner Verlag",
docid="B 3-519-22153-5"
}
@item{chapter1,
type=chapter,
super=buch,
title="Grundlagen",
number="1",
docid="B 3-519-22153-5/1"
}
/* Die Strkturelemente */@structtext{
item=buch, fragment=appelrathbuch,
component=fulltext, format=html, usage=any
}
@structtext{
item=buch, fragment=inhalt,
component=toc, format=html, usage=any}
-
8/14/2019 haber16 10 97
14/17
Cornelia Haber- 14The MeDoc-Project: Meta Data13.10.97
alternative for LitiScript
better: Liti Script in form of an SGML-document
there is a DTD for MeDoc Meta Data
-
8/14/2019 haber16 10 97
15/17
Cornelia Haber- 15The MeDoc-Project: Meta Data13.10.97
alternative for Liti Script
still better: architectural forms:
assignment of the elements in a specific DTD to a general
class with known semanticassociates attributes with that meta element type
no predefined names
idref IDREF #REQUIRED
HyTime NAME #FIXED clink>
-
8/14/2019 haber16 10 97
16/17
Cornelia Haber- 16The MeDoc-Project: Meta Data13.10.97
Conclusion
MeDoc Meta Data schema is rather detailed
MeDoc Meta Data schema allows for functionality
enhancements
Administration of Meta Data is to be supported
Proprietary Meta Data solution
MeDoc Meta Data may be mapped to Dublin Core
further information about MeDoc:
http://medoc.informatik.tu-muenchen.de
-
8/14/2019 haber16 10 97
17/17
Cornelia Haber- 17The MeDoc-Project: Meta Data13.10.97
Thanks for your attention
Do you have comments, questions, etc?
[email protected]@informatik.tu-muenchen.de