Digital Resource Management in National Institute of Japanese Literature Shoichiro Hara (National Institute of Japanese Literature) , Yutaka-cho, Shinagawa-ku, Tokyo , Japan

National Institute of Japanese Literature - NIJL: 国文学研究資料館 - Founded in 1972  As an Inter-University Research Institute  By the Ministry of Education, Culture, Sports, Science and Technology (MEXT: 文部科学省 ) Mission  Survey Japanese Classical Literal Materials  Collect Originals and Microfilms  Public Access to Research Information We Have Done  Collected Materials  Organized their Information  Published Catalogues  Developed Variety Kinds of Databases

NIJL Databases Catalogue Databases  Holding Catalogues (Books and Microfilms)  Research Papers  OPAC (Online Public Access Catalogue)  Union Catalogue of Classical Books( 古典籍総目録 ) etc. Sharing Database of Historical Materials Image Database  Holding Original Materials (Approx. 1,000,000 frames)  Meiji Publications  Nara Picture Book ( 奈良絵本 ) etc. Full Text Databases  The Anthology of Japanese Classical Literature( 日本古典文学大系 )  21Waka-Anthologies ( 二十一代集 ) etc. Movie Pictures and more ・・・

Resource Management (Past Systems) 1. Investigation, Collection, Microfilming, Cataloging 2. Database Systems  Main-frame System  Networks (N-1) 3. Database Services  Catalogues  OPAC  Full-text Data  Image Data 4. Other Services  Publications  References, Reproductions  Education, Lectures, Exhibitions

Problems of Past Systems NIJL Systems were particular to its own purposes Heterogeneities of the Information Systems  System Architecture and Historical Background Different data structure Different data description  Complicate and High-cost Data Management Obsolescence of Hardware and Software  Regular/Periodic System Renewal CPU / peripheral devices Applications  System Reconstruction Reconstruction of applications /user Interfaces Data migration Coping with Hypermedia  No Standard Applications  Development for Particular System

Resource Management (Current Systems) 1.Data Portability  Introducing XML 2.Coping with Hyper Media  Unix Base Systems  Catalogue - Image 3.Databases  Catalogues  OPAC  Full-Texts  Images  Movies

Importance of Data Portability Maintenance  Data Independent from Hardware, Software  Readable Data Data Processing  Data Conversion to Web, Publishing, Database etc.  Data Backup and Transfer  Data Hub Format / Data Interchange Coping with Hypermedia  Web Pages  Linking with Images, Movies etc.  External Standard Character

Necessities for Portability Self-describing  An ability to define a set of data structure and provide a way to check that data conforms to a set of rules Readable Data  Data should be plain text files in ASCII, Latin 1 (ISO ) or Unicode (UTF-8 or -16)

Portability of XML Self-describing  DTD: Document Type Definition  XML Schema Can define element sets and provide a way to check that a document conform to a set of rules Readable Text  XML documents are plain text files in ASCII, Latin 1 (ISO ) or Unicode (UTF-8 or - 16)

Schema of XML as “an Intermediate Data” Data Base 1 Data Base 2 Application 1 Application 2 Interface Data Base 3 XML XSLT HTML PDF XHTML XML Spread Sheet

NIJL Present Multimedia Databases e-Book e-Book  Full Text Database  Reconstructed Books  WEB Books Image Database Movie Pictures Movie Pictures Image Databases of Holding Original Materials (Approx. 900,000 frames) Image Databases of Holding Original Materials (Approx. 900,000 frames)

Resource Management (Future Systems) Resource Sharing System Resource Sharing System Another Approaches Another Approaches  Web Based System  GIS

Resource Sharing Project What are the Problems ? Most Databases are Heterogeneous … Similar but Different Databases  Historical Background, Different Purposes Incompatibility  Different Operations, Non-Interoperability Inter-institutional Information Retrieval  Different Information Systems  Different Information Management Bases

Solutions might be ・・・ Introducing Standards for  Data Description (Portability)  Mutual Data Structure (Different Structures)  Data Retrieval (Compatibility) Standardization not by  Compulsion  Authority

3-layer Architecture (Standardization) Our efforts have been standardization of 1. First Layer: Database Layer  Description Portability  SGML/XML 2. Second Layer: Data Structure Layer  Mutual Data Structure  Metadata (Dublin Core, EDI, EAD, TEI etc ) 3. Third Step: Data Retrieval Layer  Protocol (Z39.50 etc)

Schema of 3-layers Architecture Existent Databases Existent Methods Data Description Standard Data Structure Layer Data Retrieval Layer Database Layer

The Merits of Layer Architecture Module Oriented  Easy to change sub-modules  Ex. from Z39.50 to Web Service (Retrieval Layer)  from DC to METS (Structure Layer)  Dictionaries (Database Layer) Protocol Oriented  Independent from hardware/software/venders

How to Link Heterogeneous System? Federation System by Dublin Core + Z39.50

Web-Z39.50 Gateway + Metadata (Resource Sharing System) Original Database Metadata Database Z39.50 Server Web Client Z39.50 Protocol Web-Z39.50 Gateway Server HTTPZ39.50 Protocol One Data View

Resource Sharing Project Inter-institutional Project  Linking Databases of Several Institutes Seamlessly The Graduate University for Advanced Studies  National Institute of Japanese Literature  National Museum of Ethnology  International Research Center for Japanese Studies  National Museum of Japanese History Universities  The Historiographical Institute, The University of Tokyo  Institute of South East Studies, Kyoto University  Osaka City University  Keio University ECAI Clearing House  IAS University of California Berkeley,  ACL aboratory dney the University of Sydney

Web Service - Next Z WEB Oriented  More Portability  Remote Procedure Call  System Architecture Independent Light Protocol Light Protocol  Only for Data Retrieval Introducing SOAP (Simple Object Access Protocol)  How to Treat ASN.1 ?

Experimental SOAP System

Information Retrieval by Time and Space Geo-temporal Information  Facts about specific time and places and their associations with other times and places on the Earth's surface Not all materials have enough bibliographic information  Archaeology (Historical Sites, Ruins, Remains)  Maps, Pictures  Physical events We use time and pace information in many aspects  5 W 1 H

Tool Example (ECAI TimeMap) Time Longitude Latitude Meta Data ECAI Metadata Data Set GIS Data TimeMap Metadata Attribution Data Project

Time and Place Data and Related Information Time and Place Data from Texts  Japanese Calendar ⇒ Gregorian Calendar  Old Place Name ⇒ Lat. And Lon. Related Information  Ex. Faults Map Superimposed

Related URL National Institute of Japanese Literature ECAI (Electronic Cultural Atlas Initiative) PNC (Pacific Neighborhood Consorcium) PRDLA (The Pacific Rim Digital Library Alliance) Contact