Hi, Helix84,
OK, thanks for that -- starting to make more sense.
Here's the thing -- I've been bouncing around Dublin Core and danged if
I can find some of the really basic stuff I need to record (maybe I just
haven't followed the right link yet, eh?).
The basic stuff I do need to record:
* Title
* Author
* Type (book, monograph, notes, document)
* Size
* Subject
* Illustrator
* Publisher (name, location)
* Date
* Printer (name, location)
* Date
* Binding
* Binder (name, location)
* Date
* Acquired (Dealer, location)
* Date
* Cost
* Language (English, Old- and New French, German, Latin, Greek,
Portuguese, Spanish, Italian; ISO codes, of course)
* Evaluator
* Date Evaluated
* Condition
* Notes
The contributor is one person, a constant, which may be ignored or may
be batch updated -- everything is from one estate.
I can figure out most of it, but danged if I've been able to find where
to put dealer, cost, evaluator and maybe illustrator (many volumes are
illustrated with original art in various formats; e.g., copper etchings
from, oh, 1620). We have first editions illustrated by George
Cruikshank, kind of an important guy in the 19th century. It would be
convenient to define a field, and I have no clue on this one, for a
chain of ownership; e.g., one recent volume I evaluated contained the
original owner's hand-written signature and address: "George R, Hampton
Court" (there would only be one George R(egent) resident at Hampton
Court -- see what I mean?). There are a number of presentation copies
(the pages aren't trimmed, not meant to have been read).
Most of the list I've been able to find or figure out, but there are
those that I haven't and I know those will be mandatory so I need to
figure them out, too. I've been looking at Using Dublin Core
<http://www.dublincore.org/documents/usageguide/> (out-of-date, but it's
got examples in it) and getting a better feel for how to use it; I've
also been reading through Dublin Core Metadata Element Set v. 1.1
<http://www.dublincore.org/documents/dces/> (no examples, but more
in-depth). But, cost? Nope, nowhere to be found (and I can't imagine
anybody not wanting to record where I got it and how much I paid for it).
You know, if I'd just done a LAMP data base I'd have been done weeks ago
-- but, big but, it wouldn't adhere to any particular standard and would
be just as useless and the FoxBase thing we've already got (with few,
really, really few, entries in it). So I'm pretty sure DSpace is worth
the effort and I am grateful for the help and advice, thanks.
Thomas
A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm
stickin' to it.
On 08/05/2013 08:20 AM, helix84 wrote:
On Mon, Aug 5, 2013 at 2:19 PM, helix84 <[email protected]> wrote:
define which metadata fields
you'll be using and which ones of those are missing from the default
metadata registry in DSpace. You should add all those you'll be using.
To do that, log in as admin and go to Registries - Metadata in the admin menu.
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-general
