On Sep 28, 2009, at 9:53 AM, Mark H. Wood wrote: > So, just to make certain: > > o There is a Bitstream Format Registry, which is initially populated > at setup time from bitstream-formats.xml and modified later through > one of the UIs. > > o There is a Metadata Schema Registry, which is populated whenever > a schema is installed. There is no separate file to be loaded; the > information is supplied with each schema.
Actually, the "dc" metadata schema is pre-loaded when the database is initialized, at least for Oracle. The PostgreSQL version of database- schema doesn't seem to add the "dc" row to the MetadataSchemaRegistry so I'm not sure where it gets done, but the RegistryLoader doesn't do it. Additional metadata schemas must be added manually, in the administrative UI. As for modifying the DC fields, I think that's really a matter of policy for each site. We should document the risks, mainly which fields are "magic" in that DSpace scribbles on them automatically (e.g. dc.description.provenance, dc.date.available). It is legitimate for a site to new "standard" DC fields; DCMI (see http://dublincore.org/ ) is always updating the official list of terms, and they have a registry[sic] of common usage: http://dcmi.kc.tsukuba.ac.jp/dcregistry/ -- Larry > o The "Dublin Core Metadata Registry" is a single schema definition, > loaded from dublin-core-types.xml. Loading it also adds DC to the > Metadata Schema Registry. This serves as an example of the > previous point. > > Correct? > > We ought to call the "Dublin Core Metadata Registry" something else, > IMHO. My understanding is that DC is DC and shouldn't be altered by > others; that the type definitions supplied with DSpace are (nearly) a > "profile" defining what parts of DC are core to DSpace; and that > anyone who wants other types should use or (if necessary) create an > additional schema. I'm not an expert on such matters and I hope to > see comments from those who are, but if this area of the documentation > is being cleaned up right now then it is an excellent time to nail > down what we mean and what we recommend. > > (I recall some comment that we are abusing one of the DC types. > Someday we ought to correct that, but for now at least it should be > well documented that whatever type that is does not mean in DSpace > what you might think it means from studying DC.) > > -- > Mark H. Wood, Lead System Programmer [email protected] > Friends don't let friends publish revisable-form documents. > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf_______________________________________________ > Dspace-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
