libdb-develop

[libdb-develop] modularizing schema?

[Bruce D'A. <bd...@fa...>]

Things are quiet here.  Looking at the SQL schema again, is it possible 
to break out the genre/media-specific content into separate files?  A 
lot of the bulk of the schema is just stuff specific to people 
cataloguing movies, and I don't want most of that stuff in my db if I'm 
interested in texts instead.

Perhaps then I could have a file for marc relator terms.

Same with concepts.

Also, Morbus, if you can find time sometime, could you please show what 
an SQL record example (maybe by adding to the mysql_sample.sql file) 
would look like for a magazine article?  It might help me wrap my head 
around how it should work (where to put the page and volume numbers, 
etc.).

Bruce

Re: [libdb-develop] modularizing schema?

[Morbus I. <mo...@di...>]

> Things are quiet here.  Looking at the SQL schema again, is it possible 
> to break out the genre/media-specific content into separate files?  A 
> lot of the bulk of the schema is just stuff specific to people 
> cataloguing movies, and I don't want most of that stuff in my db if I'm 

The FRBR spec contains numerous suggested fields for books, serials, and 
audio materials, but I've not included those in the actual tables, as 
you know, because they wouldn't have actually been used (for my initial 
purposes, etc.). But, "genre" in LibDB is being handled with the 
"concept" table, which is a Group 3 entity in FRBR. The plan, once 
movies were "done", was to simply add the media-specific fields to the 
relevant tables (page numbers to manifestations, etc.).

Unfortunatley, I'm not sure what is going on with LibDB anymore. I've 
had no time to work on it, and the company that I /was/ working on this 
for has gone with a "quick" alternative that I set up in a few hours 
(for the probably-live-next-week demo, see http://cinema93.com/movies). 
Unfortunately, this "quick" alternative was a "just get it done for the 
mundanes and the non-libtechs", so it has very little merit for those 
interested in the original goal of LibDB.

With that said, and with that company no longer "bugging" me to get 
something done, I'm not sure I'll have "time" to work on LibDB for a 
very long time, if at all. The original impetus is gone, there are other 
projects that are taking up a lot of my effort and, though there was a 
lot of interest in the Drupal world for it, there were no additional 
developers who had the libtech knowledge to do it "right".

-- 
Morbus Iff ( anything else in the box, pandora? )
Technical: http://www.oreillynet.com/pub/au/779
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus

Re: [libdb-develop] modularizing schema?

[Bruce D'A. <bd...@fa...>]

On Feb 19, 2005, at 12:59 PM, Morbus Iff wrote:

> The FRBR spec contains numerous suggested fields for books, serials, 
> and audio materials, but I've not included those in the actual tables, 
> as you know, because they wouldn't have actually been used (for my 
> initial purposes, etc.). But, "genre" in LibDB is being handled with 
> the "concept" table, which is a Group 3 entity in FRBR. The plan, once 
> movies were "done", was to simply add the media-specific fields to the 
> relevant tables (page numbers to manifestations, etc.).

Is it technically possible to do as I was suggesting though?  To have 
that community-specific content broken out in to separate files?

> With that said, and with that company no longer "bugging" me to get 
> something done, I'm not sure I'll have "time" to work on LibDB for a 
> very long time, if at all. The original impetus is gone, there are 
> other projects that are taking up a lot of my effort and, though there 
> was a lot of interest in the Drupal world for it, there were no 
> additional developers who had the libtech knowledge to do it "right".

I guess that's the way things go.  I do think it would be valuable -- 
if you can find a bit of time -- to consider the above, so that the 
core schema just represented the logic.  If someone comes along wanting 
to do this sort of project (maybe me in a year or two), then I could 
just point 'em to the schema.  There's are probably 50 LAMP bib 
projects out there, almost all of which start and end with bibtex.  I'd 
love to give them a ready-made alternative.

Bruce