ILS Interop

2010-03-04T20:19:18Z

67.121.146.131: /* Existing Efforts to Review */

<h1>Work from this group has been relocated to the [http://groups.google.com/group/ils-di/web/ils-interop-discussion-home ILS-DI Google Group]</h1>

A place to work on developing an infrastructure for interoperating between integrated library systems and other systems, but primarily discovery layers such as Blacklight, VUFind, Summon, WorldCat Local, SOPAC, Scriblio, and others.

* '''[http://groups.google.com/group/ils-di Group Mailing List]'''
* '''[[ILS_Interop_Mtg_Notes|Meeting Notes]]'''

== Existing Efforts to Review ==

* DLF ILS Discovery Interfaces (see below)
* [http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API Document Availability API] and [[DAIA_extensions|DAIA Extensions]]
* [http://www.jangle.org/ Jangle]
* [[Umlaut|Ümlaüt]]
* [http://www.extensiblecatalog.org/ XC NCIP and OAI Toolkits]

== DLF ILS Discovery Interfaces ==

This group worked to create a spec / recommendation for a set of functions that ILS systems would implement in order to support 3rd party discovery systems.

The work of this group is [http://www.diglib.org/architectures/ilsdi/ archived] on the DLF website ([http://www.diglib.org/architectures/ilsdi/DLF_ILS_Discovery_1.1.pdf final report]).

===List of functionality===
'''Level 1: Basic Discovery Interfaces'''<br />
This level represents a minimal set of functions that are easily implemented and essential to support applications that provide discovery outside the ILS.
* HarvestBibliographicRecords
* HarvestExpandedRecords (expanded records include bib, marc holdings, and item info)
* GetAvailability (for a single title or a list)
* GoToBibliographicRequestPage (basically the ability to link directly to an OPAC full record page)

'''Level 2: Elementary OPAC supplement'''<br />
This level describes a set of functions needed for a reasonably broad range of practical discovery applications that operate in tandem with the OPAC.
All of the above, plus
* HarvestAuthorityRecords
* HarvestHoldingsRecords (where 'holdings' generally refers to structured marc holdings as opposed to just item records)
* GetRecords (real-time via identifiers, as opposed to harvest)
* Search
* Scan (support browse)
* GetAuthorityRecords
* Either OutputRewritablePage or OutputIntermediateFormat

'''Level 3: Elementary OPAC alternative'''<br />
This level describes a set of functions needed for a practical discovery application that can operate completely independently of the OPAC.
All of the above, plus
* LookupPatron (I think this was going from a possible external identifier, like campus ID, to the internal ILS identifier)
* AuthenticatePatron
* GetPatronInfo (fines, holds, loans, recalls, messages, etc.)
* GetPatronStatus
* GetServices (services available for a particular item for a particular patron)
* RenewLoan
* HoldTitle
* HoldItem
* CancelHold
* RecallItem
* CancelRecall

'''Level 4: Robust/domain specific discovery platforms'''<br />
This level describes functions required to build useful discovery applications beyond the elementary level.
All of the above, plus
* SearchCourseReserves
* Explain (this is really a placeholder for an SRU type explain that says which functions have been implemented)
* Both OutputRewritablePage and OutputIntermediateFormat

== Existing Functionality ==
This section shows which systems are supported by which software packages. We should eventually build a chart; for now, we can start by listing details until we have a better idea of what standard entries belong in chart format.

=== VuFind ILS Drivers ===
The trunk VuFind drivers support various ILS's at different levels of detail. Some users have extended this through local customizations, but this list currently reflects only the baseline trunk code.
* Aleph - Item status, Patron details, Place holds (in progress in branch)
* Evergreen - Item status, New item list, Patron details, Suppressed record list
* Horizon - Item status, Patron details
* III - Item status
* Koha - Item status (incomplete)
* Unicorn - Item status; additional functionality may be available through the separate [http://code.google.com/p/vufind-unicorn/ VuFind Unicorn project].
* Virtua - Course reserves, Item status, Patron details, Place holds, Renew items
* Voyager - Course reserves, Item status, New item list, Patron details, Place holds (in progress in branch), Suppressed record list

23-02-2010 Mtg Notes

2010-03-02T01:19:01Z

67.121.146.131:

'''Action Item Notes from Code4Lib 2010 Meetings 23 and 24 February 2010, Asheville, NC on ILS Interoperability'''

Attendees: Ross Singer, Andrew Nagy, Bess Sadler, Naomi Dushay, Terry Reese, Jill Sexton, Emily Lynema, Demian Katz, Jennifer Bowen, Karen Coombs, Godmar Back, Roy Tennant

Goal: To collaboratively develop a middleware infrastructure for enabling discovery layers such as Blacklight, VUFind, Summon, WorldCat Local, SOPAC, Scriblio, etc. to interoperate with integrated library systems to accomplish specific functions (e.g., discover if an item is checked out, place a hold, etc.).

Action Items:

1) Roy will circulate action item notes to the group. [We should all also forward these to potentially interested parties not at this meeting]

2) Emily offered up the DLF ILS Interoperability list as the mailing list for this group. It is at <http://groups.google.com/group/ils-di> [ignore the description for now]. All participants should join this group.

3) Roy twill create a wiki page for the group on the Code4Lib wiki. This is now available at: <http://wiki.code4lib.org/index.php/ILS_Interop>. Please feel free to add to or edit this page and related pages. There is a link to this page from <http://wiki.code4lib.org/> under the “Interest Group” heading

4) We will all work on building a "to do" list on the wiki page noted above and assign relative priorities and assign responsibility.

5) To move the work of the group forward, Roy and Karen will schedule a regular series of conference calls using OCLC's toll-free conference call system.

6) Emily will provide a list of potential functions on the wiki based on her DLF ILS TF work.

7) Everyone will collaborate on creating a chart of ILS systems of interest and what connectors already exist for specific systems (e.g., VUFind, Blacklight, etc.) and what those connectors are capable of (e.g., retrieve circ info, place a hold, etc.).

8) One of the first "to do" items will need to be a review of the various strengths and weaknesses of using either Jangle or XC's NCIP toolkit or some third choice for developing this infrastructure.

9) Tim Shearer will send around information on the NISO group that he suggested might provide a suitable "home" for this group, noting that NISO can foster "interest group" kinds of activities without imposing the full requirements of a standards process until those are required.

Code4Lib - User contributions [en]

ILS Interop

23-02-2010 Mtg Notes