LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2008

CODE4LIB April 2008

Subject:

Re: [ils-di] DLF ILS Discovery Interface recommendations and community participation

From:

Ross Singer <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 7 Apr 2008 18:55:21 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (129 lines)

Emily,

Actually, thanks for cross-pollinating this to all three lists, since
I think it directly affects all three groups.

I think one of the questions that would help guide this discussion is
knowing a little more about the future of the DLF API and the role
that the task force will have in it.  You mention that the group
doesn't feel comfortable with trying to implement, but obviously they
have a stake in making sure it doesn't just fall by the wayside,
forgotten.  What, exactly, does "success" mean to the task force and
what are the plans of achieving that?  Would the ideal be to release a
more formal recommendation and hope something adopts that and
continues development?  Or would it continue to evolve independently
of other initiatives and what kind of group *should* be shepherding
that?

As far as where the development lives, I can make arguments for both
wiki.code4lib.org and jangle.org; both have advantages and
disadvantages.

I couldn't imagine people objecting to this being hosted on
wiki.code4lib.org, it's certainly not out of scope to what people are
working on there.  That being said, wiki.code4lib.org will probably
always be a hodge-podge of content from a variety of different
initiatives; most of which would have nothing to do with the DLF API.
That might be a little disconcerting to uninitiated.  It's a good
project-neutral location, however.

On the flip side, Jangle is using the DLF API as the use case to guide
the initial development.  At first blush it would seem as though it
makes sense combine the two (there will certainly be need for
communication and coordination); however, Jangle and the DLF API are
not a 1:1 match.  Jangle (at least in the current vision) wouldn't
directly supply the DLF API and it would need to be made clear that
the DLF API could be implemented *without implementing Jangle* (which,
again, might be confusing to the uninitiated).  Since both of these
projects are really working for the same eventual outcome ("help me
free my data"), there is something to be said for them being under the
same umbrella.

Regarding your other question, the hosting of this code, I think,
again, either place could work.  What we're really talking about a
registry (code for SD Unicorn, EL Aleph, Koha, etc.) with either file
attachments or contact information on how to download it (if, for
instance, it's protected by an NDA).

-Ross.

On Mon, Apr 7, 2008 at 5:59 PM, Emily Lynema <[log in to unmask]> wrote:
>
>  Many apologies for the cross-posting, but I wanted to make sure all the
>  involved parties were fully represented.
>
>  I have 2 questions that relate to the work of the ILS Discovery
>  Interface Task Force [1], the work of the jangle community [2], and the
>  code4lib community in general.
>
>  1. At the Discovery Interface Task Force breakout session at code4lib,
>  there were many folks interested in moving beyond the abstract DLF
>  recommendation document [3] to more detailed function specifications
>  that could actually be implemented with specific technologies and
>  metadata formats. While we'd love to be able to fully specify a single
>  uniform API specification, those of us on the DLF group feel we lack the
>  time, resources, nor expertise to do this without community input.
>
>  The idea of providing a wiki where anyone could contribute ideas about
>  implementing the recommended functionality (which would hopefully evolve
>  into best practices over time) was well received at code4lib. However,
>  DLF doesn't have an openly available wiki and may not be shepherding
>  this work in the future. Code4lib.org *does* have an openly available wiki.
>
>  At the same time, I see a lot of interest going into an API
>  specification for jangle. I think these projects could work together on
>  defining metadata formats and schemas that support the DLF
>  functionality. But I don't know if the jangle specification will provide
>  a direct mapping to the functions in the DLF recommendation. Jangle
>  already has an open wiki hosted by Google Code (and a Drupal installation).
>
>  In the spirit of democratic openness, I wanted to poll the community.
>  Does it make sense to start a space on the code4lib.org wiki regarding
>  implementation of the DLF recommendation? Is that an acceptable use of
>  the wiki? Or does it make more sense to point to the jangle wiki as a
>  place for discussion?
>
>  2. During the code4lib breakout session, we also discussed creating a
>  wiki where library developers could share their past work to access data
>  stored in the ILS (ex: I've written a function that retrieves live
>  holdings in SirsiDynix, I've written a function that places a hold in
>  Innovative, etc.). We would hope to move toward a point where the code
>  could actually be posted and shared in an open source fashion (no one
>  really knows about NDAs yet). Is this an acceptable use of the code4lib
>  wiki? Google Code makes sense for posting code, but seems like overkill
>  if all you need is a wiki.
>
>  Please let me know if you have any input or suggestions.
>  Thanks!
>
>  -emily lynema
>
>  [1] https://project.library.upenn.edu/confluence/display/ilsapi/Home
>
>  [2] http://jangle.org - community-driven, open source project to create
>  a uniform API specification across all ILS products as well as code for
>  individual connectors for each individual ILS system to implement that
>  API. Jangle could serve as a reference implementation / binding for the
>  DLF recommendations, or the recommended DLF functions could be
>  implemented on top of Jangle and its system connectors.
>
>  [3] For the Feb. 15 draft, see
>  Wiki:
>  https://project.library.upenn.edu/confluence/display/ilsapi/Draft+Recommendation
>  Word: http://tinyurl.com/2bzrje
>
>  --
>  Emily Lynema
>  Systems Librarian for Digital Projects
>  Information Technology, NCSU Libraries
>  919-513-8031
>  [log in to unmask]
>
>  --~--~---------~--~----~------------~-------~--~----~
>  You received this message because you are subscribed to the Google Groups "ILS Discovery Interface Task Force" group.
>  To post to this group, send email to [log in to unmask]
>  To unsubscribe from this group, send email to [log in to unmask]
>  For more options, visit this group at http://groups.google.com/group/ils-di?hl=en
>  -~----------~----~----~----~------~----~------~--~---
>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager