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 2011

CODE4LIB April 2011

Subject:

Re: distributed library alpha server up, feedback welcome

From:

Gabriel Farrell <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 25 Apr 2011 00:55:46 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (108 lines)

The distributed library, where all patrons are both lenders and
borrowers, is an intriguing concept, and it's great that you have a
rudimentary system up to experiment with it. Aside from the unusual
requirements of a distributed library, you have one thing which
separates you from the masses of small libraries who set up systems
for their resources: you're not using MS Access. I applaud your
decision to build a webapp, though some might call this overkill. As
long as your patrons are able to use the system, and you're having fun
with the challenge, charge on ahead.

I have a few questions and comments.

I see you're storing only the title and location of each book in the
Django database, and tying into MarcEdit for the rest of the record. I
assume you're using MarcEdit for the Z39.50 client and the editing
interface, but you might want to look into exporting the records from
MarcEdit (as MARCXML, most likely) and ingesting them into the webapp
database. Keeping the two databases in sync and communicating with
each hit, especially once the webapp is on its own server, could
become difficult. Also, you may want to allow for remote cataloging at
some point. If you're really feeling adventurous, you might look into
wrapping PyZ3950 into a cataloging app.

I agree that a collection of that size doesn't warrant a search engine
like Solr. Some icontains queries are probably enough if browsing
alone doesn't suffice.

Most circ apps don't display the history of patrons who have checked
out an item, or a patron's history of checked-out items, for privacy
reasons. Some even drop those records from the database, or anonymize
them.

Another thing that differentiates you from other small libraries
attempting this sort of thing is your contacting of this list. Most of
the readers here are used to big-data problems, where they're trying
to make sense of the storage, maintenance, and display of millions of
records, so it's a bit of work to scale the mind down to a situation
such as yours. Also, most of us spend much of our time working around
legacy systems, so the troubles of a small, young app are both foreign
and envied. That's my way of explaining why you might not get much
response here.

And for heaven's sake, point a subdomain or something at that machine.
No reason to pass around IP addresses in this day and age.


On Sat, Apr 23, 2011 at 5:27 PM, Elliot Hallmark <[log in to unmask]> wrote:
> All,
>
> It was at the end of last year that I came here saying I was writing an open
> source ILS for a distributed (book sharing) library.  While I had lots of
> enthusiasm and time for it at the time, our development computer didn't have
> the capacity to run a solr based discovery front end.  Even though the back
> end was ready for feedback (though still very alpha), I dallied in posting
> the IP because there was no discovery layer.
>
> In the interest of moving forward, and since a complex discovery layer may
> not be necessary for a while (not for < 100 books), here is the IP.  Please
> check it out and give feed back.  Play around with whatever, this data isn't
> real.
>
> http://72.48.75.76
>
> If this IP changes, I'll let y'all know on this thread.
>
> Soon I would like to use this system at our private alternative
> school<http://www.clearviewsudburyschool.org>in hopes that it would
> facilitate folks letting us use their excellent
> books, since they would be lending them, not donating them.  Having a
> database keeping track of who owns the books would give a little peace of
> mind.  in the future, setting up a network of libraries would be easy.
>
> notes:
>
> 1. This is a distributed library, where a book enters the system through a
> primal loan (from owner to library), and is due back at some point.  The
> book or item can be further lent to a regular borrower, or to another
> library (which inherits lending privilages).  extending lending privilages
> must be done through the administrative back end, so it wouldn't happen
> accidentally.
>
> 2. The "discovery layer" is severely crippled because I don't want to write
> a indexer for our MARC records unless it becomes necessary (ie, better
> searching is needed but writing a VuFind driver or integrating with Kochief
> isn't yet feasible).  All books entered in this system also have MARC
> records associated with them, so a solr or other front end can be added
> later.
>
> 3. If you'd like to try uploading a MARC record, email it to me and I'll put
> it up for anyone to enter through the cataloging app.
>
> 4. This is written in django.  Hooray for python!
>
> 5. This is not at all perfect yet.  here is my todolist so far (please add
> to it):
>
> when checking a book out, do not allow a due date later than the current
> lease on the book.
> subtitle, does this really need to be limited to 100 characters?
> create an end of day script that:
>   sends emails to books that are due back soon
>   sends emails to books that are overdue
> activate fines model and add an Fine.calcuate() method
> make a legit zipcode field. current one accepts <5 digits
>
> thanks for reading,
> Elliot
>

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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
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