On Mon, Aug 5, 2013 at 6:03 PM, Thomas Ronayne <[email protected]> wrote: > 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?).
It's OK, it takes time getting used to. I'd say everyone curses their first schema and learns wth their second one. > The contributor is one person, a constant, which may be ignored or may be > batch updated -- everything is from one estate. Don't put it into dc.contributor. DSpace uses dc.contributor.author for the actual author and you wouldn't want to mix these up, which could happen e.g. when crosswalking QDC to DC. Create your own field for your "contributor", which brings me to the most important advice - don't touch the "dc" namespace, create your own namespace called "local" and create any new fields solely in there. What seems to fit into dc, put to dc; put the rest into your own "local" namespace. > 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 is a thing called "authorities" for this (for creating an ID for a single person/string), but currently they're easily usable only on one field. You'll probably want that field to be the author and you'll probably want to postpone implementing authorities for later; it's an advanced topic. > 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. Yep, see above - your custom "local" schema. Define it anyway you see fit. 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
