Library Software Development Specialist
Falvey Library, Villanova University
This position reports to the Technology Management Team and is responsible for
designing, developing, testing and deploying new technology methods, tools and
resources to extend and enhance digitally-mediated or
Roy, WRT I have a right to the API if I've bought the product, would
it be useful to add, maybe as a subpoint, I have a right to implement
the API in an open source product even if I've signed an NDA dealing
with that API? I understand vendor's (perceived) need for non
disclosure statements, but
Roy,
While your rights are interesting, the consumer responsibilities I find are
actually more important (and always more difficult to see followed). As some
that develops software for wide public consumption (read, not developers but
the computer illiterate in many cases), I find that
Hmmm, I'm tempted to add something to responsibilities along the lines of Seek
to understand the priorities of the software developers. Similar to
requesting features responsibly. I can see an important difference.
Sometimes it's important to let people know of a desired feature, even if in
On 11/6/07 10:27 AM, Jonathan Gorman [EMAIL PROTECTED] wrote:
How about an equivalent list from the vendor/software developer's perspective?
I think that would help balance the picture, but perhaps that's already in
your plans ;).
Funny you should ask...I had originally intended to do this,
Vendors need to guarantee that software development and support is not a
factor of the software's life-cycle. Too many library systems products
are being under supported presumably because the products are no longer
generating new revenue for the vendor. I don't know how that fits into
your
I think this depends entirely on what type of developer we are talking
about. Let's say it is a large ILS vendor who promises that their
software will do all things for all types of library. When a promised
feature or a discovered bug that only applies to a small subset of their
customer base
some ideas for vendor's responsibilities:
1) Care for the software as a whole. This means sometimes not giving what your
customers what in the short term to make a better product in the long term.
2) Care about the end user, despite whoever your customers are. Frequently
they're not the same.
Hi Roy,
Not sure how to make this succinct enough to be elegant (i.e. a bullet
point) but...
We have a large enough staff to break into software when necessary. A
typical scenario is:
We need a feature added (or bug removed) to make workflow tenable
We request the feature (bug fix)
We hear
I'm willing to jump in here as a long time vendor to add to the
customer responsibility list some items that would make developers/
vendors a lot happier..
1. Select software using a fair and reasonable process for both the
vendor and the organization (one could say a lot more here!)
2.
Original message
Date: Tue, 6 Nov 2007 14:16:05 -0500
From: Tim McGeary [EMAIL PROTECTED]
Subject: Re: [CODE4LIB] Library Software Manifesto
To: CODE4LIB@listserv.nd.edu
I think this depends entirely on what type of developer we are talking
about. Let's say it is a large ILS vendor who
11 matches
Mail list logo
