On Mon, Jul 22, 2013 at 3:51 PM, Mark H. Wood <mw...@iupui.edu> wrote: > I think you could do that, but I'm wondering why. What makes > cg.org1.subject a different data type than cg.org2.subject, or for > that matter, say, dc.subject?
Hi Mark, you certainly have a point there. I'll try to explain one situation in which it would make sense. If the two organizations have different requirements on the schema, you would have to keep them separate. E.g. org1 wants to use org1.foo, but for org2 org2.foo has a different meaning because they're harvested by someone else, who requires that specific meaning (yes, I'm ignoring the concept of dissemination crosswalks here). In a real world scenario, it could be author's keywords for org1.subject, but controlled vocabulary keywords for org2.subject. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
