Displaying Availability data using Juice

[Owen]

Has anyone done any work with Juice to enable the retrieval and
display of availability information for an item via a standard
mechanism? Eg DLF ILS-DI or similar?

--
You received this message because you are subscribed to the Google Groups "juice-project-discuss" group.
To post to this group, send email to juice-proj...@googlegroups.com.
To unsubscribe from this group, send email to juice-project-di...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/juice-project-discuss?hl=en.

[Richard Wallis]

Hi Owen,

Not sure exactly what you are after here.

Do you mean, are there any extensions that go off to other systems [which expose a DLF style API] and bring back information to enrich the display?  - In which case the answer is currently no - some of the currently published extensions do bring back results from other systems (eg. Google Book Search) and embed them in the local display, so it wouldn't be a major leap to do this for systems using DLF compliant APIs.

Or do you mean, has Juice been used to enable the local OPAC to behave as a DLF compliant API?  Again the answer is no, but more because this isn't what Juice is targeted at doing.  Juice is about extending a user interface, not changing its core behaviour.    I would suggest the OS Jangle project (http://www.jangle.org/) which is a generic framework approach to delivering (DLF ILS-DI and beyond) API access to all library systems.  The architecture builds on library system specific connectors, plugging in to a standard API service layer.

Richard.

Richard Wallis

Technology Evangelist, Talis

Tel: +44 (0)870 400 5422 (Direct)

Tel: +44 (0)870 400 5000 (Switchboard)

Tel: +44 (0)7767 886 005 (Mobile)

Fax: +44 (0)870 400 5001 

Linkedin: http://www.linkedin.com/in/richardwallis

Skype: richard.wallis1

Twitter: @rjw

IM: rjw...@hotmail.com

---

Please consider the environment before printing this email.

Find out more about Talis at http://www.talis.com/
shared innovation™

Any views or personal opinions expressed within this email may not be those of Talis Information Ltd or its employees. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.

Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.

[Owen]

Hi Richard,

Thanks for this reply. I mean the former - go off to other systems
which expose a DLF style API (or similar) and bring back information
to enrich the display.

Thanks,

Owen

[sieh...@googlemail.com]

Hi Owen,

You wrote:

> Has anyone done any work with Juice to enable the retrieval and
> display of availability information for an item via a standard

> mechanism? Eg DLF ILS-DI or similar? [...] go off to other systems

> which expose a DLF style API (or similar) and bring back information
> to enrich the display.

What do you mean by "availability information for an item"? You can
express some availability information in DLF-DI or in DAIA (see
http://daia.sourceforge.net/) - the latter is more detailed and can
losslessly be encoded in JSON but I have not written a JavaScript DAIA
client (which is what you seem to be looking for) yet. However most
library system do not provide availability information in DAIA or by
any other "standard mechanism". Instead of writing a JavaScript client
that knows how to talk with the specific library systems, I'd
recommend to create a DAIA wrapper and a DAIA client, but I must admit
that I am biased ;-)

If you can tell what you mean by "availability information for an
item" please let me know for instance at this mailing list
http://sourceforge.net/mailarchive/forum.php?forum_name=daia-devel so
we can add the missing features to DAIA.

Cheers
Jakob

P.S: Jonathan Rochkind gave an example of a dlf-ils-di response
including a very simple DAIA in it:
http://groups.google.com/group/ils-di/msg/652c731ad7f765ab

[Owen Stephens]

Thanks Jakob,

I was just doing a bit of investigation for a possible project (and DAIA was on my list as well as DLF-DI) - whether it goes ahead will depend on funding, so some of the detail is unlikely to emerge until then. I agree completely - we don't want to write custom code for different library systems, and the type of approach I was thinking of was along the lines you suggest. I do see one advantage to using DLF-DI - which is that I believe it has already been implemented by at least one library system vendor. However, as you note, since DAIA can be included in a DLF-DI response, using one doesn't negate the use of the other.

In terms of what type of information I'm thinking about I guess there are a few aspects - which you've already worked through for DAIA (using DAIA terminology):

Does the document exist within a library system/collection
If so, what items exist, how are they made available (DAIA presentation/loan/openaccess - although probably not interloan), and are they available now and if not, when will they be available in the future

However, what level of detail we supply might depend on the time available - for example we could start by extracting the simpleavailability and then move onto DAIA.

The idea of doing some of this with Juice is clearly that then this availability information could be added to any environment with Juice implemented - so assuming one or both of DFL-DI and DAIA get wider adoption, display of availability information would be easy to do - and it seems to be something several of the current set of 'NG' OPAC systems struggle with.

Hope this all makes sense

Owen