libdb-develop — Developer discussions and bickerings.

Re: [libdb-develop] Don't Look At This Demo

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

 >This raises a point: you're current UI works for videos on a shelf, but
 >I don't think it does for my examples (where the location is more fine
 >grained).  If I store an an online newspaper article record, I need to
 >have the complete uri, along with a date accessed.

Yeah, the current focus of LibDB is physical materials. I haven't
given digital material much thought, but you could do the following
in the current system and it'd work well enough (in fact, I'm jotting
down a note to include "URI" as a default annotation):

  * define a location called "Online" (or some such). locations
    are solely relationships: besides describing a location type,
    you can't add *per-item* metadata to them. but...

  * define an annotation called "URI". annotations are defined
    as relationships too, but you can add as many strings per
    annotation type per item as you want. they have nothing to
    do with locations, so ultimately, you could leave the location
    of an item blank, and just use the "URI" annotation.

With the above, you could have:

  Location Type: Online
  Annotation Type: URI

  Title: Online Newspaper Record
  Location: [Location Type: Online; no value, relationship only.]
  Annotation: [Annotation Type: URI; Value: "http://www.demo.com/"]
  Annotation: [Annotation Type: URI; Value: "http://www2.demo.com/"]
  Annotation: [Annotation Type: URI; Value: "http://bak.offsite.com/"]

Would that work for you?

 >So what is a location? Say I want to store a bunch of records from an
 >archival collection. So: ABC Archive, Collection X, Box 23, Folder 324
 >How does this fit in the model?

 From an "FRBR model" standpoint, it really doesn't. FRBR mentions that
an item is located somewhere, but it doesn't set out to conceptualize
"location" as anything but a relationship/attribute.


-- 
Morbus Iff ( i put the demon back in codemonkey )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus

Re: [libdb-develop] Don't Look At This Demo

[Bruce D'A. <da...@mu...>]

On Feb 20, 2004, at 12:31 AM, Morbus Iff wrote:

> Go ahead and add one, and you'll be told your changes have been
> saved, as well as given a chance to re-edit your changes or what
> have you. You'll also notice that all these edits and additions
> will apply to the "add_film" page above - once you're down fiddling
> with locations, reload the "add_film" page, and you should see your
> changes reflected in the "where is this item located" drop-down.

I just added a couple of examples that I could use: archival and online 
uri.

This raises a point: you're current UI works for videos on a shelf, but 
I don't think it does for my examples (where the location is more fine 
grained).  If I store an an online newspaper article record, I need to 
have the complete uri, along with a date accessed.

Bruce

Re: [libdb-develop] Don't Look At This Demo

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

Still plenty more to do (I've yet to address Bruce's Safari thing, and
I believe I've licked the mod_perl problems but have yet to implement
them), but another update of half-working code tonight.

The "add film" page hasn't changed in coding whatsoever:
http://disobey.com/noos/LibDB/dev/index.cgi?tmpl=add_film

But, I've started work on making "locations" actually do something
from a database integration point of view. You can see the list of
current locations here:

  http://disobey.com/noos/LibDB/dev/index.cgi?tmpl=locations

Nothing too surprising. That's the happy browsing interface.
The administrative interface, however, adds editing buttons:

  http://disobey.com/noos/LibDB/dev/admin.cgi?tmpl=locations

Clicking the little pencil icon thing will bring you to an
editing form, which actually works. You can go and edit existing
locations all you want, and you'll be informed of your success,
as well as be given the opportunity to re-edit your edits <g>.

I don't have a magic button (yet) for adding a new location,
but you can do that too at the following URL (slightly diff):

  http://disobey.com/noos/LibDB/dev/admin.cgi?tmpl=locations&edit=1

Go ahead and add one, and you'll be told your changes have been
saved, as well as given a chance to re-edit your changes or what
have you. You'll also notice that all these edits and additions
will apply to the "add_film" page above - once you're down fiddling
with locations, reload the "add_film" page, and you should see your
changes reflected in the "where is this item located" drop-down.

Still need to add a delete button too (though, that causes some
database integrity problems, so I may hold off on that for now).

-- 
Morbus Iff ( tomorrow never comes until it's too late )
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

[libdb-develop] LibDB and Administrative Access

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

I'm not a huge, huge fan of reinventing the wheel so, for the early
versions of LibDB, all administrative authentication will be handled
by the webserver itself. In other words: outta the box, anyone can
modify your LibDB database and it's up to you to secure it.

There are a few reasons for this:

 * I don't, currently, have the time to code a whole authentication
   layer, with user accounts, passwords, hashing, verification, blah
   blah blah. It's so much easier to let the webserver handle it.

 * I'm not a fan of cookies in my stuff. Cookies would be required if
   I were to do my own authentication; the only other alternatives would
   be un/pw in the URL (ahahaha), or some other cheap way of server
   side session management (flawed and exploitable).

 * Built-in security in a webserver is often far more
   secure than stuff people re-code in their scripts.

 * For demonstration purposes, I don't need to worry about wearisome
   instructions like "for the demo, enter 'this' as your username and
   'sucks' as your password".

 * Similarly, I don't have to worry about *implied* security. If I
   set a default username of "Admin" and a default password "Bob",
   I don't have to *trust* the user to change them. There's no grey
   area with webserver based security: you're either secured (on
   your own volition) or you're not (also on your volition).

With that in mind, an unsecured administrative script WILL spit
out errors: http://www.disobey.com/noos/LibDB/dev/admin.cgi. Of course,
the tip page it directs you too hasn't been written yet, but I'm
working on it! <g>

-- 
Morbus Iff ( i'd swear in japanese, but your email doesn't support UTF-8 )
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

[libdb-develop] Fwd: Identifiers Relate To Manifestations, Except When...

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

 >Date: Thu, 19 Feb 2004 18:56:37 -0500
 >To: fr...@in...
 >From: Morbus Iff <mo...@di...>
 >Subject: Identifiers Relate To Manifestations, Except When...
 >
 >In 99% of the cases I can think of, an identifier is related to a
 >manifestation. ISBNs, ISSNs, DOIs, UPC's, Amazon ASINs, etc., etc.
 >I haven't had any problem coming to this conclusion: identifiers
 >should relate to the physical manifestation of the expression.
 >
 >Except... when it comes to an IMDb identifier. Some of you will recognize
 >my pseudonym from previous discussions and questions about movies under
 >FRBR, and I've been largely silent because I'm coding like mad on the
 >LibDB project [1]. As I was working on the identifiers interface,
 >however, I realized that I'd like to include the IMDb identifier
 >for a particular movie.
 >
 >For example, here's a URL for a movie at
 >IMDB: http://imdb.com/title/tt0368296/.
 >The identifier is "tt0368296".
 >
 >But IMDb doesn't talk about physical manifestations of movies, it
 >talks about the movies themselves: in other words, the expression.
 >The IMDb identifier should be related to the expression.
 >
 >Does this make sense? How are other people handling identifiers?
 >Can anyone think of similar identifiers that are better to an
 >expression than a manifestation? If the IMDb identifier is a
 >rarity, then I think, for now, I'll just relate them to the
 >manifestation and jot a note down somewhere. If, however, people
 >can think of more instances where an expression is a better
 >relationship, I'll have to rethink some things.
 >
 >[1] http://disobey.com/noos/LibDB/

-- 
Morbus Iff ( think about the good things that I did for you )
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] Don't Look At This Demo

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

 >Note: on Safari at least, in general the text
 >rendering is coming across as rather ... large.

Odd. Could you screenshot it for me? I've ONLY been testing
the layout in Safari lately. Cross-browser stuff I always
check the next day (being today <g>).

 >BTW, how are you designing the underlying code that lays out the form?
 >Would be nice to start with a system designed to be easily modified by
 >users.  I'm no coder, but how about an xml template config file that
 >defines how each type of record would be presented?  That way later on
 >it's easier to add stuff other than films.

It's actually "just HTML" with movable snippets
of "code you don't have to understand".

   http://cvs.sf.net/viewcvs.py/libdb/LibDB/
     templates/default/en/add_film.html?rev=1.2&view=auto

That's the URL for the source code of the "add_film.html" file,
which is what's parsed when ?tmpl=add_film is sent to LibDB
(going through the paths, this is the "add_film" file for the
"en"glish version of the "default" "template". The name of the
template and the language of the user is determined automatically
by the internal code, so URLs need only to worry about the
name of the file, passed via "tmpl=").

As you can see, it's 99% HTML. Here's an explanation of the code
snippets you do see. All non-HTML code is encased in delimiters:

   [$    # this is the starting delimiter of "code is coming"

     # this is where code goes. code can print HTML too.

   $]    # this is the ending delimiter of "code is done!"

The simplest piece of code is getting the value of a setting.
The following line (well, something similar) is used to print
out the little "0.1.0" thing in the footer of each page:

   my $ver = LibDB::Settings->get("app_version")

As for other pieces of code, I've tried to keep them as "movable"
as possible, with no regard for what sort of media we're adding.
So, the following code, which displays the different "locations"
where an item can live, is the same regardless of whether we're
adding a movie, a book, a magazine, or what have you (note that
I've included lots of whitespace and commenting here for your
perusal: in the "add_film.html" file, it's just four lines):

  [$ # here's our delimiter. ie. "code is coming"

   # create an interface to the database, and
   # prepare a data structure ($results) to store
   # any results we receive.
   my $db = LibDB::DB->new; my $results;

   # connect to the database, and store a list
   # of all our possible locations into $results.
   # if this fails, we return an error message and
   # stop processing FOR THIS BLOCK OF CODE only.
   unless ($db->connect
     and ($results = $db->get_locations_types)) {
     $OUT .= '<p class="err">'.$db->error.'</p>'; return; }

   # if we're this far, then there were no database
   # errors, so we expect to have rows of results
   # stored in $results. we'll go through each result
   # and print out an HTML <option> tag for our <select>.
   foreach my $r (@$results) {
      $OUT .= "<option value=\"$r->{lt_id}\">
                $r->{lt_name}</option>"; }

  $] # our ending delimiter. no more code.

In your case, if you wanted to revise the "add_film.html" to
be book specific, you could run through the following steps
(assume, of course, that add_film.html would be a final
version, and not what I'm currently working on):

  a) copy "add_film.html" to "add_book.html".
  b) change the HTML to reflect books, not film.
  c) there is no step three.

There's no step three because you won't really have to change
any of the database/template *code* (code meaning Perl, not
HTML markup) to satisfy your needs. Ultimately, the distinction
between "film" or "book" or "comic" happens in the interface
only, and not in the underlying frameworks.

Thoughts?




-- 
Morbus Iff ( i put the demon back in codemonkey )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus

Re: [libdb-develop] Don't Look At This Demo

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

On Feb 18, 2004, at 9:36 PM, Morbus Iff wrote:

> This is SooOSoooOOoOo very eaaRRrRrLLlLy that I'm only mentioning it
> to certify that, yup, I'm still working on things.

You're being modest. It doesn't look half bad.

Note: on Safari at least, in general the text rendering is coming 
across as rather ... large.

BTW, how are you designing the underlying code that lays out the form?  
Would be nice to start with a system designed to be easily modified by 
users.  I'm no coder, but how about an xml template config file that 
defines how each type of record would be presented?  That way later on 
it's easier to add stuff other than films.

Bruce

[libdb-develop] Don't Look At This Demo

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

This is SooOSoooOOoOo very eaaRRrRrLLlLy that I'm only mentioning it
to certify that, yup, I'm still working on things. Due to some deadlines
for a client, I'll probably have a very infantile, very basic, very "pff,
you call this worthy?" working "submit film to db" stuff by next week
sometime. Anyways, for this client, the interface for "Add Film" looks
something like:

   http://disobey.com/noos/LibDB/dev/?tmpl=add_film

Nothing works (well, save for the preloading of possible locations
and identifiers), but this is just where I'm at, at this minute.
Definitely not ready for anyone to use.

-- 
Morbus Iff ( I'd prefer my past to be multiple choice. )
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] "chapters"

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

On Feb 14, 2004, at 12:06 PM, Morbus Iff wrote:

>> What's the purpose of this structure?  Is it just to register the, um,
>> contents of some thing?  So, I pull up a book record and this field
>> displays the table of contents?  The same with a DVD?
>
> In essence, yes.

You could always call it "listOfContents" or some such.  That means the 
same thing as table of contents, but moves away from the book 
association.

Bruce

Re: [libdb-develop] "chapters"

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

>> or "Contents", thinking of movies + books) or should things be broken
>> down into different types of annotations? "Movie Chapters",
>> "Contents (Physical)", and "Contents (???)"?
>
>What's the purpose of this structure?  Is it just to register the, um,
>contents of some thing?  So, I pull up a book record and this field
>displays the table of contents?  The same with a DVD?

In essence, yes.

-- 
Morbus Iff ( a blivet is 11 pounds of manure in a 10 pound sack )
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

[libdb-develop] xisbn update

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

FYI, Jon Udell has a note about an update to the FRBR-ized ISBN lookup 
service.

	http://weblog.infoworld.com/udell/2004/02/13.html#a916

Bruce

Re: [libdb-develop] Very Early Browsing Demo

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

>Question: what is the purpose of this interface?  I thought you were
>going to hide the FRBR stuff from the user?  Or is this more the
>beginnings of an admin UI?

It's more a "here's all the code I need to write" <g>. It's mostly
a "developer's interface" at the moment; something quick for me to
test all the functions and SQL code that I'm currently writing.

>I guess where I'd start is the basic search and results interface. So,
>I want to find an item; how do I do it?  How does the metadata get
>displayed, with what sort of labels, etc.?

I'm getting there, slowly but surely. Once I have all the DB access
code written for the literal FRBR parts (regardless of whether the
user interface mentions FRBR, the code and database need to talk
like that), then packaging them together as specific/generic/advanced
searching will be a lot easier (as I can just start plucking existing
code APIs out of the trees).

-- 
Morbus Iff ( were you a community theatre satan? )
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] Very Early Browsing Demo

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

On Feb 11, 2004, at 8:59 PM, Morbus Iff wrote:

> I want comments on design, css, colors, buttons,
> browsers, questions, etc., etc.

Question: what is the purpose of this interface?  I thought you were 
going to hide the FRBR stuff from the user?  Or is this more the 
beginnings of an admin UI?

I guess where I'd start is the basic search and results interface. So, 
I want to find an item; how do I do it?  How does the metadata get 
displayed, with what sort of labels, etc.?

Bruce

Re: [libdb-develop] Very Early Browsing Demo

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

> http://www.disobey.com/noos/LibDB/dev/?tmpl=variants

And an even rougher demo of "roles":

  http://www.disobey.com/noos/LibDB/dev/?tmpl=roles

The "role names" are clickable; go ahead and try.
Ignoring the fact that the visuals suck, thoughts?

-- 
Morbus Iff ( for safety's sake, don't humiliate me )
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

[libdb-develop] Very Early Browsing Demo

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

Hey all. Just wanted to show you one page of the future
browsing+installer release. This page shows the variant
titles in the sample database:

 http://www.disobey.com/noos/LibDB/dev/?tmpl=variants

A few things:

 * nothing else works.

 * mod_perl is causing my code some difficulties that i'm
   still trying to hash out. if you get an error about "->connect"
   not being defined, refresh about 30 times (literally) and you'll
   probably get a proper read. if anyone knows mod_perl, email me
   privately ;)

I want comments on design, css, colors, buttons,
browsers, questions, etc., etc., etc. Rip me a new one.

-- 
Morbus Iff ( they should rename controlled chaos to morbus droppings )
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

[libdb-develop] LibDB 0.0.3 Released

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

Download: http://osdn.dl.sf.net/sourceforge/libdb/libdb-0.0.3.tar.gz
Blog Entry: http://www.disobey.com/dnn/2004/02/index.shtml#001578
Release Notes: http://www.disobey.com/noos/LibDB/?ReleaseNotes003
LibDB Homepage: http://www.disobey.com/noos/LibDB/

LibDB 0.0.3 has been released. It is the last installer-only version of the
LibDB project. The next planned version, 0.1.0, will contain some, if not
all of the administrative and browsing interfaces for the database. If you
could, I'd appreciate some testing on this one, as it does revise a number
of file locations, as well as adds a new test of a proper installation.

Changes in 0.0.3:

  - we now exit with a note if our Perl is less than 5.6.1.

  - use ExtUtils::Manifest to ensure the user's archive is complete.

  - .htlibdb has been moved to settings.cgi; easier to find in FTP.

  - /installer/index.cgi has been moved to /installer.cgi; less confusion.

  - all installer pages now xhtml 1.1 and css valid (well, save
    for any form that uses our qforms js, but that's because mozilla
    needs the "name" attribute, not "id").

  - minor changes to the templates to support IE5/Win32.

-- 
Morbus Iff ( i've got the creme filling )
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] "chapters"

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

On Feb 9, 2004, at 5:10 PM, Morbus Iff wrote:

> And, thinking further ahead with my desire for serials (which I'll
> be doing after movies), I can see "Chapters" not being an appropriate
> denomination for a magazine. So, should there be one communal term
> with possibly confusing, or improper characteristics (ala "Chapters"
> or "Contents", thinking of movies + books) or should things be broken
> down into different types of annotations? "Movie Chapters",
> "Contents (Physical)", and "Contents (???)"?

What's the purpose of this structure?  Is it just to register the, um, 
contents of some thing?  So, I pull up a book record and this field 
displays the table of contents?  The same with a DVD?

MODS actually has a tableOfContents element, though I never use it...

Bruce

Re: [libdb-develop] "chapters"

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

 >I'm just coming at this from my perspective, and thinking down the line
 >when someone (say me) wants to store a book chapter per se as a
 >complete record (an expression I suppose), complete with its title,
 >page numbers, etc.

And, thinking further ahead with my desire for serials (which I'll
be doing after movies), I can see "Chapters" not being an appropriate
denomination for a magazine. So, should there be one communal term
with possibly confusing, or improper characteristics (ala "Chapters"
or "Contents", thinking of movies + books) or should things be broken
down into different types of annotations? "Movie Chapters",
"Contents (Physical)", and "Contents (???)"?


-- 
Morbus Iff ( i put the demon back in codemonkey )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus

Re: [libdb-develop] "chapters"

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

On Feb 9, 2004, at 4:14 PM, Morbus Iff wrote:

> [1] Though, technically, those bits of contents are in fact stored
> on a chapter of a DVD, the chapters I was referred to here was
> the movie chapters, often shown on an inset card.

OIC.

I'm just coming at this from my perspective, and thinking down the line 
when someone (say me) wants to store a book chapter per se as a 
complete record (an expression I suppose), complete with its title, 
page numbers, etc.

Bruce

Re: [libdb-develop] "chapters"

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

 >Was just looking through the schema.  I wonder if "chapters" in the
 >annotation table ought to be named something different.  "Contents"?

Is "contents" still representative of a DVD? Is "Contents" literal,
or figurative? The "contents" of THE WICKER MAN box set includes
some little trinket thing I can't remember. Likewise, the "Contents"
of the DVD could be "13 trailers; 2 Behind-the-scenes, 3 featurettes".
At least in the realm of a DVD "chapter", that's not what I meant. [1]
FRBR kinda confuses this issue, though, with the approach that
each extra "thing" of a manifestation should be considered a
different work. So, a DVD's "behind-the-scenes" is considered
a new work, related to the original movie work. An English book,
with a syllabus, are considered two separate related works.

[1] Though, technically, those bits of contents are in fact stored
on a chapter of a DVD, the chapters I was referred to here was
the movie chapters, often shown on an inset card.


-- 
Morbus Iff ( i put the demon back in codemonkey )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus

[libdb-develop] "chapters"

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

Was just looking through the schema.  I wonder if "chapters" in the 
annotation table ought to be named something different.  "Contents"?

Bruce

Re: [libdb-develop] [ANN] LibDB 0.0.1 Released

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

>OK, that's cool then.  The README should just say "move the extracted
>libdb directory to the ____ directory" and all will be clear.  The

Sounds good.

>existing language is just ambiguous.  I also got confused on OS X
>because I have two directories on my server: a cgi-related one, and one
>called "Documents."  The libdb only goes in the former, despite the
>fact that it contains documents?

Yup, and that's standard sorta stuff for web servers: by default, they
have a "put naughty programs that run at the visitor's request here" (ie.
CGI programs) and a "put plain old HTML, text or images here" (ie. documents).

You bring up a point that the installer helps you through: documents
placed in CGI directories ARE NOT accessible from the web: the webserver
tries to execute them, instead of serve their contents. The first page
of the installer checks to see if it can access these files, and if
it can't ("can't" being determined by whether you visually ID something
as working or not), instructs you to move them into a web accessible
directory (in your case, "Documents").

The installer determines that for you, and not extra steps in a README.txt,
because there ARE circumstances where you can have a CGI script and a
document in the same directory, and they're happily served with no
problem. LibDB is being tested under this configuration, your configuration,
and one other possibility (mod_perl).

-- 
Morbus Iff ( oh, i wish i was a hoggle )
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

[libdb-develop] roles and genres

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

On Feb 6, 2004, at 7:13 PM, Morbus Iff wrote:

> Fair enough. The big challenge is showing the proper
> list, at the proper time. Say we have books and movies.
> It's quite easy to say "show me only roles related to books".
> But, now, add two different authorities. How would we display
> them? Both in the same list ("author [marc]", "author [bob]").
> What about equivalence? Which is the more proper authority to use?

You're right; this is tricky.  I don't necessarily have any good 
answers, but let me think aloud...

What about using the MARC list as the generic LCD?  You then have 
genre/community-specific extensions.  So MARC has director, writer and 
probably a few other movie-related terms.  You then have a "film" 
extension that covers everything else.  Each term, no matter where it 
is, then has a list of possible genres/types they can be associated 
with.

But this issue of "type" classification by which you do this mapping is 
REALLY difficult.  For example, we could say that the sort of terms you 
have now could apply to all films.  We could then say there's a similar 
group of terms for written texts, including (but not limited to) books. 
  But what about legal texts?  Personal communications?

I'd like to think this through some more because it has bearing beyond 
this project.

Bruce

Re: [libdb-develop] [ANN] LibDB 0.0.1 Released

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

On Feb 7, 2004, at 10:39 AM, Morbus Iff wrote:

> Hmm. I'm confused, then. They *are* all in one dir, named 
> "libdb-0.0.1",
> at least, on my machine. Same with the just released "libdb-0.0.2".

OK, that's cool then.  The README should just say "move the extracted 
libdb directory to the ____ directory" and all will be clear.  The 
existing language is just ambiguous.  I also got confused on OS X 
because I have two directories on my server: a cgi-related one, and one 
called "Documents."  The libdb only goes in the former, despite the 
fact that it contains documents?

Bruce

Re: [libdb-develop] [ANN] LibDB 0.0.1 Released

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

>Right.  It's not clear (to me) which files must be uploaded, and where
>they can and should go.  Sticking them in a single folder and saying
>"move the folder" is more clear for me.

Hmm. I'm confused, then. They *are* all in one dir, named "libdb-0.0.1",
at least, on my machine. Same with the just released "libdb-0.0.2".

>> >"installer/index.cgi" isn't a valid url.
>> >If I try this, though, it doesn't work:
>> >http://localhost/installer/index.cgi
>>
>> Define "it doesn't work".
>
>"File not found"
>
>On OS X, I put them all in /Library/WebServer/CGI-Executables; no

Then you want: http://localhost/cgi-bin/installer/index.cgi.

-- 
Morbus Iff ( think about the good things that I did for you )
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