iugonet 20100706 poster

1
Adaptation of DSpace to Geoscience Yukinobu KOYAMA *1 , Takahisa KOUNO *2 , Hiroo HAYASHI *1 , Tomoaki HORI *2 , Yoshimasa TANAKA *3 , Daiki YOSHIDA *1 , Satoru UeNO *1 , Masato KAGITANI *4 , Shuji ABE *5 , Atsuki SHINBORI *1 , Naoki KANEDA *1 *1 Kyoto Univ., *2 Nagoya Univ., *3 NIPR, *4 Tohoku Univ., *5 Kyushu Univ. Contact address: [email protected] http://www.iugonet.org/ The 5th International Conference on Open Repositories Madrid, Spain July 6th – 9th, 2010 IUGONET will provide the analysis software which is based on the THEMIS Data Analysis Software suite on IDL developed by UCB and UCLA. It runs on the client side. IUGONET [Current Status] • Building the metadata DB for geoscience by using DSpace 1.5.2. • Metadata files in XML is stored as ‘content’ of DSpace. • Preparing the connection between the metadata DB & the analysis software via SRW/SRU. [Schedule] • IUGONET will release the beta version of the metadata DB & the analysis software in Apr. 2011. Conclusion Issues for investigating upper atmosphere Metadata DB for Upper Atmosphere The integration analysis by using various kinds of observational data is necessity for investigating the mechanism of long-term variations in the upper atmosphere. However, there are no way to cross-search their DBs which are distributed over many research institutes. For resolving this inconvenience, we build the metadata DB in order to cross-search their DBs. References [1] Metadata format utilized for the IUGONET metadata database, Tomoaki HORI et al., MGI015-02 , JPGU 2010 [2] SPASE 2.0: a standard data model for space physics, Todd King, James Thieman and D. Aaron Roberts, Earth Science Informatics, 1865-0473 C onnection betw een the m etadata D B & the analysis softw are C lientSide IUG O NET m etadata D B (1)Q uery (3b)W get (Internalcall) (ID LVM +TD A S) (D Space) (SRW /SR U ) (2)M etadata (4) O bservational data (3a)Load procedure (5)Plot • Metadata which includes location information (e.g., URL) of observational data is sent to the analysis software via SRW/SRU. •The analysis software downloads observational data by using the location information. Connection between the metadata DB & the analysis software The SRW/SRU will be opened also to the other applications. We are discussing to switch to DSpace 1.6.2 to use OpenSearch too. SnapshotofRegionalSearch UI Implementing Specification ofC oordinate Metadata DB System •CentOS 5.3-x86_64, •DSpace 1.5.2, •Httpd-2.2.3- 31.el5.centos.4, •Apache-tomcat- 6.0.20, •Postgresql-8.1.17, •SRW/SRU rev. 126. We adopted DSpace as our metadata DB system because there are so many case examples in Japanese academic information repositories. Our development environment are, We designed the IUGONET common metadata format [1] which is based on the SPASE Data Model [2]. Basically the metadata includes URL of observational data, start time of observation, spatial coverage of observation and so forth. The additional elements of our own to the SPASE format are, Metadata Format & Customization Points SPASE Data M odel& an exam ple ofthe m etadata E xam ple ofM etadata D stindex) Above m etadata corresponds to the “N um ericalD ata”in the left figure. Search Target By Todd King etal.Earth Science Inform atics,1865- 0473 •element for describing the analogue data, •element for describing the longitude and latitude which observation covers, •element for describing the coordinate system for Solar images. Institude 2 U niversity 3 Research C enter1 A urora D ata DB S olarD ata DB G eom ag.D ata DB G eom ag. Data Experts ・・・・・・ A urora D ata Experts SolarD ata Experts C ross-search forvarious kinds ofobservational data from research institutes. DB access via metadata DB ・・・・・・ M etadata D B Metadata G eneration XML Sharing M D am ong allM DB Ideally, the metadata DB system which can deal with arbitrary metadata is the best but •default setting of DSpace is for Dublin Core metadata format, •IUGONET Common metadata format has deeper tree structure than Dublin Core metadata format. Therefore we gave up to handle complete shape metadata which is described in IUGONET common metadata format as ‘metadata’ of DSpace. Then we customized it according to following two rules. In the near future, the metadata DB system which can deal with arbitrary metadata will be needed. ---> DSpace 2.0 ?? Exam ple ofthe records in the m etadatafieldregistry table AccessInformation Form at Num eric alData 2 177 SourceU R L Granule 2 147 qualifier element metadata _schem a _id metadata _field_id <Spase> <Num ericalData> <AccessInformation> <Form at/> </AccessInformation> </Num ericalData> </Spase> <Spase> <Granule> <Source> <UR L/> </Source> </G ranule> </Spase> 1.Complete shape metadata is stored as ‘content’ of DSpace. 2.Some search targets are chosen from the metadata (qualifier is created like right figure.) Inter-university Upper atmosphere Global Observation NETwork

Upload: yukinobu-koyama

Post on 20-Jun-2015

25 views

Category:

Technology


3 download

TRANSCRIPT

Page 1: Iugonet 20100706 poster

 

 

Adaptation of DSpace to Geoscience

Yukinobu KOYAMA*1, Takahisa KOUNO*2, Hiroo HAYASHI*1, Tomoaki HORI*2, Yoshimasa TANAKA*3, Daiki YOSHIDA*1, Satoru UeNO*1, Masato KAGITANI*4,

Shuji ABE*5, Atsuki SHINBORI*1, Naoki KANEDA*1

*1 Kyoto Univ., *2 Nagoya Univ., *3 NIPR, *4 Tohoku Univ., *5 Kyushu Univ.

Contact address: [email protected] http://www.iugonet.org/

The 5th International Conference on Open Repositories Madrid, Spain

July 6th – 9th, 2010

IUGONET will provide the analysis software which is based on the THEMIS Data Analysis Software suite on IDL developed by UCB and UCLA. It runs on the client side.

IUGONET

[Current Status]• Building the metadata DB for geoscience by using DSpace 1.5.2.• Metadata files in XML is stored as ‘content’ of DSpace.• Preparing the connection between the metadata DB & the analysis

software via SRW/SRU.[Schedule]• IUGONET will release the beta version of the metadata DB & the

analysis software in Apr. 2011.

Conclusion

Issues for investigating upper atmosphere

Metadata DB for Upper Atmosphere

The integration analysis by using various kinds of observational data is necessity for investigating the mechanism of long-term variations in the upper atmosphere. However, there are no way to cross-search their DBs which are distributed over many research institutes. For resolving this inconvenience, we build the metadata DB in order to cross-search their DBs.

References[1] Metadata format utilized for the IUGONET metadata database, Tomoaki HORI et al., MGI015-02 , JPGU 2010

[2] SPASE 2.0: a standard data model for space physics, Todd King, James Thieman and D. Aaron Roberts, Earth Science Informatics, 1865-0473

Connection between the metadata DB & the analysis software

Client Side IUGONET metadata DB

(1) Query

(3b) Wget(Internal call)

(IDLVM+TDAS) (DSpace)

(SRW/SRU)

(2)Metadata

(4) Observational data

(3a) Loadprocedure

(5) Plot

• Metadata which includes location information (e.g., URL) of observational data is sent to the analysis software via SRW/SRU.

•The analysis software downloads observational data by using the location information.

Connection between the metadata DB & the analysis software

The SRW/SRU will be opened also to the other applications. We are discussing to switch to DSpace 1.6.2 to use OpenSearch too.

Snapshot of Regional Search UI (Implementing)

Specification of Coordinate

Metadata DB System

•CentOS 5.3-x86_64,

•DSpace 1.5.2,

•Httpd-2.2.3-31.el5.centos.4,

•Apache-tomcat-6.0.20,

•Postgresql-8.1.17,

•SRW/SRU rev. 126.

We adopted DSpace as our metadata DB system because there are so many case examples in Japanese academic information repositories. Our development environment are,

We designed the IUGONET common metadata format [1] which is based on the SPASE Data Model [2]. Basically the metadata includes URL of observational data, start time of observation, spatial coverage of observation and so forth.

The additional elements of our own to the SPASE format are,

Metadata Format & Customization Points

SPASE Data Model & an example of the metadata

Example of Metadata

(Dst index)

Above metadata corresponds to the “NumericalData” in the left figure.

Search TargetBy Todd King et al. Earth Science Informatics, 1865-0473

•element for describing the analogue data,•element for describing the longitude and latitude which observation covers,•element for describing the coordinate system for Solar images.

Institude 2 University 3Research Center 1

Aurora DataDB

Solar DataDB

Geomag. DataDB

Geomag. Data

Experts

・・・・・・

Aurora Data Experts

Solar DataExperts

Cross-search for various kinds of observational datafrom research institutes.

DB access via metadata DB

・・・・・・

Metadata DB

Me

tad

ata

G

en

era

tio

n

XML

Sharing MD among all MDB

Ideally, the metadata DB system which can deal with arbitrary metadata is the best but•default setting of DSpace is for Dublin Core metadata format,•IUGONET Common metadata format has deeper tree structure than Dublin Core metadata format. Therefore we gave up to handle complete shape metadata which is described in IUGONET common metadata format as ‘metadata’ of DSpace. Then we customized it according to following two rules.

In the near future, the metadata DB system which can deal with arbitrary metadata will be needed. ---> DSpace 2.0 ??

Example of the records in the metadatafieldregistry table

AccessInformation

Format

NumericalData

2177

SourceURLGranule2147

qualifierelementmetadata_schema_id

metadata_field_id

<Spase><NumericalData>

<AccessInformation><Format/>

</AccessInformation></NumericalData>

</Spase>

<Spase><Granule>

<Source><URL/>

</Source></Granule>

</Spase>

1.Complete shape metadata is stored as ‘content’ of DSpace.

2.Some search targets are chosen from the metadata (qualifier is created like right figure.)

Inter-university Upper atmosphere Global Observation NETwork