80 likes | 159 Views
The ADEPT Middleware Effort. Greg Janée. ADEPT’s middleware effort. Broad goals distributed digital library for georeferenced information DL interoperability ADEPT-specific goals interface to library infrastructure for information creation, organization, management & publishing.
E N D
The ADEPT Middleware Effort Greg Janée
ADEPT’s middleware effort • Broad goals • distributed digital library for georeferenced information • DL interoperability • ADEPT-specific goals • interface to library • infrastructure for information creation, organization, management & publishing
Recent activities • Distributed, peer-to-peer architecture • multiple, “local” servers; inter-server cooperation • central collection discovery service • Bucket metadata framework • representation & utilization of metadata mappings • Personal collections • lightweight; utterly heterogeneous; totally automated • create, import, categorize, manage items • Miscellaneous new features • collection groups, load balancing, ... • Packaged & documented
Middleware architecture client • uniform client services • item-level metadata mapped to search buckets (high-level, typed fields with rich search semantics) • uniform collection- level metadata includes coverage histograms • plugins support common collection implementations collection discovery service middleware RDBMS Z39.50 proxy collection collection personal item item item
increasing semantic richness Z39.50+MARC+ AACR2 SDLIP GDLIP HTTP+ HTML OAI SOAP increasing structure, standardization increasing generality The interoperability landscape ADEPT
Interaction with NSDL metadata repository harvest OAI portal 2. harvest & interpret 3. h & i metadata ADEPT 1. map ADEPT collection discovery ADEPT client ADEPT per collection provider
Next steps • In 6 months or less: • Complete middleware & collection discovery service • Stop development • diminishing returns • extreme generality of limited use to ADEPT • Then: • Focus on bringing GIS functionality into the library • necessary for effective use • ADL has almost none; corollary: ADL is unusable • interfaces, tie-ins, “lite” tools, indexing techniques • More information: • http://www.alexandria.ucsb.edu/~gjanee/middleware/
Gazetteer protocol • Streamlined for & specific to gazetteers • Supports 5 fundamental queries • name, footprint, class, relationship, identifier • Lightweight • 80/20 rule used throughout • accommodates differing implementations • simple services that can be combined into higher-level services • Buzz-compliant: HTTP, XML, schemas, SOAP, GML • More information: • http://www.alexandria.ucsb.edu/~gjanee/gazetteer/