You may wish to give a try to J-ISIS
With J-ISIS, you can create a searchable database with a couple of clicks.
It uses Berkeley Database as persistence manager and Lucene for indexing
The user can concentrate on the domain and to what he want to achieve. No
need to be an expert in relational dabases and SQL. Furthermore, you get
suggestions of term indexed when making a particular query.
Web-JISIS is a web application prototype that allows to browse and search
I can help if you need.
On Sat, Apr 16, 2016 at 2:07 AM, Matt Sherman <[log in to unmask]>
> Well, we've got one volume done, with about 1,250 bibliographies, but there
> are 3 other volumes to convert. So at the end of the day probably about
> 5,000 entries. Though the how is to make it intractable via the web and
> hopefully letting scholars in the field continue to add to the database
> once it is online.
> On Fri, Apr 15, 2016 at 7:38 PM, Kyle Banerjee <[log in to unmask]>
> > On Fri, Apr 15, 2016 at 11:53 AM, Roy Tennant <[log in to unmask]>
> > wrote:
> > > In my experience, for a number of use cases, including possibly this
> > > a database is overkill. Often, flat files in a directory system indexed
> > by
> > > something like Solr is plenty and you avoid the inevitable headaches of
> > > being a database administrator. Backup, for example, is a snap and
> > > automated.
> > >
> > I'm with Roy -- no need to use a chain saw to cut butter.
> > Out of curiosity, since the use case is an annotated bibliography, how
> > stuff do you have? If you have only a few thousand entries in delimited
> > text, flat files could be easier and more effective than other options.
> > kyle
[log in to unmask]