Hey, Jangle *has* an ILS-DI interface! It just has the option of
supplying other interfaces, as well.
It supports all of "Level 1" except for HarvestExpandedRecords (I just
haven't gotten to it, yet, since I've learned what it means).
http://groups.google.com/group/ils-di/browse_thread/thread/71d78edc0c800f27
-Ross.
On Thu, Jul 17, 2008 at 2:47 PM, Emily Lynema <[log in to unmask]> wrote:
> David,
>
> 2 email lists that you can start with, although neither one of them is
> truly a place to discuss implementation issues.
>
> 1. The ILS-DI discussion list on google. See
> http://groups.google.com/group/ils-di.
>
> I created this group to foment discussion surrounding the technical
> recommendation being developed by DLF's ILS Discovery Interface Task Group
> (now published on the DLF site). We have not had a lot of technical
> discussion on this list in the past, but we certainly could.
>
> 2. The jangle-discuss discussion list on google. See
> http://groups.google.com/group/jangle-discuss
>
> There's lots of technical discussion going on on this list. Jangle is really
> not an implementation of ILS-DI, but they are interested in using ILS-DI
> connectors to the local ILSs. It's an interesting conversation, regardless.
> Personally, I'd like to see Jangle *be* an implementation of ILS-DI, but I
> know Ross wants to have a little more freedom to develop a uniform
> interface.
>
> -emily
>
> Walker, David wrote:
>>
>> Hi all,
>>
>> I'm working on converting a screen-scraping class, written in PHP, I have
>> for looking-up bib and availability information in an Innovative systems to
>> the new ILS-DI specification, and had a couple of questions:
>>
>> 1. Is there a place (other than the workshop) to discuss issues or
>> questions I might have? A listserv perhaps?
>>
>> 2. Is anyone else thinking about, or currently working on, an
>> implementation for Innovative?
>>
>> Since the company has not agreed to work with the library community on
>> this, we're kind of on our own. I've got a pretty good scraper that can
>> accommodate most of the abstract functions in the spec. But wanted to see
>> if others did too, so we might combine efforts.
>>
>> Thanks!
>>
>> --Dave
>>
>> ==================
>> David Walker
>> Library Web Services Manager
>> California State University
>> http://xerxes.calstate.edu
>> ________________________________________
>> From: Code for Libraries [[log in to unmask]] On Behalf Of Emily
>> Lynema [[log in to unmask]]
>> Sent: Thursday, July 10, 2008 9:22 PM
>> To: [log in to unmask]
>> Subject: [CODE4LIB] Update: DLF ILS-DI Developers' Workshop Aug 7
>>
>> Now that the DLF technical recommendation is officially published [1], DLF
>> is trying to help maintain momentum and build a community of
>> implementation
>> around this project. Toward that end, an ILS-DI Developers' Workshop has
>> been organized in August for folks to hash out questions and answers about
>> implementing the first level of the recommendation, Basic Discovery
>> Interfaces. While this meeting is invitation only to keep the size down,
>> feel free to let me know if you are involved in this type of
>> implementation
>> and think you could contribute to this meeting.
>>
>> Of course, a summary of the outcome of the meeting will be made available
>> in
>> its aftermath. It is even possible there may be some suggested revisions
>> or
>> clarifications to the recommendation as we actually begin to write code.
>>
>> I've included the text of the original inviitation below for all to see.
>> We
>> hope to keep this topic of APIs and interoperability for our integrated
>> library systems fresh on your mind, especially as some many of you are
>> building these types of APIs literally as we speak....
>>
>> -emily lynema
>>
>> [1] http://diglib.org/architectures/ilsdi/
>>
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> Greetings -
>>
>> As you may know, the Digital Library Federation has released
>> the technical recommendation of its ILS Discovery Interface
>> (ILS-DI) Task Group. This document recommends basic, standard
>> interfaces -- known as the Berkeley Accord -- for integrating
>> the data and services of integrated library systems (ILS) with
>> new applications supporting user discovery. The documentation
>> is available at : http://diglib.org/architectures/ilsdi/ .
>>
>> The basic discovery interfaces permit libraries to deploy new
>> discovery services to meet ever-growing user expectations in
>> the Web 2.0 era, take full advantage of advanced ILS data
>> management and services, and encourage a strong, innovative
>> community and marketplace in next-generation library management
>> and discovery applications.
>>
>> DLF is planning a developer's workshop for Thursday, August 7,
>> at the Berkeley Faculty Club on the UC Berkeley campus, in
>> which parties supporting the Basic Discovery Interfaces can
>> learn more about the interfaces and how they should be
>> implemented, meet with potential development partners, and
>> begin the formation of a community building effective software
>> services. Because of the nature of this meeting, we recommend
>> that staff with a high degree of technical knowledge of your
>> platform and bibliographic standards and protocols receive
>> priority for attendance.
>>
>> The Berkeley Accord and the DLF ILS-DI recommendation are
>> important first steps in building advanced, interoperable
>> architectures for bibliographic discovery and use in the
>> networked world.
>
> --
> Emily Lynema
> Systems Librarian for Digital Projects
> Information Technology, NCSU Libraries
> 919-513-8031
> [log in to unmask]
>
|