x server integration with the cdl common framework n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
X-Server integration with the CDL Common Framework PowerPoint Presentation
Download Presentation
X-Server integration with the CDL Common Framework

Loading in 2 Seconds...

play fullscreen
1 / 24

X-Server integration with the CDL Common Framework - PowerPoint PPT Presentation


  • 131 Views
  • Uploaded on

X-Server integration with the CDL Common Framework. Using SOAP and XML to access Metalib LITA National Forum, October 1, 2005 Michael McKenna, CDL michael.mckenna@ucop.edu. Overview: Metalib X-Server (/X). Currently supports basic services XML interface

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'X-Server integration with the CDL Common Framework' - affrica


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
x server integration with the cdl common framework

X-Server integration with the CDL Common Framework

Using SOAP and XML to access Metalib

LITA National Forum, October 1, 2005

Michael McKenna, CDL

michael.mckenna@ucop.edu

overview metalib x server x
Overview: Metalib X-Server (/X)
  • Currently supports basic services
    • XML interface
      • Modeled after Web Services (request/response)
    • Core interface to MetaLib
    • Data presentation in other application
      • E.g., a university portal or an institution’s courseware management system
x basic interface
(/X) Basic Interface
  • Login
  • User Authentication / User Affiliation
  • Retrieve Resources
  • Search Resources
  • Retrieve Search Status Report
  • Combine Result Sets
  • Retrieve Search Results
x upgrades
/V

Version 3.11 to 3.12?

196 files changed – for one instance (UCOP)

2,354 files changed – across all campuses

Upgrade script saves and marks changed files

“diff” and decide to keep changes or modify.

Merge to recreate prototype interface

/X

Does not touch our UI

May require modifications to Common Framework (CF) Manager Layer

Generally, existing CF functionality is left unchanged

(/X) Upgrades

/V = vanilla html interface /X = X-Server XML interface

x development methodology
/V

Cannot use CVS easily

Cannot see UI changes unless Metalib can see files

Cannot have unlimited Metalib instances

Be careful not to trash other’s work!

Keep close tabs on changes

Do regular file system backups

/X

Use CVS and Java IDE

Integrate with Common Framework development environment

(/X) Development Methodology

/V = vanilla html interface /X = X-Server XML interface

x development methodology1
/V

Example – to customize simple search, change all the following:

quick-1, quick-2-end, quick-3-body, quick-details, quick-1-body, quick-2-end.orig, quick-3-head, quick-details-info, quick-1-head, quick-2-head, quick-3-js, quick-full, quick-1-tail, quick-2-tail, quick-3-no-results, quick-help, quick-1-toolbar, quick-2-toolbar, quick-3-tail, quick-help-main, quick-1-toolbar-pd, quick-2-wait, quick-3-toolbar, quick-js, quick-2, quick-3, quick-8-body.spa, quick-main-help

/X

To brand or create new simple search, change only of the following:

search.jsp

(/X) Development Methodology

/V = vanilla html interface /X = X-Server XML interface

cdl common framework
CDL Common Framework
  • Integrated interfaced for (most) all University of California CDL managed information services
  • Based on Web Services
  • Packaged for internal use by UC libraries and departments
common framework web service layers
Common Framework Web Service Layers
  • User Interface
    • HTML, JSP, PHP, CSS, etc. as needed
    • STRUTS
  • Client Layer
    • Handlers that talk to the SOAP Service Layer
  • Service Layer
    • Interface, published as a SOAP Web Service (J2EE)
  • Manager Layer
    • Portability layer in front of Applications
  • Application Layer
    • Integrated information and repository systems
common framework web service layers1
Common Framework Web Service Layers
  • User Interface
    • HTML, JSP, PHP, CSS, etc. as needed
    • STRUTS
  • Client Layer
    • Handlers that talk to the SOAP Service Layer
  • Service Layer
    • Interface, published as a SOAP Web Service (J2EE)
  • Manager Layer
    • Portability layer in front of Applications
  • Application Layer
    • Integrated information and repository systems
x cf integration max
(/X) CF Integration (MAX)
  • Use existing modules as templates
    • Access Client –> Metasearch Client
    • Access Service -> Metasearch Service
    • Query Manager -> Metasearch Manager
  • New Modules
    • XTF / SRU
    • Struts or JSP layer -> User Interface
  • New interface
    • Metasearch Manager to Metalib
    • Metalib to XTF / SRU
x cf integration max1
(/X) CF Integration (MAX)
  • Use existing layers as templates
    • Access Client –> Metasearch Client
    • Access Service -> Metasearch Service
    • Query Manager -> Metasearch Manager
  • New Modules
    • XTF z39.50
    • Struts or JSP layer -> User Interface
  • New interface
    • Query Manager to Metalib
    • Metalib to XTF / SRU
x cf integration max2
(/X) CF Integration (MAX)
  • Use existing layers as templates
    • Access Client
    • Access Service
    • Query Manager
  • New Modules
    • XTF z39.50
    • Struts or JSP layer
  • New interface
    • Query Manager to Metalib
    • Metalib to XTFz39.50
max logic flow
MAX Logic Flow
  • Connect
  • Authorize Site

Find Resource

    • Find Resource
  • Search
    • Status
  • Results
x issues
/X Issues
  • Limited buffer sizes in ML /X
    • Being fixed by ExLibris using Apache for 3.13
  • Limited number of databases that can be searched
    • Same limits as MetaLib – communicate in ConnectService
    • Balance Speed vs. Coverage
  • Response time, time-outs
    • Communicate parameters in ConnectService
future
Future
  • Finish Metasearch Service implementation
  • Usability Study / UX Design
  • Write Client Layer / STRUTS
  • Write User Interface
  • Beta Roll-out
    • Fall/Winter 2005
  • New MetaLib /X ver., 3.14?
future1
Future

ExLibris New Discovery Web Services

  • New Metalib Web Services?
slide21

Thank you!

michael.mckenna@ucop.edu