> > (By the way, I didn't actually get this email, someone let me know
> > about it
> > -- anyone else sporadically getting code4lib emails?)
> >
> > -b
> >
> > ---
> > Birkin James Diana
> > Programmer, Integrated Technology Services Brown University Library
> > [EMAIL PROTECTED]
> >
Most of them
Hi, Phil.
We use Fedora Commons at University of Virginia, and we're in the
process of rolling out Blacklight as our front end. You can see an
example of it at http://blacklight.betech.virginia.edu. This allows
us to maintain a single index containing all of our bibliographic
holdings fro
Ah... thanks Birkin, good idea. I'll take a look.
Kevin
On Tue, Oct 28, 2008 at 4:29 PM, Birkin James Diana
<[EMAIL PROTECTED]> wrote:
> Kevin,
>
>> What is this Birkin hack of which you speak? I've been wondering how all
>> these recent pieces are getting tied back to the main code4lib site..
Kevin,
What is this Birkin hack of which you speak? I've been wondering how
all these recent pieces are getting tied back to the main code4lib
site...
For the login for , I came
up with some python code (for the django app) that takes a submitted
username and password and posts them to
Last week I gave a presentation at the TDWG 2008 meeting in Fremantle,
Western Australia, titled "Using Fedora Commons To Create A Persistent
Archive"
http://www.slideshare.net/phil.cryer/using-fedora-commons-to-create-a-persistent-archive-presentation
It was well received, and think it has plent
What is this Birkin hack of which you speak? I've been wondering how
all these recent pieces are getting tied back to the main code4lib
site. It would be nice to make appalachia.code4lib.org hook in rather
than use it's own passwords.
Also, looking on appalachia.code4lib.org I see we have nine f
I strongly suggest moving the URL and then putting it in robots.txt.
You can keep it open and link to it as much as you want, but if
spammers can't search for boilerplate wiki phrases in Google, they'll
never find it. Of course, nobody else will be able to find it
either...
That worked for us for
Our wiki page got clobbered by a spambot because I never got around to
password protecting it. lbjay--
So I've slapped an http basic auth challenge in front of it for the
time being. The user/pass is code4lib/code4lib. Hopefully that will be
enough to thwart the bots for a little while. Maybe we c
