Your SlideShare is downloading. ×
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
DLF ILS Discovery Interface Task Force API recommendation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

DLF ILS Discovery Interface Task Force API recommendation

1,719

Published on

The DLF ILS Discovery Interface Task Force was charged with creating a technical proposal that would provide standardized integration between integrated library systems and external applications, …

The DLF ILS Discovery Interface Task Force was charged with creating a technical proposal that would provide standardized integration between integrated library systems and external applications, better enabling libraries to replace their OPAC with an external discovery system. This talk would provide background for the project and an overview of the recommendation (hopefully published by code4lib 2008), as well as address how the library developer community can contribute to API implementation. More information and current work on the recommendation are available: https://project.library.upenn.edu/confluence/display/ilsapi/Home. A breakout session could facilitate further feedback and discussion of next steps.

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,719
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
16
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. Opening the ILS for Discovery DLF ILS Discovery Interface Task Force API Recommendation Emily Lynema Terry Reese code4lib February 27, 2008
    • 2. Background
      • ILS is a monolithic, centralized system
      • Patron discovery and delivery is becoming more de-centralized
      • The ILS can no longer do *everything* well
      • We need better tools for integration
        • Our focus: Patron discovery, from search to use
          • Finding relevant resources (discovery)
          • Acquiring them (delivery)
          • Managing their usage (patron info and account)
    • 3. Charge
      • Convened summer 2007 by DLF
      • Analyze: problems integrating ILS with external discovery applications
      • Create: technical recommendation for improving integration
      • What will be the outcome?
        • An idea, not a product or implementation
        • You can help build the implementations!!
    • 4. Membership
      • John Mark Ockerbloom, Penn (chair)
      • Terry Reese, Oregon State
      • Patricia Martin, California Digital Library
      • Emily Lynema, NC State
      • Todd Grappone, Univ. of Southern California
      • Dave Kennedy, Univ. of Maryland
      • David Bucknum, Library of Congress
      • Dianne McCutcheon, National Library of Medicine
    • 5. Functions & bindings
      • Improve integration by specifying set of functions (API)
      • Abstract functions
        • Functionality, inputs, outputs
      • Possible bindings for implementation
        • Suggest possible technology
      • Encourage use of non-library standards
    • 6. Core vs. Expanded
      • Specify functions most important for immediate implementation [by vendors]
      • 3 usage profiles
        • Minimum for OPAC supplement (enhanced discovery)
        • Minimum for OPAC alternative (replaced discovery + delivery)
        • Robust discovery platform (would be nice)
    • 7. Data aggregation
      • Bulk harvesting for external apps that maintain local indexes
        • Incremental harvesting by date added / last updated
      • HarvestBibliographicRecords
      • HarvestHoldingsRecords
      • HarvestExpandedRecords
      • HarvestAuthorityRecords
    • 8. Real time search
      • On the fly access to real time data
      • On the fly lookup of original record
      • Federated real time searching
      • Searching
        • Search
        • Scan
        • SearchCourseReserves
      • Identifer lookup
        • GetAvailability
        • GetRecords
        • GetAuthorityRecords
    • 9. Patron functionality
      • Patron authentication and account information
      • Delivery functionality as managed by the ILS
      • Patron Account
        • LookupPatron
        • AuthenticatePatron
        • GetPatronInfo
        • GetPatronStatus
        • RenewLoan
      • Delivery
        • HoldTitle
        • HoldItem
        • CancelHold
        • RecallItem
        • CancelRecall
    • 10. OPAC embed / escape
      • Support rewriting OPAC displays to include external content / services
      • Support output transformation of OPAC displays for use outside of ILS
      • Possible behaviors:
        • OutputRewritablePage
        • OutputIntermediateFormat
    • 11. Where do we go from here?
      • Now soliciting feedback: vendors + library community
      • Finalize draft (spring 2008)
      • Make recommendations to DLF
        • What happens next?
        • What will be needed to maintain recommendations?
        • How will they be implemented?
    • 12. How can I participate?
      • Read draft and send feedback:
        • [email_address]
      • Join the conversation:
        • Breakout session today @ 2:40
        • http://groups.google.com/group/ils-di
      • Contribute code
        • Work with existing efforts (VuFind, XC) to build open source connector implementations
        • Implement as part of your open source ILS
        • Encourage ILS vendors to implement
    • 13. Full draft recommendation
      • Most up to date on wiki
        • http://tinyurl.com/262xqn
        • or just search dlf ils wiki
        • can post comments there, as well
      • Available as Word document
        • attachment is in left nav bar on wiki

    ×