On Thu, Sep 09, 2010 at 10:22:36AM -0600, Brian Freels-Stendel wrote: > I have a small concern about the metadata fields that might be employed, > though. In my search to figure out how to do it, I ran across a message from > someone that suggested using a schema other than DC, so that they wouldn't be > harvested via OAI and such. I thought that was a pretty good idea, since the > fields would not provide any useful information outside the specific > instance. I think that, even if these fields are standardized within DSpace, > they still won't provide useful information to the outside world.
Seconded. We may have a tradition of abusing DC but we should not extend it. I made up a DXM (DSpace eXtra Metadata?) schema out of thin air to house dxm.embargo.terms and dxm.embargo.liftdate so I wouldn't pollute the DC namespace, even if no one ever sees it. If there isn't already a namespace which defines usable terms, then we need a private one for DSpace. We might even migrate our "DC" neologisms into it someday. -- Mark H. Wood, Lead System Programmer [email protected] Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_
pgpOgVfVfu11Q.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
